3 ms·
yes this would be interesting. We have application severs with multiple windows apps running on them with different versions of the .Net framework. I had to p
by ropman76 12y ago
yes this would be interesting. We have application severs with multiple windows apps running on them with different versions of the .Net framework. I had to pull teeth with our SysAdmin to get the .Net upgraded on the server. It would be nice to have a container for each so I (as a dev) could run the each app with it's own needed dependencies instead of having to install them on the server.
- ghuntley 12y agoThis is already happening in .NET land independently of this announcement. ASP.NET vNext Katana (1) completes the move away from a perspective monolithic framework and instead individual NuGet packages. Ie - when you deploy your app you deploy your assemblies and into that folder goes everything needed to run the app independently, including and up to .NET core assemblies or BCLs. Your app is a folder and that folder contains everything needed to run the application even up to the point of self-hosting with OWIN - IIS is not needed anymore! (1) http://www.asp.net/aspnet/overview/owin-and-katana/an-overview-of-project-katana http://www.asp.net/aspnet/overview/owin-and-katana/an-overvi...