none
Click once deployment & .NET Framework 3.5 SP1 not recognized RRS feed

  • Question

  • Hi,

    we have created a click once setup for our application. Setup checks if .NET Framework 3.5 SP1 is installed already and should continue setup without installing .NET Framework if already installed on the machine. However, this works perfectly on Windows 7 clients. If I start the same setup on a Windows XP client .NET Framework is not recognized even it has been installed before and therefore it is installed again. Reinstalling .NET Framework works, but I want to avoid it if it is not necessary.

    The relevant part of the setup log:
    Running checks for package '.NET Framework 3.5 SP1', phase BuildList
    Reading value 'SP' of registry key 'HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\1031'
    Unable to read registry value
    Not setting value for property 'DotNet35SP'
    The following properties have been set for package '.NET Framework 3.5 SP1':
    Running checks for command 'DotNetFX35SP1\dotNetFx35setup.exe'
    Skipping ByPassIf because Property 'DotNet35SP' was not defined
    Result of running operator 'ValueEqualTo' on property 'AdminUser' and value 'false': false
    Result of running operator 'VersionLessThan' on property 'VersionNT' and value '5.1.2': false
    Result of running operator 'VersionEqualTo' on property 'VersionNT' and value '5.2.0': false
    Result of running operator 'ValueEqualTo' on property 'ProcessorArchitecture' and value 'IA64': false
    Result of checks for command 'DotNetFX35SP1\dotNetFx35setup.exe' is 'Install'
    '.NET Framework 3.5 SP1' RunCheck result: Install Needed

    There are no errors at all. .NET Framework 3.5 SP1 is simply not recognized. Do you have any ideas?

    Thank you for your help!
    Dagmar
    Wednesday, December 9, 2009 12:27 PM

Answers

  • Hi Dagmar,

    Thank you for your post.

    Some clarification with you:
    Have you tried your installer on other XP machine?
    How does your installer check whether .NET Framework 3.5 SP1 is installed or not?

    Generally Speaking, we use "Prerequisite" dialog to set .NET Framework as prerequisite for one installer. It can help developer to automatically install the prerequisite prior to the application.
    For ClickOnce, please right click your project >> go to Properties >> Publish tab >> click "Prerequisites....".
    In the Prerequisites dialog box, you can choose .NET Framework 3.5 SP1.
    You can try this method to deploy your application.

    If the problem still exists, one of possible cause could be that .NET Framework 3.5 SP1 is not well installed on this XP machine. Thus, the installer cannot detect that .NET 3.5 SP1 has been installed and install it again. That's why I would suggest you to try another XP machine to test this installer.

    BTW, This forum is for the support of .NET Framework installation. For your concern on ClickOnce deployment, you also could post your thread on ClickOnce and Setup & Deployment Projects forum. You will get more useful help there. This will make answer searching in the forum easier and be beneficial to other community members as well.

    Thank you for your understanding.

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Wednesday, December 16, 2009 3:05 AM
    Thursday, December 10, 2009 7:48 AM

All replies

  • Hi Dagmar,

    Thank you for your post.

    Some clarification with you:
    Have you tried your installer on other XP machine?
    How does your installer check whether .NET Framework 3.5 SP1 is installed or not?

    Generally Speaking, we use "Prerequisite" dialog to set .NET Framework as prerequisite for one installer. It can help developer to automatically install the prerequisite prior to the application.
    For ClickOnce, please right click your project >> go to Properties >> Publish tab >> click "Prerequisites....".
    In the Prerequisites dialog box, you can choose .NET Framework 3.5 SP1.
    You can try this method to deploy your application.

    If the problem still exists, one of possible cause could be that .NET Framework 3.5 SP1 is not well installed on this XP machine. Thus, the installer cannot detect that .NET 3.5 SP1 has been installed and install it again. That's why I would suggest you to try another XP machine to test this installer.

    BTW, This forum is for the support of .NET Framework installation. For your concern on ClickOnce deployment, you also could post your thread on ClickOnce and Setup & Deployment Projects forum. You will get more useful help there. This will make answer searching in the forum easier and be beneficial to other community members as well.

    Thank you for your understanding.

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Wednesday, December 16, 2009 3:05 AM
    Thursday, December 10, 2009 7:48 AM
  • Thank you for your suggestions and sorry for posting in the wrong forum.

    The setup process behaves exactly the same on every other Windows XP machine.

    Regards,
    Dagmar
    Thursday, December 10, 2009 6:23 PM
  • Hi Dagmar,

    Thank you for your reply.

    Could you please tell me how the installer check whether .NET Framework 3.5 SP1 is installed or not? How you deploy the installer? Have you tried "Prerequisite" dialog to set .NET Framework as prerequisite? Does it work?

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Friday, December 11, 2009 5:49 AM