troubleshooting tips for ClickOnce deployment packages – n3wjack's blog Skip to the content Search n3wjack's blog n3wjack's spurts of the mind and other geeky ramblings Menu say thanks contact & links say hi 📧 my twitter 🐦 me @ mastodon 🐘 posts about stuff I made 🎁 my sound(cloud) 🎶 my programming projects 💻 photographic snaps at @unsplash 📷 rss feed legalese content license (cc) privacy policy Search Search for: Close search Close Menu say thanks contact & links Show sub menu say hi 📧 my twitter 🐦 me @ mastodon 🐘 posts about stuff I made 🎁 my sound(cloud) 🎶 my programming projects 💻 photographic snaps at @unsplash 📷 rss feed legalese Show sub menu content license (cc) privacy policy Categories microsoft programming software tips troubleshooting tips for ClickOnce deployment packages Post author By n3wjack Post date June 15, 2013 No Comments on troubleshooting tips for ClickOnce deployment packages Getting a WPF desktop application deployed from a web server like IIS 7 using a ClickOnce package isn’t a walk in the park I’ve noticed. There are tons of little gotcha’s that stand in the way of your automated ClickOnce application generating script and tips to solve those issues are scattered around the web. Here’s a list of the tips I found and needed to get a working package deployed: To be able to download the ClickOnce package from a web server, the .deploy extension on the package’s files is used to make sure IIS doesn’t block the download because the types are not allowed or unknown (like dll’s, exe’s config files etc). This is to avoid having to add all those file types to the exceptions on the handlers in IIS, which would be a bad idea anyway as you don’t people to be able to download your ASP.NET dll’s anyway. If you don’t have .deploy, you’ll get “file not found” errors from IIS because it refused to allow the file to be downloaded. If you keep getting an error about the application’s entry-point when you download the package, check if your build output has binaries for a mix of platforms. All references should be “msil”. If you see a mix of “msil” and “x86” for the executable or one of its assemblies that could be the issue. You can see that in your manifest file. Fix this by correcting all projects’ build settings in the solution’s configuration manager in Visual Studio. Mage.exe has its limits. Some of the settings in the application file you’ll need to script yourself. For example the auto-update settings, or the mapFileExtensions to download .deploy files. The PowerShell XML type accelerator is great for this. Make sure no manifest or application files are already in the folder you use to create your ClickOnce installer before running Mage. It will result in a non-working installer. Some general troubleshooting tips. You can find some more tips here. Photo by Hugo Chinaglia, cc-licensed. Related ← the best android ftp server app → how to protect your privacy online Leave a Reply Your email address will not be published. Required fields are marked * Comment * Name * Email * Website Notify me of follow-up comments by email. Notify me of new posts by email. Δ This site uses Akismet to reduce spam. Learn how your comment data is processed. fresh posts fastest way to copy photos from a Sony A5100 camera fossil hr collider screen reset inbox clean up tool update WSL setup, tips and tricks electronic music for ukraine using vim to write prose use a single mouse and keyboard to control all your computers Yep. This site also uses cookies and by reading my awesome content you agree to their use. To find out why and how to control them, see the privacy policy © 2022 n3wjack's blog Privacy Policy Powered by WordPress To the top ↑ Up ↑