Microsoft Visual Studio 2017 Installer Projects launch condition check not work for .net 4.7.1












4















I am using visual studio professional at version: This version announced as supported .net framework 4.7.1



I installed the Microsoft Visual Studio 2017 Installer Projects extension from the market.



Generate a visual studio setup project to generate MSI for a .net framework windows service console application, inside "Launch Condition" tag, set the .net framework version is target to 4.7.1.



The msi launch check works fine in any system below 4.7 like (4.6.1/4.6/4.5.2....) the launch check will prevent installer to be launched, but in OS system with windows 2012 R2 with .net 4.7 installed, the launch check should expected also as failed. But .net 4.7 pass the launch check and continually launch the installer.



Is anyone facing the same problem and is there a solution for this? I need to support launch check of .net 4.7.1 in my Microsoft Visual Studio 2017 installer project.










share|improve this question

























  • Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

    – Panagiotis Kanavos
    Nov 26 '18 at 12:49













  • I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

    – Krishna Prasad
    Nov 26 '18 at 13:38











  • You asked about Windows 10, not Windows 2012 R2.

    – Panagiotis Kanavos
    Nov 26 '18 at 13:39











  • Appologies, corrected OS version.

    – Krishna Prasad
    Nov 26 '18 at 13:52
















4















I am using visual studio professional at version: This version announced as supported .net framework 4.7.1



I installed the Microsoft Visual Studio 2017 Installer Projects extension from the market.



Generate a visual studio setup project to generate MSI for a .net framework windows service console application, inside "Launch Condition" tag, set the .net framework version is target to 4.7.1.



The msi launch check works fine in any system below 4.7 like (4.6.1/4.6/4.5.2....) the launch check will prevent installer to be launched, but in OS system with windows 2012 R2 with .net 4.7 installed, the launch check should expected also as failed. But .net 4.7 pass the launch check and continually launch the installer.



Is anyone facing the same problem and is there a solution for this? I need to support launch check of .net 4.7.1 in my Microsoft Visual Studio 2017 installer project.










share|improve this question

























  • Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

    – Panagiotis Kanavos
    Nov 26 '18 at 12:49













  • I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

    – Krishna Prasad
    Nov 26 '18 at 13:38











  • You asked about Windows 10, not Windows 2012 R2.

    – Panagiotis Kanavos
    Nov 26 '18 at 13:39











  • Appologies, corrected OS version.

    – Krishna Prasad
    Nov 26 '18 at 13:52














4












4








4








I am using visual studio professional at version: This version announced as supported .net framework 4.7.1



I installed the Microsoft Visual Studio 2017 Installer Projects extension from the market.



Generate a visual studio setup project to generate MSI for a .net framework windows service console application, inside "Launch Condition" tag, set the .net framework version is target to 4.7.1.



The msi launch check works fine in any system below 4.7 like (4.6.1/4.6/4.5.2....) the launch check will prevent installer to be launched, but in OS system with windows 2012 R2 with .net 4.7 installed, the launch check should expected also as failed. But .net 4.7 pass the launch check and continually launch the installer.



Is anyone facing the same problem and is there a solution for this? I need to support launch check of .net 4.7.1 in my Microsoft Visual Studio 2017 installer project.










share|improve this question
















I am using visual studio professional at version: This version announced as supported .net framework 4.7.1



I installed the Microsoft Visual Studio 2017 Installer Projects extension from the market.



Generate a visual studio setup project to generate MSI for a .net framework windows service console application, inside "Launch Condition" tag, set the .net framework version is target to 4.7.1.



The msi launch check works fine in any system below 4.7 like (4.6.1/4.6/4.5.2....) the launch check will prevent installer to be launched, but in OS system with windows 2012 R2 with .net 4.7 installed, the launch check should expected also as failed. But .net 4.7 pass the launch check and continually launch the installer.



Is anyone facing the same problem and is there a solution for this? I need to support launch check of .net 4.7.1 in my Microsoft Visual Studio 2017 installer project.







c# visual-studio visual-studio-setup-proje






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 26 '18 at 13:44







Krishna Prasad

















asked Nov 26 '18 at 12:40









Krishna PrasadKrishna Prasad

393




393













  • Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

    – Panagiotis Kanavos
    Nov 26 '18 at 12:49













  • I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

    – Krishna Prasad
    Nov 26 '18 at 13:38











  • You asked about Windows 10, not Windows 2012 R2.

    – Panagiotis Kanavos
    Nov 26 '18 at 13:39











  • Appologies, corrected OS version.

    – Krishna Prasad
    Nov 26 '18 at 13:52



















  • Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

    – Panagiotis Kanavos
    Nov 26 '18 at 12:49













  • I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

    – Krishna Prasad
    Nov 26 '18 at 13:38











  • You asked about Windows 10, not Windows 2012 R2.

    – Panagiotis Kanavos
    Nov 26 '18 at 13:39











  • Appologies, corrected OS version.

    – Krishna Prasad
    Nov 26 '18 at 13:52

















Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

– Panagiotis Kanavos
Nov 26 '18 at 12:49







Why do you assume 4.7.1 is not installed? Windows 10 continually upgrades itself. Older versions are not supported which means all Windows 10 machines will have 4.7.2 unless an administrator took explicit actions to prevent upgrades. 4.7.2 was added in the Windows 10 April 2018 Update

– Panagiotis Kanavos
Nov 26 '18 at 12:49















I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

– Krishna Prasad
Nov 26 '18 at 13:38





I checked in registry Key path HKEY_LOCAL_MACHINESOFTWAREMicrosoftNET Framework SetupNDPv4Full. the value for the key Release is '460805'. this implies it is .Net framework 4.7.0. The OS version is Windows server 2012 R2.

– Krishna Prasad
Nov 26 '18 at 13:38













You asked about Windows 10, not Windows 2012 R2.

– Panagiotis Kanavos
Nov 26 '18 at 13:39





You asked about Windows 10, not Windows 2012 R2.

– Panagiotis Kanavos
Nov 26 '18 at 13:39













Appologies, corrected OS version.

– Krishna Prasad
Nov 26 '18 at 13:52





Appologies, corrected OS version.

– Krishna Prasad
Nov 26 '18 at 13:52












1 Answer
1






active

oldest

votes


















1














It is happening because Microsoft Visual Studio installer considers only first two digits of version.
To overcome from this situation you can create Launching condition to prevent installer to be launched if required version of .Net framework is 4.7.1 is not installed even 4.7 is installed on machine.



See Defining Launching Conditions section in https://help.sap.com/doc/saphelp_nwgwpam_1/1.0.4/en-US/c5/88c211fa174464800b9d457182e4be/content.htm?no_cache=true






share|improve this answer


























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53481340%2fmicrosoft-visual-studio-2017-installer-projects-launch-condition-check-not-work%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    It is happening because Microsoft Visual Studio installer considers only first two digits of version.
    To overcome from this situation you can create Launching condition to prevent installer to be launched if required version of .Net framework is 4.7.1 is not installed even 4.7 is installed on machine.



    See Defining Launching Conditions section in https://help.sap.com/doc/saphelp_nwgwpam_1/1.0.4/en-US/c5/88c211fa174464800b9d457182e4be/content.htm?no_cache=true






    share|improve this answer






























      1














      It is happening because Microsoft Visual Studio installer considers only first two digits of version.
      To overcome from this situation you can create Launching condition to prevent installer to be launched if required version of .Net framework is 4.7.1 is not installed even 4.7 is installed on machine.



      See Defining Launching Conditions section in https://help.sap.com/doc/saphelp_nwgwpam_1/1.0.4/en-US/c5/88c211fa174464800b9d457182e4be/content.htm?no_cache=true






      share|improve this answer




























        1












        1








        1







        It is happening because Microsoft Visual Studio installer considers only first two digits of version.
        To overcome from this situation you can create Launching condition to prevent installer to be launched if required version of .Net framework is 4.7.1 is not installed even 4.7 is installed on machine.



        See Defining Launching Conditions section in https://help.sap.com/doc/saphelp_nwgwpam_1/1.0.4/en-US/c5/88c211fa174464800b9d457182e4be/content.htm?no_cache=true






        share|improve this answer















        It is happening because Microsoft Visual Studio installer considers only first two digits of version.
        To overcome from this situation you can create Launching condition to prevent installer to be launched if required version of .Net framework is 4.7.1 is not installed even 4.7 is installed on machine.



        See Defining Launching Conditions section in https://help.sap.com/doc/saphelp_nwgwpam_1/1.0.4/en-US/c5/88c211fa174464800b9d457182e4be/content.htm?no_cache=true







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Dec 18 '18 at 3:54

























        answered Dec 17 '18 at 11:06









        Girish NegiGirish Negi

        113




        113
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53481340%2fmicrosoft-visual-studio-2017-installer-projects-launch-condition-check-not-work%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Ottavio Pratesi

            Tricia Helfer

            15 giugno