ClickOnceMore enables a smoother ClickOnce build and deployment process by offering a project based approach to creating and building you ClickOnce manifests.
Version: 2.8If you're building ClickOnce deployments, then you've probably noticed the lack of available tools to help you.
License: Free To Try $50.00
Operating System: Windows
Visual Studio and Mage only cater for basic requirements and provide little support for automating the build process.
ClickOnceMore plugs that gap in your development process, allowing you to easily create and deploy ClickOnce manifests as part of your development and build process.
ClickOnceMore provides a simple and intuitive development environment for your deployment.
Use the Project Editor UI to define all of the settings for your ClickOnce manifests and to pull in files from anywhere in your system.
No more batch files to copy all of your output to one location and then manually running Mage to set up the deployment.
Instead use the Project Editor to define inclusion rules that can, for example, include all the DLLs in one directory and all the xml files from another; or use an exclusion rule to take everything from one directory, except those pesky pdb files that Visual Studio creates.
Once you have defined your ClickOnceMore project it can easily be integrated with Visual Studio using a post build step to fire off the command line tool which can build the projects you defined in the project editor.
Now you only have to click once in Visual Studio to get a new deployment with all of your up to date binaries in it.The command line tool integrates easily into you regular build process, so you always have an up to date deployment for you testers and QA staff to install.
Version 2.8: 2.8 is a minor update. Support for certificate store. Support for .Net 4.6 and .Net 4.6.1 as pre-requisites. Support for Windows 8.1, Windows 8.1, Update 1 and Windows 10 as pre-requisites. Added additional Display Name field for application. Improved messages and error handling.
Version 2.7: 2.7 is a minor update. Support for .Net 4.5.1 and .Net 4.5.2 as pre-requisites for your application. UI layout improvements. ErrorReportUrl now being set. Addition of 'Processor' as a built in macro value. Application version can now be auto-detected from the main exe. Minor bug fixes.
Version 2.6: Version 2.6 is a minor update to ClickOnceMore:. 1. Support for .Net 4.5 as a pre-requisite for your application. 2. Added legacy support for V2.4 users wishing to continue having an assembly identity without ".application" in name. 3. Better handling of errors deleting old output directory during a build - especially due to permissions.
Version 2.2: Version 2.2 is an update to ClickOnceMore with some great new features:. 1. Optional ClickOnce manifest signing, as supported by Visual Studio. If you don't need the security of signed manifests, . then you don't need to go to the effort of creating a certificate to use. Just deploy your ClickOnce app unsigned. 2. Better handling of duplicate assemblies pulled in by file inclusion rules... catching the duplicates, so that you don't have to! . Leaving you free to concentrate on more important things than ClickOnce!. 3. Support for Registration Free COM. ClickOnceMore will transfer Registration Free COM info from your applications . manifest file into the ClickOnce manifests it creates. 4. New command line options for allowing you to override individual macro values and override many settings at build time. 5. New option to ignore warnings during a build. 6. Several small usability improvements such as options to automatically create missing output directories and to open the . output directory after a successful build. 7. New option to expand macros placeholders in your application config file when deploying your ClickOnce package. 8. You can now specifiy any Windows version as a prerequisite. Select from a preconfigured list of set your own version . number directly. . And a few bug fixes:. 1. Output folders and files now correctly inherit permissions from parent directories. 2. Trust level information now moved correctly to manifest file. 3. Macros placeholders in Application Name now get expanded in description field of .manifest file. 4. Missing project file no longer causes error at start up. 5. Loading relative paths that are simply a macro placeholder (e.g. [output]) no longer causes a path to be appended to the . front. 6. Macro placeholders in path names are now recorded before a 'Browse' and put back afterwards where possible.
Version 2.1: Version 2.1 is a minor update to ClickOnceMore. The main feature of this release is full support for the .Net 4 Framework. There are several other features in this release:. * Full support for .Net Framework 4, including adding it as a prerequisite. * Option to remove the Installation Path from deployment manifest to allow installtion from multiple URLs. * Automatic detection of processor architecture. Particularly helpful for x86 and x64 applications. * Remember user's preference for maximized/normalized window on start up. . And some minor bug fixes:. * .application extension and .exe extensions correctly added to assembly identity in the .manifest and .application files . respectively. * Better handling of errors during build process when trying to determine if an included file is a .net assembly or not. * Application settings files now stored in users profile for smoother operation on Windows Vista and Windows 7.
Version 2.0: Version 2.0 is a major update to ClickOnceMore. With some great new features:. 1. New Macro system. Define macro schemes with different values for different environments (e.g. DEV and PROD). 2. Full support for .Net3.5 ClickOnce features (Desktop Shortcut, File Associations, Installation Error URL, Minimum OS Error . URL, Suite Name). 3. Specify minimum .Net Framework version for target systems. 4. Full product documentation. Summary help on screen and F1 online help available for each screen. 5. Quick start guide. 6. Compatible with 64 bit Windows. 7. Updated user interface.
Version 1.3: Release 1.3 is a minor release containing several important fixes. Most notably:. 1. Read only files being included in a build no longer cause the next build to fail. 2. Files included by an inclusion rule which are picked up from a sub-directory of the rules directory, and which are to be . installed to the same directory on the target, no longer cause erroneous warnings.
Version 1.2: Release 1.2 is a minor release containing several functional changes and bug fixes. 1. Less restricted evaluation version. You can now save projects and evaluate the command line tool. 2. Support for Windows Vista. 3. Compatible with 64 bit OS.
Version 1.1: Release 1.1 is a minor release containing several functional changes and bug fixes. 1 Including the same file by multiple rules no longer causes unhandled error. 2 Deployment URL can be overridden from command line. 3 New option allowing you to set the current version to be the minimum version.