Version history of the CLR 2.0

MSDN Blog Postings » Version history of the CLR 2.0

MSDN Blog Postings » Version history of the CLR 2.0 — Thu, 06 Sep 2007 15:33:07 GMT

PingBack from http://msdnrss.thecoderblogs.com/2007/09/06/version-history-of-the-clr-20/

A listing of CRL 2.0 Hot Fixes

This Old Code — Thu, 06 Sep 2007 17:27:44 GMT

re: Version history of the CLR 2.0

dougste — Thu, 06 Sep 2007 18:49:51 GMT

Thanks Aaron (of 'This Old Code'), you're welcome!

As an escalation engineer in Microsoft's support organisation it's part of my role to provide technical detail to go into the hotfix articles. There are others involved in the publication process so I do not always have complete control over the final wording that appears but I certainly appreciate the need to make articles as useful as possible.

Thanks for the feedback!

Doug

Know your CLR 2.0 versions

Development 4.0 — Thu, 06 Sep 2007 19:27:48 GMT

Know your CLR 2.0 versions

Pratique : historique de versions du CLR 2.0

CoqBlog — Sun, 16 Sep 2007 18:40:41 GMT

Ca, ça peut être très pratique : Notes from a dark corner : Version history of the CLR 2.0 Une historique

1433

Notes from a dark corner — Thu, 22 Nov 2007 12:25:56 GMT

This is a number that is going to become very familiar to me over the coming months and probably years.

1433

Noticias externas — Thu, 22 Nov 2007 12:35:24 GMT

This is a number that is going to become very familiar to me over the coming months and probably years

re: Version history of the CLR 2.0

jesperjfj — Fri, 14 Dec 2007 18:28:02 GMT

Hi Doug

We have received a report where our product was running in .Net 3.0 mode, but where .Net 3.5 had been installed. I can see that this changes the version of aspnet_wp.exe to .1433. The worker process died and left this clue in the event log. It is reproducible. How do we best address this quite fatal error?

Best regards

Jesper Jørgensen, Sitecore

Faulting application aspnet_wp.exe, version 2.0.50727.1433, stamp 471ebf4c, faulting module kernel32.dll, version 5.1.2600.3119, stamp 46239c31, debug? 0, fault address 0x00012a5b.

aspnet_wp.exe (PID: 1620) stoppede uventet.Yderligere oplysninger finder du under Hjælp og support på

re: Version history of the CLR 2.0

dougste — Fri, 14 Dec 2007 18:44:34 GMT

Hi Jesper

One option is to raise an assisted support case with Microsoft support. We have a bunch of talented support engineers ready to assist troubleshoot such issues with you. If it turns out to be due to a Microsoft bug there is no charge. And maybe you already have a support contract with us or support incidents available through an MSDN subscription or through having Partner status?

The other option is to DIY debug it. Grab a memory dump at process shutdown and then use the debugging tools to figure out what happened.

My colleague Tess has a very details blog showing how to do this kind of debugging. See the first link under "Blog I recommend" above left.

Regards

Doug

re: Version history of the CLR 2.0

JamesBuddell — Mon, 30 Jun 2008 13:15:56 GMT

Very useful list, thank you!. Just found one extra version that's not covered, see: http://support.microsoft.com/kb/923028

re: Version history of the CLR 2.0

abfo — Wed, 10 Jun 2009 20:08:37 GMT

Any plans to update this invaluable list? I'm trying to hunt down version 4903 at the moment. I've found 3521 in Win 7 Beta and 4918 in Win 7 RC 1.

re: Version history of the CLR 2.0

dougste — Fri, 12 Jun 2009 19:30:24 GMT

Yes, this list is overdue for an update. I will try to do it soon.

4903 is a strange number. Looks to high to be any official hotfix release and I am not aware of any beta release that would include that.

Doug

re: Version history of the CLR 2.0

Reg — Mon, 05 Oct 2009 19:37:03 GMT

An update would be most appreciated. I have Win7 RC1 with 4918, but am looking for 4927.

re: Version history of the CLR 2.0

dougste — Thu, 08 Oct 2009 14:05:52 GMT

4927 is the Windows 7 and Windows Server 2008 R2 version.

I've just made a minor update. A major update is long overdue and I am working on it.

Thanks

Doug