What's new in ClickOnceMore 2.8
Dec 1, 2016
- 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.
New in ClickOnceMore 2.7 (Feb 19, 2015)
- 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.
New in ClickOnceMore 2.6 (Dec 20, 2013)
- Support for .Net 4.5 as a pre-requisite for your application.
- Added legacy support for V2.4 users wishing to continue having an assembly identity without ".application" in name.
- Better handling of errors deleting old output directory during a build - especially due to permissions.
New in ClickOnceMore 2.5 (Jan 31, 2013)
- a maintenance release to ClickOnceMore fixing an issue with 2.4 where by ".application" was missing from the . assembly identity name in the deployment manifest causing issues for people upgrading from 2.3 and before
New in ClickOnceMore 2.4 (Nov 20, 2012)
- Ability to treat assemblies as simple files, not assemblies. This can be useful for third party assemblies that contain manifests which confuse ClickOnce.
- File inclusion and exclusion rules no longer case sensitive.
- Read only files included in the build no longer cause build errors.
- Fixed some issues around the user setting folder on Windows 7.
- Changing a macro shceme name no longer detatches values from the scheme.
New in ClickOnceMore 2.3 (May 31, 2011)
- Improved error handling when creating output directory.
- New option to use the application name as the identity field in .manifest file. This allows you to create distinct ClickOnce . packages based on the same executable file, without having to change the name of the executable file each time.
New in ClickOnceMore 2.1 (Jul 15, 2010)
- 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.
New in ClickOnceMore 2.0 (Oct 15, 2009)
- 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.
New in ClickOnceMore 1.2 (Jul 10, 2008)
- Less restricted evaluation version. You can now save projects and evaluate the command line tool.
- Support for Windows Vista.
- Compatible with 64 bit OS.