I've noticed a lot of specific shortcommings with regard to creating redistributable ClickOnce applications for local installation on customer servers in a way that the app can be slightly customized with regard to product name and such without requiring a lot jumping through flaming loops to get it to work. Most of this relates to capabilities of Mage and MageUI, the Visutal Studio publish process, the APIs under Microsoft.Build.Tasks.Deployment.ManifestUtilities, and ClickOnce in general.

At this point we have bought into the idea of using ClickOnce assuming that it was going to become more mature over time and that the kinks would be worked out so I guess I'm looking for a little assurance that it isn't stagnating and that some of the communities concerns and needsare being addressed.

I originally asked this question on the CTP forum but that has been closed and there were no real detailed responses. For completeness you can find the original link to that post below.

http://social.msdn.microsoft.com/Forums/en-US/vs2010ctpsupport/thread/e5204d49-d926-41d8-9e1b-cd3c20d17fe7

For more specific details about some of the kinks I'm referring to just look around for ClickOnce posts on these MSDN forums or take a look at the following threads that I've been following as they relate to issues that have affected us in our efforts.

Creating the bootstrapper exe

Cannot specify product name with "Use application manifest for trust information" option

Modify Bootstrapper URL of signed setup quietly or create unsigned bootstrapper

ClickOnce with bootstraper setup.exe need to change URL without any build

ClickOnce & product description

Publishing a program. How do I get my company name ect. to show up in the shortcut in start menu?

Modify setup.exe?

Passing URL parameters to Bootstrapper