If you build ClickOnce deployments, you have probably noticed the lack of tools available to help you. Visual Studio and Mage only meet basic requirements and provide some support to automate the build process. ClickOnceMore plugs gap in your development process, which allows you to easily create and deploy ClickOnce manifests in the construction process and your development framework.
ClickOnceMore provides a development environment simple and intuitive for your deployment. Use the user interface of the project editor to set all the parameters of your ClickOnce manifests and withdraw to files from anywhere in your system.
No batch file more copy all of your output to a single location and then manually run Mage to put in place the deployment.
No batch file more copy all of your output to a single location and then manually run Mage to put in place the deployment.
Use instead the editor in Chief of project to define rules of inclusion which may, for example, include all the DLLs in a directory and all the xml files on the other; or use an exclusion rule to take everything in a directory, except the pesky pdb files that creates Visual Studio.
Once you have defined your ClickOnceMore project, it can easily be integrated into Visual Studio using a build step post to fire off the coast of the command line tool that can build the projects that you have defined in the project editor. Then, you will simply need to click once in Visual Studio for a new deployment containing all your binaries to update.
Command line tool easily integrates with you build process regular, so that you always have a day for you deployment testers and QA to install staff.
Here are a few "clickoncemore key features.
· Windows application to create ClickOnce installation projects
· Line tool command to integrate the building ClickOnce manifests in your development and build process
· Specify the exact files, or use include and exclude rules to specify the type of files you want in your application deployed
· Rules to ensure that the new files get dragged in your build automatically, do need to edit the project each time you add a new Assembly
· List of included files allows to easily see your rules files are dragging in
· Specify the installation directories to create a specific folder on the end user's machine
· Pull files from several directories, that does is not limited to a single root as MAGE folder
· Full support of the characteristics of the range of ClickOnce, including updates, the preconditions and the levels of confidence
· Auto increment version on each generation number, or specify an exact version number
· According to the project approach allows an easy integration with source control to support the development of the team
· User project options allow each developer working in their own preferred way
· Specify your own template to publish, or use our default one
· Line tool command to integrate the building ClickOnce manifests in your development and build process
· Specify the exact files, or use include and exclude rules to specify the type of files you want in your application deployed
· Rules to ensure that the new files get dragged in your build automatically, do need to edit the project each time you add a new Assembly
· List of included files allows to easily see your rules files are dragging in
· Specify the installation directories to create a specific folder on the end user's machine
· Pull files from several directories, that does is not limited to a single root as MAGE folder
· Full support of the characteristics of the range of ClickOnce, including updates, the preconditions and the levels of confidence
· Auto increment version on each generation number, or specify an exact version number
· According to the project approach allows an easy integration with source control to support the development of the team
· User project options allow each developer working in their own preferred way
· Specify your own template to publish, or use our default one
Requirements:
· NET Framework
Limitations:
· 14-day trial
What's new in this version:
· Error handling improved when you create the output directory.
· New option to use the name of the application as the identity field in the .manifest file. This allows you to create separate ClickOnce. packages based on the same executable file, without having to change the name of the executable file each time.
· New option to use the name of the application as the identity field in the .manifest file. This allows you to create separate ClickOnce. packages based on the same executable file, without having to change the name of the executable file each time.
NOTE: You are now downloading a Trial version of ClickOnceMore. This download is provided to you free of charge.
0 comments:
Post a Comment