locked
FAQ: Where is the location of ClickOnce Installation and what are the restrictions of ClickOnce Deployment? RRS feed

  • Question

  • Where is the location of ClickOnce Installation and what are the restrictions of ClickOnce Deployment?


    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.
    Saturday, April 11, 2009 3:38 PM

Answers

  • ClickOnce Deployment will install an application in the user Application Cache per user (not in X:\Programe files\folder) and will be managed by the ClickOnce service.  There is no way you can install it to another folder directly using ClickOnce. This means you cannot change the ClickOnce installation location.

     

    ClickOnce Deployment is excellent, but it's not appropriate for every project. Here are some of the restrictions.

     

    1)    ClickOnce applications are installed for just one user. If several people log onto the same computer with different logins, you have to create an install for each user. You can't install an application for every user on a workstation.

     

    2)    You can't change the way the shortcut is installed using ClickOnce. You can do this using other methods, such as creating a shortcut in the correct folder manually, but you can't get ClickOnce to do it for you.

     

    3)    You can't use ClickOnce to install shared components into the GAC (Global Assembly Cache). In fact, you can't do anything out of the ordinary such as creating a database, registering file types, or configuring registry settings.

     

    ClickOnce Deployment will create a Program Group menu shortcut: "Publisher name" -> "Product name" under Start menu -> All Programs.

    You can change “Publisher name” and “Product name” to whatever you’d desire like this:

    Project Properties -> Publish tab -> "Options..." button

     

    To allow for more flexible and robust configurations and automation requirements than ClickOnce deployment, you can use the Setup Project deployment based on the Windows Installer.

     

    Some tutorials can be found here:

    ClickOnce and Windows Installer Comparison Table

    http://msdn.microsoft.com/en-us/library/142dbbz4.aspx

     

    Choosing a Deployment Strategy

    http://msdn.microsoft.com/en-us/library/e2444w33.aspx

     

    Determining When to Use Windows Installer Versus XCOPY

    http://msdn.microsoft.com/en-us/library/aa302347.aspx

     

     

    For more FAQ about Visual Basic .NET General, please see Visual Basic .NET General FAQ

     

     


    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.
    Saturday, April 11, 2009 3:38 PM