Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / New Users / July 2007

Tip: Looking for answers? Try searching our database.

Writing to the EventLog in Vista

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Henrik Skak Pedersen - 11 Jul 2007 14:41 GMT
Is it possible to write an entry in the "Windows Logs\Application" EventLog
and set the source to the name of our application, without creating a source
for our application ?
If we set source to "Application" when calling the WriteEntry method on the
EventLog class, the Source name for the entry will be "Application".

Best regards

Henrik Skak Pedersen
Kevin Spencer - 11 Jul 2007 18:05 GMT
Hi Henrik,

Actually, you're confusing the Source and Log properties of the EventLog
class, not surprisingly, as I had to look it up to ensure that I was
remembering it correctly. I wrote a number of classes to support Event
Logging a couple of years ago, and I rely on them, so it wasn't exactly
fresh.

The Log property is the log that is written to, as in Application, System,
Security, etc. The Source is the Source name that appears in the log for the
source of the log entry. Each Log can have many sources.

I'm not sure you can use an existing Source, as it may be in use already by
the original Source creator, and there may be a conflict as a result. It is
certainly possible to create your own Event Log and Event Source in Windows
Vista, as long as you have the correct (Administrator) permission to do so.

Signature

HTH,

Kevin Spencer
Microsoft MVP

Printing Components, Email Components,
FTP Client Classes, Enhanced Data Controls, much more.
DSI PrintManager, Miradyne Component Libraries:
http://www.miradyne.net

> Is it possible to write an entry in the "Windows Logs\Application"
> EventLog and set the source to the name of our application, without
[quoted text clipped - 5 lines]
>
> Henrik Skak Pedersen
Jeffrey Tan[MSFT] - 12 Jul 2007 08:04 GMT
Hi Henrik,

Yes, just as MVP Kevin pointed out, you should set EventLog.Log property to
"Application" to write to "Windows Logs\Application". Then, you may use
EventLog.Source property to customize your log entry name as your
application name. Like this:

private void button1_Click(object sender, EventArgs e)
{
   EventLog myNewLog = new EventLog();
   myNewLog.Log = "Application";
   myNewLog.Source = "MyApplicationName";
   myNewLog.WriteEntry("This is a test");
   myNewLog.Close();
}

Hope this helps.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

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/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Henrik Skak Pedersen - 17 Jul 2007 09:02 GMT
Hi again,

Thank you very much for your responses. My problem is now solved.

Cheers Henrik.

> Hi Henrik,
>
[quoted text clipped - 37 lines]
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
Jeffrey Tan[MSFT] - 17 Jul 2007 09:31 GMT
Thank you for the confirmation, if you need further help, please feel free
to post, thanks.

Best regards,
Jeffrey Tan
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

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/subscriptions/support/default.aspx.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.