Hi Danny,
Try a conditional debug as a workaround if you suspect it to be a bug in VS 2010. Below is a link that might help you: http://stackoverflow.com/questions/3788605/if-debug-vs-conditionaldebug Regards, Benj On Oct 26, 5:01 pm, Danny <[email protected]> wrote: > For some obvious reasons, I have (strike that, 'had') some # If DEBUG > then ... # End If in my code to skip some unneeded checks in the code > while developping (ie bypassing login screen). > > To my surprise the compiled/build version of the executable still > considered istelf as being in DEBUG, as the login in this case was > still bypassed. > > I have the impression that - as Build/publish is invoked during debug > - the DEBUG variable is not set to False hence generating code that > behaves as if in DEBUG. > All other aspects of DEBUG are I believe removed as the release-exe is > 15% smaller than de debug-exe. > > Is this a bug in VS? I use now 2010, but 2008 had it also, not sure > about 2005.
