Search code examples
c#visual-studiowindows-installersetup-deployment

Can't install the project after added Prerequisites NET 4.6


I used Visual Installer project to deploy.

After I added .NET 4.6 components to my project and built it, I didn't got click to install option, to check this in Visual studio.

But after deleting this everything worked again.

enter image description here


Solution

  • Download Prerequisites: I would set the prerequisite to download from the vendor's web site - that is the first option of those 3 in your screen shot - at least in my English Visual Studio Setup Project. I don't read Russian / Cyrillic I am afraid. Those letters really look like an alien language :-).

    Eliminate Embedded Prerequisites (for common runtimes): My rant about including the .NET framework is generally that what you include is 1) outdated in no time with all the security fixes (hence bloating your setup for no reason?) and 2) the new Windows OS versions are including .NET pre-installed outright (albeit perhaps not in the correct version). 3) .NET is also installed via Windows Update now - for home users (eventually, there is some delay in release), and 4) corporate packagers absolutely hate pulling packages apart to remove common runtimes since they have to use standard corporate packages for these runtimes and are not allowed to use the bundled ones. Just a report from those who receive vendor setups. Keep it simple. Prefer to document what your setup does? Providing simple Readme.txt or Deployment Info.pdf is good. Delivering a special setup for corporations and large scale deployment is another good way to do it (just a zip of prerequisites and the actual setup).

    Launch Condition: A simple launch condition telling the user to install the .NET framework and what version might be enough, but maybe your "download from vendor site" is best?


    .NET Runtime: As a side-note - and I guess this is well known for most - just pointing it out to whoever might read this: There have been way fewer versions of the .NET runtime (CLR) than is commonly perceived. There is the framework, and then there is the runtime. Please see .NET expert and overall computer expert Hans Passant's summary here (and the other answers on the page too). One more. Version 1.0 and 1.1 of the CLR would seem to be largely irrelevant by now?

    Alternative Tools: I have long disliked Visual Studio Installer Projects. Just throwing in a link to alternative MSI tools.