Skip to main content

.Net v4 vs v2 - In-Process Side-by-Side

In-Process Side-by-Side, or In-Proc SxS is a process whereby assemblies written in .NET4 and .NET2 co-exist together in runtime.
This is possible because a process is able to host multiple version of .NET CLR in a single process.
This means if an application is recompiled to run against the .NET Framework 4 runtime and still has dependent assemblies built

against .NET 2.0, those assemblies will load on the .NET 4 runtime transparent to the user.

It faces problem (if .NET4 runtime is used) in the following areas:

a) Shell Extension support is limited. Application built with earlier version wil fail.

b) C++/CLI section which specifically states that a pre-2.0 mixed mode assembly can only load in a v2 CLR. The v4 CLR does not

support this scenario. There is no solution to this problem. You have to recompile the mixed mode assembly under v4 or switch back

to v2 for your application.

http://msdn.microsoft.com/en-us/magazine/ee819091.aspx

Comments

Popular posts from this blog

Android Programmatically apply style to your view

Applying style to your view (button in this case) dynamically is pretty easy. All you have to do is place the following in your layout folder (res/layout)
Let's call this file : buttonstyle.xml
<?xml version="1.0" encoding="utf-8"?> <selector xmlns:android="http://schemas.android.com/apk/res/android"> <item android:state_pressed="true" > <shape> <solid android:color="#449def" /> <stroke android:width="1dp" android:color="#2f6699" /> <corners android:radius="3dp" /> <padding android:left="10dp" android:top="10dp" android:right="10dp" android:bottom="10dp" /> </shape> </item> <item> <shape> <gradient android:startColor="#449def" a…

DataTable does not have AsEnumerable

I have problem locating my AsEnumerable extension method in my DataTabe (System.Data). Thank god for this post by Angel
(http://blogs.msdn.com/angelsb/archive/2007/02/23/does-not-contain-a-definition-for.aspx)

I was able to find this method once i have added reference to the following assembly.

C:\Program Files\Reference Assemblies\Microsoft\Framework\v3.5\System.Data.DataSetExtensions.dll

Try to do a dummy Build and you should be able to get it.

OpenCover code coverage for .Net Core

I know there are many post out there getting code coverage for .dotnetcore. I'm using opencover to address this needs.

In case, you do no want to use opencover and wanted to stick with vs2015 code coverage, you can try to copy Microsoft.VisualStudio.CodeCoverage.Shim.dll from C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Dynamic Code Coverage Tools\coreclr\ and drop it into your project "bin\Debug\netcoreapp1.0" folder.  Please note : you need to be on VS2015 Enterprise to do this. 

To get started, I guess we need to add OpenCover and ReportGenerator for our test projects, as shown in diagram below :-



When nuget packge gets restored, we will have some binaries downloaded to our machine and we going to use this to generate some statistics. I think the biggest issue is to getting those command lines work.

In dotnetcore, we run test project using "dotnet test" (assuming you are in the test project folder - if not please go there)  So we add this …