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 18.104.22.168.0 and Microsoft.AspNet.Hosting 22.214.171.124.
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.