.NET Blog

Getting more information than the exception class provides

June 20, 2009 Jun 20, 2009 06/20/09

CLR Team

We recently had a question about how to get more information than an exception’s type provides. The developer was trying to copy a file and didn’t know why the copy was failing. File copies can fail for many reasons, almost all of them what Eric Lippert calls “exogenous conditions”. The developer was catching System....

Tail Call Improvements in .Net Framework 4

June 19, 2009 Jun 19, 2009 06/19/09

CLR Team

Grant Richins has a post on the CLR Code Generation team blog that covers the work done to improve the x64 JIT to honor the "tail." instruction prefix, thereby making functional languages like F# more viable. You can find the full post here...

What’s New for .Net Framework Security

June 11, 2009 Jun 11, 2009 06/11/09

CLR Team

 Shawn Farkas, CLR security developer, has started a cool series of posts on what’s new in .NET Framework 4 security. If you’re doing any work with or have scenarios involving partially trusted code, you’ll want to take a look. Topics include sandboxing, Code Access Security (CAS) Policy, and a nifty Channel 9 video. ...

New Security Model: Moving to a Better Sandbox

June 10, 2009 Jun 10, 2009 06/10/09

CLR Team

 For .Net Framework 4, we decided to remove the dependency on caspol and the policy levels and make things simpler. With this change, the default grant-set for assemblies is now FullTrust unless the host (such as InternetExplorer) decides to load them in a sanbox. We also made CodeAccessPermission.Deny obsolete. This MSDN ...

In-Process Side by Side Part 2 – Common in-proc SxS scenarios

June 7, 2009 Jun 7, 2009 06/7/09

CLR Team

Update: The information in this blog post applies to pre beta-1 behavior and is not applicable to beta 2 and RTM. We will have more posts and documentation on this subject as we get closer to RTM.  This section covers the most common in-process side by side scenarios. The scenarios cover which CLR is used to run the specific code, ...

In-Process Side by Side (Part1)

June 3, 2009 Jun 3, 2009 06/3/09

CLR Team

One of the new features in CLR 4 is In-Process Side-by-side (Inproc SxS) – a feature that lets you use multiple versions of .NET in the same process. For applications that use add-ins (particularly COM add-ins), in-proc SxS lets us provide a level of compatibility never before possible. If you write applications that use an add-in model (for...

In-Process Side by Side (Part1)

June 3, 2009 Jun 3, 2009 06/3/09

CLR Team

One of the new features in CLR 4 is In-Process Side-by-side (Inproc SxS) – a feature that lets you use multiple versions of .NET in the same process. For applications that use add-ins (particularly COM add-ins), in-proc SxS lets us provide a level of compatibility never before possible. If you write applications that use an add-in model (for...

CLR Inside Out – Memory Usage Auditing For .NET Applications

June 1, 2009 Jun 1, 2009 06/1/09

CLR Team

(image) The new installment of the “CLR Inside Out” column in MSDN magazine is now available on line.  This month we have an article from Subramanian Ramaswamy and Vance Morrison on Memory Usage Auditing For .NET Applications. You can find a list of all “CLR Inside Out” articles here.  As always, please let...

.Net Framework Performance Survery

May 29, 2009 May 29, 2009 05/29/09

CLR Team

Everyone has probably dealt with an annoying performance issue at some point or the other. Performance optimization is a hard problem and we could sure use some help from you. We have a survey posted at the CLR and Framework Performance blog over here. The survey contains questions assessing your level of satisfaction specific ...

More Channel 9 Videos on CLR 4

May 29, 2009 May 29, 2009 05/29/09

CLR Team

And the videos keep coming in! We have Shawn Farkas who works on the security model, talking about the new managed security model. Check out the video here. And then we have Surupa Biswas, from the CLR Code Generation team, talking about the new Targeted Patching work in CLR 4. The link to the video is here...