We wanted to let you know that we’ll be changing the signature verification process for ClickOnce applications and WPF XAML Browser Applications (XBAPs) in an upcoming update. This change will help users recognize when they’re running untrusted applications from the Internet Zone,
Post by this author
The Base Class Libraries team, the wider CLR team and Microsoft Research worked hard on this new technology and we are very proud to be able to share the news. Read the full article for details.
Sorry for the late notice, but October installment of the “CLR Inside Out” column in MSDN Magazine is available on line. This month we have an article from Andrew Pardoe and Justin Van Patten on the move to a new CoreCLR for Silverlight 4.
After installing .NET 4.0 or later you may notice something a little unusual about your .NET processes. Here is a partial list of the loaded modules of a simple “Hello World” executable compiled with the .NET 2.0 compiler.
start end module name
60f00000 61491000 mscorwks C:\Windows\Microsoft.NET\Framework\v2.0.50727\mscorwks.dll
6c650000 6c6b6000 mscoreei C:\Windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll
6d420000 6d46a000 MSCOREE C:\Windows\SYSTEM32\MSCOREE.DLL
75a80000 75aca000 KERNELBASE C:\Windows\system32\KERNELBASE.dll
Something here looks out of place –
This post is meant to help you understand what runtime in-process side-by-side is, how to think about it, how to use it, and how it affects application and component migration to the .NET 4 Runtime. This post is relevant to you if you use native runtime activation APIs,
The new installment of the “CLR Inside Out” column in MSDN Magazine is now available on line. This month we have an article from Luke Hoban of the F# team on F# Fundamentals. The article gives an overview of the language,
The new installment of the “CLR Inside Out” column in MSDN Magazine is now available on line. This month we have an article from Jon Langdon on Production Diagnostics Improvements in CLR 4. This article talks about some of the new diagnostics features we added in .NET Framework 4 and focuses on how they enable tools that help you find and fix those issues that seem to show up only after you’ve released your application.
The CLR Code Generation team blog has a series of new posts featuring hands-on style content around how to use the NGen technology and how to measure performance benefits from it. You can find the series here.
As hopefully most of you know, Microsoft has a site called Connect where customers can log bugs and suggestions (http://connect.microsoft.com/). Issues for .NET can be found in the Visual Studio and .NET Framework feedback category (http://connect.microsoft.com/VisualStudio/Feedback) and can be logged from the main Visual Studio Connect page (http://connect.microsoft.com/VisualStudio/).
Today the BCL Team is launching a CodePlex site to host samples, previews, and prototypes. You can find it at http://bcl.codeplex.com.
This is a site for the BCL Team to get features to customers to try out without requiring a Beta or CTP of the .NET Framework.