ClickOnce fixes in VS2005 SP1
|
I finally noticed that Service Pack 1 for Visual Studio 2005 corrected two of the problems that I've mentioned in previous articles and blog posts about ClickOnce. 1) Application Icon is now included! I learned in the MSDN forums that you can modify the manifest manually to put in the correct xml tags. But this was a pain. It required building the manifest, editing it in notepad and then signing it again. Now the xml is included in the manifest by ClickOnce. 2) I use MAGEUI to build my app manifest, but there was a bug in the original version. Whenever you asked it to populate the manifest with the files in your deployment folder, it would run through the files and then MAGEUI would shut down. Then I had to restart mageui and the file population process. It always worked the 2nd time.
Now it always works the first time! Thanks to whoever fixed those little nits. |
Comments (4)
I know this is slightly off topic, but can someone enlighten me as to what benefits using MageUI offers versus the publish option from inside Visual Studio? I�ve had issues with publish getting confused about my certificate with the only resolution (that I�ve found) being creating a new certificate. I�m curious if MageUI handles this better.
Posted by turner | April 10, 2007 9:59 AM
the MAGE tool (command line or UI) give you more granular control about how your manifest is built. The wizard is great gets you a good part of the way but if you want to do more complex stuff, it's not enough. For an example of how/why I'm using the MAGE tools, check out my CoDe mag article which is the "articles" hyperlink above.
Not sure what problems you are having with certs. THe mage tool lets you choose what certificate to use.
Posted by Julie | April 10, 2007 11:40 AM
Sorry, but ClickOnce is still useless until it supports Firefox.
Posted by Joe | April 23, 2007 2:39 PM
Joe
According to Surabh Pants' "Smart Client: Whats new in Orcas?" presentation [http://blogs.msdn.com/saurabh/archive/2007/03/26/smart-client-whats-new-in-orcas.aspx], ClickOnce will work "out of the box" in FireFox in the Orcas version of Visual Studio. In case you haven't seen this (year old) post of his about ClickOnce and FireFox workarounds it's here: [http://blogs.msdn.com/saurabh/archive/2006/03/02/541988.aspx]
Posted by Julie | April 23, 2007 3:14 PM