What are differences between Portable and win-x64 when deploying?
I deploy my code to IIS on Windows Server 2016 and I am trying to understand the effective difference between selecting Portable vs win-x64 in the Publish/Settings/Target Runtime dropdown.
Will the site take longer to start under Portable because the JIT needs to compile the code to the specific architecture? Is there anything else?
Edit - Short Answer
If you choose portable, every time the app starts up it will need to go through JIT compilation on the parts of the application that actually execute. If your application is large, the performance can be impacted.
If you choose x64, the application will not slow down from compilation, because that is already done by the publish process on the build machine (your laptop).
Original Answer
When you choose the Portable publish option, you'll get a package that is capable of running on either x86 (32-bit) machines and x64 (64-bit) machines. With the portable option selected, on application launch you'll get JIT compiled code for the target machine (either x64 or x86) as the application stays running. However, if the application closes, all the code that was JIT compiled would be lost. The compiled code sits in memory until the application process ends. The next run would have to JIT compile the application again as it is used. The advantage here is that you'd only need to distribute one package, and it'll run on both x86/x64 machines.
The alternative is generating multiple packages, one for each target platform you intend to distribute your application on though. In this case, you'll get machine-specific packages that are already compiled, and do not require recompilation even after the application process ends and is restarted later. In this case your application will appear to run faster since the compilation is done once and only once, on the build server / machine. However it does impact your deployment style.
More information on .NET runtime identifiers can be found here: https://learn.microsoft.com/en-us/dotnet/core/rid-catalog
And a good document on JIT compiled code is here: https://www.telerik.com/blogs/understanding-net-just-in-time-compilation
- How to determine if a property is required?
- .NET 4.5 changing how Response.IsRequestBeingRedirected behaves on Ajax calls - why?
- CancellationToken with async Dapper methods?
- How to check if a number is a power of 2
- How to stop Visual Studio from adding IIS Express to launchsettings
- How do I create a generic converter for units of measurement in C#?
- WinUI 3 Community Toolkit: Undefined namespace XAML
- The constraint reference 'string' could not be resolved to a type. (netcoreapp3.0)
- "File Not Found" while trying to compile an RC file (probably dumb mistake)
- Using Snyk Build Task in Azure DevOps Pipeline Error for .Net 8 Project
- How to conditionally use the 'default' color in MAUI?
- Automatically Install Module/Extension in DNN (DotNetNuke)
- Can you explain difference between StrictMock and Partialmock?
- Stubbing a read only property with Rhino Mocks
- Retrieve the current view name in ASP.NET MVC?
- How to Use UnsafeAccessor to Check if Autofac.Core.Lifetime.LifetimeScope IsDisposed in .NET 8?
- How do I convert hexidecimal to decimal using C# & BigInt?
- How do I truncate a .NET string?
- KERNELBASE.dll Exception 0xe0434352 offset 0x000000000000a49d
- .NET MAUI Hybrid Blazor Copy to Clipboard
- How to bind the IsEnabled property to an OR of two values?
- error MSB3073: The command "npm install" exited with code 1
- CSharp Console - Account Login
- EF Core 9 .HasConversion
- How do strings work when shallow copying something in C#?
- How to set the target framework to v2.0 or v3.5 instead of 4.0 when compiling a program from a source file?
- How is it possible to see C# code after compilation/optimization?
- Start exe even with missing dependency dlls?
- Using Action(Of T...) over a custom delegate syntax for readability
- Is C# compiler not reporting all errors at once at each compile?