![]() ![]() However it does impact your deployment style. In this case your application will appear to run faster since the compilation is done once and only once, on the build server / machine. 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. ![]() The alternative is generating multiple packages, one for each target platform you intend to distribute your application on though. The advantage here is that you'd only need to distribute one package, and it'll run on both x86/圆4 machines. The next run would have to JIT compile the application again as it is used. The compiled code sits in memory until the application process ends. However, if the application closes, all the code that was JIT compiled would be lost. WinRAR is a Windows data compression tool that focuses on the RAR and ZIP data compression formats for all Windows users. With the portable option selected, on application launch you'll get JIT compiled code for the target machine (either 圆4 or x86) as the application stays running. When you choose the Portable publish option, you'll get a package that is capable of running on either x86 (32-bit) machines and 圆4 (64-bit) machines. If you choose 圆4, the application will not slow down from compilation, because that is already done by the publish process on the build machine (your laptop). ![]() If your application is large, the performance can be impacted. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |