When I publish an application with ClickOnce, it always builds based on the
active configuration in my Visual Studio environment.  Is there any way to
force ClickOnce to always build the Release configuration before deploying
the application?

Garbage collection and async operations
VSNET: Problems adding VS 2005 extensions for .Net 3.0
VB vs. C# language challenge question
Split .NET exe file into many smaller ones
Block WM_MOUSEACTIVATE messages