By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
432,028 Members | 1,092 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 432,028 IT Pros & Developers. It's quick & easy.

Critical Errors with Vista Event Logs

P: n/a
I have a test routine that looks at the Application, System, and Security
event logs. I noticed that Vista added a new "type" of error called
"Critical". However, VS 2005 doesn't list this new type in the
EventLogEntryType enum. Is there some patch that updates this type
definition or some other way to correctly identify a "critical" error under
Vista's event logs?

--
-----------
Thanks,
Steve
May 29 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Hi Steve,

Windows Vista has introduced a new eventing system, Windows Eventing 6.0,
and Windows Eventing 6.0 brings a new event level, Critical.

NET 2.0 doesn't support the event level, Critical. I think it may be
covered in the latest version of .NET Framework-.NET Framework 3.5 Beta.
You may get the .NET Framework 3.5 Beta from this link:

http://www.microsoft.com/downloads/d...E6F-E123-428B-
8A0F-028AFB9E0322&displaylang=en

I also suggest that you use Visual Studio Code Name "Orcas", the next
generation development tool for Windows Vista, when you are going to use
NET Framework 3.5 Beta. You can download the Visual Studio Code Name
"Orcas" from the link below:

http://www.microsoft.com/downloads/d...5DF-E369-4DB4-
B9A7-845DBF793368&displaylang=en

Hope this helps.
Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.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/subscripti...t/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

May 30 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.