Customizing and building the ClickOnce deployment package
|Article:HOWTO58559|||||Created: 2011-08-01|||||Updated: 2013-07-12|||||Article URL http://www.symantec.com/docs/HOWTO58559|
The Compliance Accelerator ClickOnce package comes with a file called
GenerateClickOnce.msbuild, which you can customize to suit your environment. For example, this file lets you specify the IIS Server address from which users can run the installation. You can also choose whether an installed Compliance Accelerator client should perform an update check at start-up.
After you have set your preferred configuration options in the file, use the MSBuild engine to build the final deployment package. This engine is included in .NET Framework 2.0 and later.
To customize and build the ClickOnce deployment package
Copy the files from the following folder in the release media to a new folder on your local drive:
..\Symantec Enterprise Vault Compliance Accelerator version\Client\ClickOnce\ApplicationFiles
Browse to the new folder in Windows Explorer.
GenerateClickOnce.msbuildfile in a plain text editor such as Windows Notepad.
Modify the following properties at the start of the file:
For example, you can set the properties as follows:
<Thumbprint>df9634cc5e654f07521d11de8bc03d6ed789ef8e</Thumbprint> <OutputPath>\\Server1\WebServer</OutputPath> <DeploymentPath>http://server2/compliance</DeploymentPath> <EnableAutoUpdates>true</EnableAutoUpdates>
Save and close the file.
In Windows Explorer, search the folders under your .NET Framework installation for the file
Open a Command Prompt window.
Change to the folder that contains the most recent version of
MSBuild.exe. For example, you can type the following:
Type the following command:
where path_to specifies the absolute path to the
GenerateClickOnce.msbuildfile. For example, you can type the following:
MSBuild creates the final deployment package in the folder that you specified with the OutputPath property.
Copy the contents of the output folder to the required location on your IIS Server computer.
Article URL http://www.symantec.com/docs/HOWTO58559