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

Why Database Modernization Matters for AI

By
  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...
Post a Comment
Read more

How to audit an Azure Cosmos DB

By
In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...
Post a Comment
Read more

[Post Event] Azure AI Connect, March 2025

By
On March 13th, I had the opportunity to speak at Azure AI Connect about modern AI architectures.  My session focused on the importance of modernizing cloud systems to efficiently handle the increasing payload generated by AI.
Post a Comment
Read more