installer - Should I worry about redistributing .NET runtime with my application? -


If possible, with my application. I would like to refrain from redistribution to the NET runtime because it will increase the size of the app, download time, time of development & amp; Will potentially implement several deployment errors? Does Microsoft Force users run .net runtime through updated Windows Update? If not, what are some options to redistribute the NET Runtime? Has Microsoft made it easy to redistribute runtime again? Besides, is the NIT runtime guaranteed to be backward compatible?

I'm just summarizing the answers here. It seems that we must have bootstrapper at least check for the existence of .NET run time. The alternative option is to run a runtime and if it does not exist it is to deploy it. There are many options for packaging & amp; There is also other packaging options like InnoSetup, WIX etc. (not sure which option is better and free) with reboot required for runtime installation and the selected installation option Should restart the application installation post reboot

In addition, Em> should worry about that your application without runtime is mysterious You should never believe that a particular version of the runtime is already installed.

As mentioned above, the installer project wizard will create a setup file in VS that is required only when it is needed. There is a script in NSIS and INO setup that will do the same thing. Note that when you install Runtime, you have to handle reboot-end ------ setup. I believe the installer wizard handles this for you.


Comments

Popular posts from this blog

c++ - Linux and clipboard -

What is expire header and how to achive them in ASP.NET and PHP? -

sql server - How can I determine which of my SQL 2005 statistics are unused? -