Well it seems I stand corrected (sort of), and these are rare moments so enjoy it.. *grin*, seems like it was a user error (again sort of - in a minute on that) when I talked about the issues with ClickOnce earlier. The problem there was that the installation can only be supported via http and not using ftp (which I have chosen), once you change it to http you are golden. Moving on, why do I say a user error (sort of)? Well mainly because the Publish Wizard as far as I can see is not very explicit about this and unless you know (which now you do), you will get into this issue.

So my recommendation is not to use the wizard at all but instead go straight to the options page, which not only has more features but also gives you more control. How do you get there? Thought you would never ask. Right-click on your project name in the Solution Explorer and select properties. In the new window select the second last tab on the left called Publish - voila you are there. If you see the screen shot you will notice I have highlighted the urls you need to be careful of. This is where you can add other external dependencies, called Prerequisites (which were not automatically picked up as they are not referenced at design time). Most of the other options are self explanatory.

Also, if you go over the Sandbox to check out the Clock v2.0 (which was recompiled for Beta 2 - no new features other than to get it compiling), and try to install it, you will notice you cannot; instead you would see a funky looking xml (ain’t that funky btw). Well that is because the “.application” MIME type is not registered on the server that hosts this site. Since this is not a dedicated server, I don’t have any control over it and cannot just “switch it on” - I need to open a ticket for that and not sure how that will go. But, till then if you do look at the xml you can find out some of what is under the skin of ClickOnce.