ClickOnce disallow publishing of Debug builds?

One thing you can do is add a condition to the . Csproj or . Vbproj file that MSBuild will check when doing a build.

One thing you can do is add a condition to the . Csproj or . Vbproj file that MSBuild will check when doing a build.

The condition would check if a publish is occurring and check if the build is a debug build, then do something like run an external tool or otherwise interrupt the build process or cause it to fail.

– LnDCobra Mar 16 '10 at 12:52 Have a look at MSBuild conditional examples: msdn.microsoft. Com/en-us/library/ms164307. Aspx – Judah mango Nov 2 '10 at 15:41.

AFAIK ClickOnce is perfectly happy with debug builds. We automate our builds which allows us control over whether we produce the ClickOnce artefacts from release or debug. Maybe this approach would help you?

I've thought about that, but right now it's as simple as clicking on the project and clicking Publish. The only modification to the current project I'd like would be to have it verify that it's not a Debug build. Edit: Also, it's not that ClickOnce isn't happy with a Debug build, but that we use a Debug build to signal the availability of certain debug options.

I have choose other solution, that worked for me: I couldn't change my build proccess. So what I did was to Tools->Customize... and change the text of the action, adding an alert like "Publish CONFIGURE TO RELEASE! ", and placing the Publish button next to the Debug/Release configuration option.It's easy!

With this I reduced considerably the risk of human error. Those buttons should be always together.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.