Scott Dorman

ephemeral segment
  Home  |   Contact  |   Syndication    |   Login
  608 Posts | 11 Stories | 898 Comments | 51 Trackbacks

News


Post Categories

Image Galleries

About me
About me


Microsoft Store


Creative Commons License


Microsoft MVP


MCP Profile

INETA Community Speakers Program

combined Stack Exchange profile for Scott Dorman


Locations of visitors to this page

Subscribers to this feed

TwitterCounter for @sdorman

View blog authority

Add to Technorati Favorites

Windows Live Alerts

AddThis Social Bookmark Button

LinkedIn profile

Community Credit profile

The Code Project

Follow me on Twitter

Get Free Shots from Snap.com

Community Credit Hall of Fame

Get Feedghost

Xobni outlook add-in for your inbox

Tampa Bay Chapter
Tampa Bay IASA

Subscribe



Subscribe to this folder

Support This Site

Tag Cloud


Article Categories

Archives

Post Categories

Image Galleries

CLR 4.0: Corrupted State Exceptions

This post has been moved.

posted on Friday, November 7, 2008 3:19 PM

Feedback

# re: CLR 4.0: Corrupting State Exceptions 5/3/2010 10:50 AM Andrew Pardoe
Seems like a minor point, but not really: change "Corrupting State" to "Corrupted State". It's important to note that these exceptions don't corrupt the process state. It's the other way around: the process state is already corrupted when the exception is raised.

# re: CLR 4.0: Corrupted State Exceptions 5/3/2010 11:01 AM Scott
Thanks. I've updated the post and moved it to a new post with a corrected page name as well.

Comments have been closed on this topic.