Skip to main content

ASP.NET vNext - Deploying your own version of .NET Framework

By
In this post we will talk about a new feature of .NET, that will allow us to deploy the .NET CLR with the application itself. No more .NET installation and versioning problems… or not
The new version promises us that we will be able to include in the application package all .NET dependencies that we are using. This mean that we can run our application on machines where we don’t have .NET installed. When we create our build, the package will contains also all the .NET resources needed.
For example the client will not need any more to install the .NET framework. This is great, because there were cases when we had to install .NET 4.0 and also .NET 4.5 on different machines because of the dependencies.
In the same time, the client will have locally only .NET components that he is using. For example we don’t need WCF or WF components installed on his machine if the application don’t use it. The deployment and setup step will be simpler and we will not use need any more to consume client storage space with the full stack of .NET framework.
Another nice thing is related to versioning. We don’t need to care anymore what version of .NET the client have on the machine. We can directly include .NET component directly in it. In this way the CLR versioning is becoming simpler, clean and in self-hosting.
In this beautiful story people could see a problem. Let’s assume that you are developing a 5 different applications for an enterprise client. He will need to install all of them on his machine. Because each application will come with his own .NET dependencies you could have theoretically the same .NET components duplicated (with the same version). On the other hand, the storage is pretty cheap, the size of .NET framework is not very big and on top of this, you include only the .NET components that you are using. Because of this you will not have a 1.6 GB of .NET stuff there, you can have only 200 MB or less.
I would say that you have a lot of advantages using this way of deployment. The cost of storage is pretty low and the .NET footprint is extremely low. Keep in mind that you have all the dependencies in your own project and you can update them independently.
Our application folder will have all the CLR and .NET framework similar with a NuGet packages. You can even specify for each sub package of   .NET framework what version you want. For example we could have Microsoft.Asp.Net.MVC version 4.5.2.1.0 and Microsoft.AspNet.Hosting 5.4.2.3.
In conclusion we could say that we will have more flexibility than we had until now, our life will be easier. I expect on real application, especially in the one that are big to have problems with versioning, updating and things like this. But, no blockers and in the end we gain a lot from this feature.

Comments

  1. Marius OgreanMay 14, 2014 at 9:54 PM

    Nice!

    ReplyDelete
  2. tudor_turcuMay 14, 2014 at 10:17 PM

    Nice, but I'm wondering when a bug or security exploit is discovered in one .NET Framework version, how will the admin (or Windows Update) patch all these self-contained versions of .NET quickly.. :) (if they are scattered on various folders and not side-by-side in GAC)

    ReplyDelete
    Replies
    1. Radu VunvuleaMay 15, 2014 at 12:59 AM

      In the same way you make an update for a NuGet package (EF for example).
      They are only in the alpha version. I can bet that they will come with a solution for this problem.

      Delete
    2. tudor_turcuMay 21, 2014 at 7:18 PM

      Can a domain admin push an update to an assembly (DLL) to 100 client workstations using NuGet only?

      If each application will have it's own 'private' copy of a certain .NET Framework version (not in GAC), the application vendor will be responsible to update it, unless somehow the admin will have a built-in way to discover all applications that have a certain .NET version..

      Delete

Post a Comment

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

By
After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(
Post a Comment
Read more

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

By
Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see
8 comments
Read more

Navigating Cloud Strategy after Azure Central US Region Outage

By
 Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage.   But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too
Post a Comment
Read more