![]() ![]() In 3.* onwards you can also target multiple runtimes, e.g. (you could try copying one over from an x86 installation and change the file to reference a 6.0.0 framework just for fun, no guarantees) NET App but in practice it internally depends on - but the host doesn't know that until it reads /usr/local/shared/dotnet/shared//5.0.4/.json for example which tells it to also load the other framework. In theory, could ship with all dependencies needed to run a. This is what the muxer looks for (and fails to find) on your local machine. For the App, it requests version 5.0.0 as a runtime. The runtime in your case is actually ASP.NET Core. Until 3.* you could even only target one of them. However, there are actually multiple runtimes and you usually target only one of them. I like to explain it like this: You are always targeting a runtime + version (excluding runtime specifics for a moment). This might have worked with the 1.* versions. It's really annoying that when I want to upgrade framework I cannot not just upgrade my Docker image but have to edit each project file manually as well.īut the final project can still be executed on the 6.0 runtime with the 5.0 assemblies loaded Ideally it should always use the latest installed unless I explicitly specify it otherwise. To be honest I don't even want to specify 5.0. I have only specified 5.0 which to me sounds like specifying which assemblies to load into my app, but the final project can still be executed on the 6.0 runtime with the 5.0 assemblies loaded. I have not specified that anywhere therefore I'd expect the roll forward to happen automatically. NET is not self contained and I need to have the correct runtime installed, but what I don't understand is why my web project has a hard dependency on the ASP.NET 5 runtime. In the csproj so the emitted runtimeconfig.json tells the host to execute the 5.* app on a 6.* framework? Major version roll-forward currently requires explicit opt in. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |