Tag | ClickOnce Posts

Well, that was certainly annoying. I'm trying to create a new application manifest (deployment manifest), and if I use the -MinVersion (-mv) option as specified in the Mage documentation, it fails with the error, "The minimum version specified is not valid." I'm guessing that this goes hand in hand with the bug that I ran into earlier where you can't do anything but a check after install when using mage. For that defect, I ended up running some code to replace the <expiration maximumAge="0" unit="days" ...
We recently had a defect entered into our defect tracking system. Title: System Error Received when .net framework is not up to dateDescription: The following error is received when using click once and .net framework installation is below the current 3.5. It is thrown on most menu items, but not all. Could not load file or assembly 'System.Core, Version = 3.5.0.0, Culture =neutral, PublicKeyToken=b77a5c561934... or one of its dependencies. The system cannot find the file specified. No, REALLY?? ...
Technorati Tags: ClickOnce,MAGE,Microsoft,.net 3.5 A few days ago I wrote about issues I was having with Mage and click once. Basically, I was always getting the following when I'd try to install the click once application: PLATFORM VERSION INFO Windows : 5.2.3790.131072 (Win32NT) Common Language Runtime : 2.0.50727.1433 System.Deployment.dll : 2.0.50727.1433 (REDBITS.050727-1400) mscorwks.dll : 2.0.50727.1433 (REDBITS.050727-1400) dfdll.dll : 2.0.50727.1433 (REDBITS.050727-1400) dfshim.dll : 2.0.50727.1433 ...
Technorati Tags: ClickOnce,MAGE,.net 3.5,MageUI We've been struggling with ClickOnce using mage.exe and MageUI.exe to manually deploy the application. Since we're doing continuous integration, we need this to work. I've spent 4 hours with MS support trying different combinations of deployment to no avail. We've tried everything. Today, I built a sample application to see if it was our projects or MS. Using Visual Studio 2008, I created a new WPF application and left everything at it's default. The ...
After much frustration, I've finally configured our TeamBuild proj file to publish our ClickOnce app, and increase the version number (kinda an important step). The Vertigo blog talks about using SolutionToPublish, but that doesn't work for all situations. Specifically, when your solution contains projects that reference other projects. So I started playing with the MSBuild Community Tasks Project, and came up with the following Xml for my proj file: This tells the .proj to use the community project:<Import ...
The ToolStripManager is a great way to save the position of toolbars on your WinForm apps. More info here. It works a little bit differently with ClickOnce applications, but it is an easy fix. Just set the key to a unique string. The key would probably have to be unique for the entire machine, but I'm not sure about that. The code looks like this: void formValidateBatch_FormClosi... sender, FormClosingEventArgs e) { ToolStripManager.SaveSettin... ...
Brian Noyes talks about an error that I am going to get when publishing a ClickOnce app from a machine running Vista. When logged in to Vista as an admin, you still won't have full admin rights when running Visual Studio. The short answer is right click on devenv.exe, select properties, select compatibility tab and check "Run this program as an administrator". He goes into more details on the User Access Control (UAC) and when it is appropriate to run with full admin rights. Technorati tags: Brian ...