Hi Michael,
Since creating event log source requires administrative privilege, and it's
only needed to create once, I recommend you create the event log source in
the installer rather than in the service.
We can move the code to create the event log source from MyNewService to
ProjectInstaller:
public partial class MyNewService : ServiceBase
{
public MyNewService()
{
InitializeComponent();
eventLog1.Source = "MySource";
eventLog1.Log = "MyNewLog";
}
[RunInstaller(true)]
public partial class ProjectInstaller : Installer
{
public ProjectInstaller()
{
InitializeComponent();
if (!System.Diagnostics.EventLog.SourceExists("MySour ce"))
{
System.Diagnostics.EventLog.CreateEventSource("MyS ource",
"MyNewLog");
}
As the walkthrough mentioned, reinstalling the service on Windows 2000 will
needs rebooting since the service control manager will first disable the
service for deleting on reboot; for Windows xp and above, the windows
installer has some feature can reinstall the service without rebooting.
That's why you need to use the generated setup file to re-install the
service.
The installutil will need an assembly and install/uninstall the installers
inside the assembly. In this case, we don't need to use installutil
manually, since we've already created a setup project to call the installer
within the service assembly.
Sincerely,
Walter Wang (wawang@online.microsoft.com, remove 'online.')
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications. If you are using Outlook Express, please make sure you clear the
check box "Tools/Options/Read: Get 300 headers at a time" to see your reply
promptly.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.