VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

ScottGu — Fri, 12 Jan 2007 07:40:34 GMT

Hi Andrew,

Can you send me an email with more details about this issue? I can then loop you in with someone on my team to help.

Thx!

Scott

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

Andrew — Wed, 10 Jan 2007 22:33:13 GMT

I love the fact that Web Application Projects are back, however it has caused somewhat of a problem for me.

With Web Site Projects I've been using CruiseControl.Net to continuously build to a dev server. This was working superbly as all the files I wanted to deploy were put into a folder under a PreCompiledWeb folder, however with Web Application Projects I have to Publish in order to get the same result.

The problem is when I try to Publish from the command line, I get an error:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets(3150,9): error : A signing key is required in order to publish this project. Publishing from Visual Studio 2005 will automatically configure a signing key for this project.

I tried creating an snk for the project but it didn't help. Any ideas?

Regards,

Andrew.

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

John — Sat, 15 Jul 2006 15:47:00 GMT

I too would love to use MSBuild but unfortunately have to build solutions containing setup (deployment) projects. Currently we run devenv from the cmd line but I would like to invoke it from an ASP.NET webservice. Even in cmd line mode devenv seems to want to interact with the desktop and I havent been able to figure out a way to get it to work from ASP.NET. It doesnt seem to work with NT AUTHORITY\NETWORK SERVICE and changing the user/password of the ProcessStartInfo causes some incompatibility with the winstation/desktop. Im open to (and tried)pinvoke'ing win32 apis (createprocesswithlogon,etc) to get access to desktop settings but still havent figured out the magic juju. CC.NET et al seem to sidestep this issue by running their own webservers which I dont want to do. Anyone had any luck launching devenv or any other desktop interacting app from asp.net? thanks -john

Link Listing - June 10, 2006

Christopher Steen — Sun, 11 Jun 2006 03:13:46 GMT

**NOW AVAILABLE** MOSS ECM Starter Kit for B2 (white
papers, code samples, workflows, and VS...

About MSBuild

Andrew Connell [MVP MCMS] — Mon, 05 Jun 2006 13:19:37 GMT

Interesting Finds: June 3, 2006 AM edition

Jason Haley — Sat, 03 Jun 2006 14:59:01 GMT

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

Joe — Sat, 03 Jun 2006 10:34:20 GMT

> I'll follow up with that team to see what the plan is for setup going forward.

Thanks. If there are any plans in this area it would be nice to see a post describing them.

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

Dr.NETjes — Fri, 02 Jun 2006 21:45:12 GMT

Good point! My team is also using the VS2005 Web Application Project to be able do continuous integration with CCNet.

CCNet basically calls a NAnt scripts, which calls MSBuild to build the solution files. Works great!

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

ScottGu — Fri, 02 Jun 2006 21:15:45 GMT

Hi Val,

We are looking at possibly adding the web application project option to Visual Web Developer Express for the next release. There are some technical reasons why it doesn't work today (the VWD express product doesn't support class library projects, which the web application project option depends on).

Hope this helps,

Scott

re: VS 2005 Web Application Projects, MSBuild, and Continuous Integrations

ScottGu — Fri, 02 Jun 2006 21:13:50 GMT

Hi Impu,

When you say "ready for VB Express" are you referring to the VS 2005 Web Application Project option or MSBuild support in general? Note that MSBuild support is there now -- the VS 2005 Web Application Project option only supports VS Standard and higher currently, although we are looking at possibly adding it to the express SKUs in the next release too (along with the web site option).

Thanks,

Scott