G
Guest
I use csc to build my applications (makefile as opposed to using Visual
Studio). I recently noticed a problem because I had forgot to specify
/target:winexe for a GUI application. As a result when you ran the
executable it would launch a command window that stuck around for the life of
the GUI. If you closed the command window the GUI would close. Adding
/target:winexe fixed that problem.
I have two other executables I create. However, these are both Windows
services. I'm not specifying /target for those either so they are getting
the default of exe (console application). Is this a problem? I checked task
manager on the machine where these services are running and I don't see any
command processors running. What should the /target setting be for .NET
Windows Services?
--
Thanks,
Nick
(e-mail address removed)
remove "nospam" change community. to msn.com
Studio). I recently noticed a problem because I had forgot to specify
/target:winexe for a GUI application. As a result when you ran the
executable it would launch a command window that stuck around for the life of
the GUI. If you closed the command window the GUI would close. Adding
/target:winexe fixed that problem.
I have two other executables I create. However, these are both Windows
services. I'm not specifying /target for those either so they are getting
the default of exe (console application). Is this a problem? I checked task
manager on the machine where these services are running and I don't see any
command processors running. What should the /target setting be for .NET
Windows Services?
--
Thanks,
Nick
(e-mail address removed)
remove "nospam" change community. to msn.com