none
Windows 7 Client Software Logo Program - Technical Requirements

    Question

  • Technical Requirement 1 in the document "Windows 7 Client Software Logo - Technical Requirements & Program Eligibility" (version 1.8) from http://go.microsoft.com/?linkid=9668061 is

    Clean, reversible, installation

    Applications must properly implement a clean, reversible, installation. The application should be able to roll back the install at failure and restore the machine to its previous state.

    Installation Requirements

    An application installation should never:

    § Force immediate reboot. A reboot should never be the only option at the end of an install or update. Users should have the opportunity to restart later 
    § Be dependent on 8.3 short file names (SFN) 
    § Block silent install/uninstall

    Windows inventory tools and telemetry tools require complete information about installed applications. Application installers must create the correct registry entries to allow successful detection and uninstalls. If you are using an MSI-based installer, MSI automatically creates the registry entries below. If you are not using an MSI installer, the installation module must create the following registry entries during installation:

    § DisplayName 
    § InstallLocation 
    § Publisher 
    § UninstallString 
    § VersionMajor or MajorVersion 
    § VersionMinor or MinorVersion


    My question is whether ClickOnce deployment is consistent with these requirements.
    Thursday, August 13, 2009 2:56 PM

Answers

  • Hello,

    As per my understanding about ClickOnce deployment technology, it enables us to create self-updating Windows-based application and the application must be signed, thus the DisplayName and Publisher information will be provided.

    ClickOnce application is installed to the ClickOnce application cache, which is %userprofile%\Local Settings\Apps (e.g. C:\Documents & Settings\joe\Local Settings\Apps) On Windows XP and %userprofile%\AppData\Local\Apps (e.g. C:\users\joe\AppData\Local\Apps) On VISTA.

    For the UninstallString, ClickOnce application can uninstall through the Control Panel -> Programs and Features, even you can restore to a previous version of the  ClickOnce application. So I think the UninstallString is not a problem.

    VersionMajor or MajorVersion and VersionMinor or MinorVersion, as ClickOnce application support self-updating, the version of the application must be provide.

    Thanks,
    Rong-Chun Zhang



    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, August 14, 2009 9:48 AM

All replies

  • Hello,

    As per my understanding about ClickOnce deployment technology, it enables us to create self-updating Windows-based application and the application must be signed, thus the DisplayName and Publisher information will be provided.

    ClickOnce application is installed to the ClickOnce application cache, which is %userprofile%\Local Settings\Apps (e.g. C:\Documents & Settings\joe\Local Settings\Apps) On Windows XP and %userprofile%\AppData\Local\Apps (e.g. C:\users\joe\AppData\Local\Apps) On VISTA.

    For the UninstallString, ClickOnce application can uninstall through the Control Panel -> Programs and Features, even you can restore to a previous version of the  ClickOnce application. So I think the UninstallString is not a problem.

    VersionMajor or MajorVersion and VersionMinor or MinorVersion, as ClickOnce application support self-updating, the version of the application must be provide.

    Thanks,
    Rong-Chun Zhang



    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, August 14, 2009 9:48 AM
  • Hello,

    I am writing to check the status of the issue on your side. Would you mind letting me know the result of the suggestions? If you have any additional question, welcome to post here.

    Have a great day!

    Thanks,
    Rong-Chun Zhang
    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.
    Thursday, August 27, 2009 9:24 AM
  • Update: posted this as a separate question.

    Hi,

    wanted to chime in on this thread. We're now testing a plain .Net WinForms application (called 4RifBatch) distributed via Clickonce for Windows 7 compatibility. In the Windows 7 Software Logo Kit report we get several warnings related to ClickOnce technicalities.

    My question is, should all these test cases pass or are these warnings that should be "ignored"?


    Test case: Write appropriate Add/Remove Program values.: PASS WITH WARNINGS
    WARNING: Applications are expected to create these registry entries DisplayName, IsntallLocation, Publisher, UninstallString, VersionMajor*, and VersionMinor*.
    This application did not create the following registry entries:
    • Value InstallLocation missing for program 4RifBatch.
    • Value VersionMajor missing for program 4RifBatch.
    • Value VersionMinor missing for program 4RifBatch.
    • Value MajorVersion missing for program 4RifBatch.
    • Value MinorVersion missing for program 4RifBatch.


     
    Test case: Install to Program Files.: PASS WITH WARNINGS
    WARNING: This application wrote the following files to a location other than %ProgramFiles%:

      • Program 4RifBatch fails due to missing install location.


    Test case:
    Do not write to the %USERS% folder.: PASS WITH WARNINGS
    WARNING: Application failed multiuser session compliance check.

      • File C:\USERS\...\APPDATA\ROAMING\MICROSOFT\WINDOWS\START MENU\PROGRAMS\4SUBSEA\4RIFBATCH.APPREF-MS was written to an incorrect location.

    Test case: Multi User session test.: PASS WITH WARNINGS
    WARNING: Application invocation in multiple sessions failed.

      • Application fails due to no shortcuts.


    Test case:
    Multi User Check Logs: PASS WITH WARNINGS
    WARNING: Application failed multiuser session compliance check.


    - Peter - http://www.demicode.com
    • Edited by Peter Lillevold Tuesday, September 29, 2009 7:05 AM moved to separate thread
    Monday, September 28, 2009 1:00 PM