The Curious Engineer

All blogs / Dev tools / editors / IDEs

Windows Installer MSI & Clickonce issues

learn.microsoft.com/en-us/archive/blogs/msiclickonce

Dev tools / editors / IDEsC# / .NETMicrosoft blogsMSDN archive

’10’15’20’25
Posts
34 from 17 Jul 2009 to 3 Aug 2010
Posting
archived, read-only
Kind
personal blog
Feed
https://learn.microsoft.com/en-us/archive/blogs/msiclickonce/feed.xml

2010 6

  1. VS2010 Setup project - Migration from VS2008 does not work with Upgrades
  2. ClickOnce - .net 4.0 errors: "Deployment manifest is not semantically valid" and "Deployment manifest is missing <compatibleFrameworks>"
  3. ClickOnce - File accociations are lost upon progrmmatic updates to ClickOnce on Win 7 X64
  4. VS Setup project - vsdraCOM sets codebase in registry to point to the SourcePath
  5. VS Setup project - Pass Checkbox properties as arguments to MSI during silient installations
  6. ClickOnce -- TargetFrameworkVersion

2009 28

  1. MSI: Using regasm to register COM may cause resiliency during application launch
  2. Windows Installer 4.0 - MSI that installs data files under System Protected folders does not remove files upon uninstall.
  3. MSI: Unable to elevate an uninstallation via ARP in Vista
  4. Native Custom action dll fails to build on x64
  5. Per-User installation of an MSI as standard user on Vista is installing files into Administrators profile
  6. MSI: About the Uninstall Registry Key, WindowsInstaller Value
  7. How to make ClickOnce work over SSL requiring client certificates
  8. How to build an MSI to deploy ActiveX control
  9. How to disable the default Launch condition for the .Net Framework in a Visual Studio Setup and Deployment project.
  10. ClickOnce Publish Error: "Cannot continue. The application is improperly formatted. Contact the application Vendor"
  11. ClickOnce:VS08 SP1 XML serialization assemblies not publishing
  12. ClickOnce Application Security Settings
  13. How to add a .net dll within your application setup (Windows Installer Package) using Visual Studio 2005/2008
  14. Web Setup (Windows Installer) project created in Visual Studio fails on a Windows 2003 Server
  15. Advertised COM add-in won't trigger on-demand install if you want to deploy the Add-in with the following conditions (HKEY_USERS + COM Add-in + managed desktop<non admin privileges>
  16. While clicking on “Calculate Permissions” button after including “WebPermission” for a partial trust application, prompts a message box “This application requires full trust to run correctly. Would you like to set this as a full trust application?”
  17. After successfully publishing a ClickOnce application, when you try to install the application you receive an XML page on the browser window as IE opens the Application Manifest
  18. How to change the size of the ClickOnce cache and how roll back occurs in ClickOnce
  19. This advertised application will not be installed because it might be unsafe. Contact your administrator to change the installation user interface option of the package to basic
  20. Why shouldn’t we create manual Shortcuts for apps which are deployed via ClickOnce?
  21. Using MSM from Security update 971090 and 973673 as prerequisite to create MSI, minor update would not work
  22. Visual studio only allows Product Version Property format in form of ##.##.#### only. For forth field it would give Build error for setup Project
  23. MSI patch created using Patchwiz version 3.0 may fail on Windows Installer 4.5 or behave differently
  24. How to sign the BootStrapper when modifying the URL in the .application file when Manually Deploying a ClickOnce Application that Does Not Require Re-Signing and that Preserves Branding Information.
  25. Web setup Package: fails while executing WEBCA_EvaluateURLsNoFail custom action
  26. Clickonce application fails after changing Configuration file and resigning the manifest
  27. This operation has been cancelled due to restriction in effect on this computer. Please contact your system administrator. Click ok
  28. Unable to install or run the application. The application requires that assembly <Assembly Name> Version 8.0.0.0 be installed in the GAC Assembly Cache first. Please contact your system administrator.