At 4/14/2005 04:15 PM, Palmer, Jean L. wrote:
>We have a developer who just now decided to see if his code works when >compiled as a release version. It doesn't... it isn't able to work with a >DLL from an outside vendor (who insists that their DLL is a release version >and that the problem isn't their fault).
Run depends on it. That will tell you what type it is (by the link requirements) and also why it doesn't load, if that is the problem.
>As a deadline looms near, it seems that it may be necessary to provide this >.exe to our customer as a debug version of the .exe. This is the only one >that works. It seems that the debug version would be larger and possibly >slower, and it may display its faults in a different way than the release >version would (for instance, ASSERTs). > >Are there other problems with sending out a debug version of an .exe that >I'm not aware of?
You can turn on optimization and turn off debugging information.
More importantly, check what it needs to run with.
Most likely, it will need the debug versions of the MFC and C Runtime dlls, which normal users don't have.
And, I think they are not redistributable.
You need to get the release working.
Phil Daley < AutoDesk > http://www.conknet.com/~p_daley
_______________________________________________ msvc mailing list [email protected] See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
