Visual Studio - Debug vs Release

15
votes

I built a windows service, targeted for .NET 2.0 in VS 2008. I run it as a console app to debug it.

Console app is working great. I put it on my local computer as a service, compiled in debug mode, still working great. I'm ready to release now, and suddenly, when I set it to release mode, the service compiles and installs, but nothing happens. (No code in service is running at all).

I realize that the release vs debug mode are property configuration settings, but it seems that in release mode, even when I check define DEBUG constant, uncheck Optimize code, and set Debug info to 'full', it is still doing nothing.

Set it back to debug and it's working like a charm again.

(As a sidenote, I tried resetting the target framework to 3.5 to make sure that wasn't the issue, too)

So my questions (in order of importance) are these:

  1. Will using my "debug" version in any way ever cause any problems?

  2. What settings are different between debug and release besides the three I've been trying to change already?

  3. This seems like a weird error to me and has stirred up my curiosity. Any idea what would cause this?

EDIT: Should mention, I already am using a custom installer. Basically I compile the program (in either debug or release) and then install it with the respective installer.

2
c#visual-studiowindows-servicespropertiesrelease
are you sure the service is being installed (and correctly, at that) when in release mode? - Josh E
You need an installer and a custom action for your windows service. More info here: msdn.microsoft.com/en-us/library/d56de412(VS.80).aspx - Robert Harvey
Does the service enter the Running state? Anything in the EventLog? - Stephen Cleary
@Robert Harvey: I have an installer. What I do is build the project in "debug" mode, then I use the installer that is created to install service to my local machine. Then I use services.msc to stop, start, and restart. @Josh E: Given that I install it the same way every time, regardless of how I compile it, I don't see where I would be going wrong? @Stephen Cleary: I can get to the event viewer, but am unsure what I'm looking for? - Brandi
use the System.ServiceProcess.ServiceBase.EventLog instance to write messages to the Event Viewer as your service starts up. For example, in the OnStart() callback, write a message indicating you've at least got that far. This will help you narrow down where the problem is occurring. Chances are, your service is triggering an exception that is shutting it down. If so, putting a try-catch block in the Main() function of your service and writing a message to the Event Viewer in the catch block that includes the stack trace will show you precisely where the problem occurs. - Matt Davis

2 Answers

17
votes

1) It might, if not directly, so indirectly by making the application slower and making it use more memory.

2) When it runs in debug mode, there are certain things that works differently, for example:

  • The code is compiled with some extra NOP instructions, so that there is at least one instruction at the beginning of each code line, so that it will be possible to place a break point at any line.

  • The instructions can be rearranged in release mode, but not in debug mode, so that the code can be single stepped and the result will correspond to the exact order of the source code.

  • The garbage collector works differently, by letting references survive throughout their entire scope instead of only for the time that they are used, so that variables can be viewed in debug mode without going away before the scope ends.

  • Exceptions contain more information and takes a lot longer to process when thrown.

All those differences are relatively small, but they are actual differences and they may matter in some cases.

If you see a great difference in performance between debug mode and release mode, it's usually because there is something wrong with the code, like for example if it's throwing and catching a huge amount of exceptions. If there is a race condition in the code, it may only happen in release mode because there is some extra overhead in debug mode that makes the code run slightly slower.

3) As to what the problem with your service is, I don't know, but it doesn't seem to be related to how the code is executed in debug mode or release mode. The code would start in any case, and if it was a problem with the code, it would crash and you would be able to see it in the event log.

0
votes

I'm not sure I can speak to #1 or #2, but when I've had problems like that, it was because of incorrect threading/concurrency. I'm not sure how large your app is, but that might be a good place to start.