I need a help regarding the .Net client profile configuration designer ,
I installed the Beta version and configured the designer to install mu ClickOnce application and the .Net client profile as prerequest.
I have two main problems :
1. I need to start the ClickOnce application , what should I supply to the Location and Atguments field under the Launch application after installation section ?
2. I noticed , when I install the application , the ClickOnce application is installed and a shourtcut is created on the desktop, but the client cann't recive new updated . I put a new version on my server and the client didn't detect it. When I install the
ClickOnce application without the designer setup , it recives updated normally. I check that the client throws "User has refused to grant required permissions to the application."
How can resolve these problems.
Please your help.
Thanks in advance...
Unfortunately there are some known limitations with the interaction between ClickOnce installation through the bootstrapper and the update functionality provided by the ClickOnce runtime. We have a new May 09 CTP online that has streamlined a few things,
so please give it a try. To answer your questions:
1. We have support to launch ClickOnce applications after installation, but it's not surfaced directly through the UI of the Configuration Designer just yet. Here's the secret sauce to apply: under the ClickOnce package entry in your Chained Installers list,
go to the Install settings tab, Install settings pane and supply as the install argument the following: "/shortcut:%temp%\myapp.appref-ms" (without the quotes). This causes the ClickOnceInstaller executable to emit a shortcut to the specified
location. Then under "Launch application after installation" you can specify %temp%\myapp.appref-ms as the command to run. I hope we can make this easier towards future releases.
2. The underlying problem with deployment of ClickOnce applications through the API used by the ClickOnceInstaller tool is its shortcircuiting behavior for the regular ClickOnce UI experience for updating and such (what I often refer to as the "blinking
wire experience", the ClickOnce dialog you'll likely be familiar with). The idea of this approach to installation is to customize the user experience by providing custom UI during setup; unfortunately it also affects the runtime with regards to update
checking. This said, there's an API you can use to check for ClickOnce updates programmatically, and display your own custom experience UI to ask the user to accept or reject the update. I'll have someone on the team dig up the sample code to accomplish this.
Another option is to just specify the .application URI in the "Launch application after installation" settings. This will cause us to ShellExecute the .application URI, causing the application to get installed with the default ClickOnce user experience,
preserving all regular updating behavior.