Skip to content

Codepolice

  • ⤫

Finally have Subversion + CruiseControl.NET + MSBuild running

Posted by Judy Alvarez Posted on February 25, 2022March 1, 2022
0

I’ve been struggling the whole afternoon to get some kind of continuous integration up and running. It started with that I got sick and tired of the Publish feature in Visual Studio 2008 because it just starts to fail from time to time and it’s kind of impossible to find out why because it doesn’t give any kind of error information.

Anyway, I started to look at MSBuild and see if it could handle my Publish task and I found this great article. It explains how to make a build file that builds your project and then also simulates the publish feature and puts just the files necessary into a separate folder.

While I was on the subject I thought that I could as well see if I could set up my source control machine to build my app as soon as I check in some files, copy the build to a folder and make that folder a web application.

It actually was kind of easy. I found an article by Omar Al Zabir that explains this in great detail.

Not any problem at all?

Of course. The one I had the most problem with was the infamous Microsoft.WebApplication.targets bug. When you build your project on the build machine you get this error.

error MSB4019: The imported project “C:Program FilesMSBuildMicrosoftVisualStudiov9.0WebApplicationsMicrosoft.WebApplication.targets” was not found. Confirm that the path in the <Import> declaration is correct and that the file exists on disk.

I have had this problem before when we migrated a “Website” to a “Web application project” at my last job. What I remembered from it was that you had to copy the file Microsoft.WebApplication.targets from its location on your dev machine to the build machine. Well fine. The problem in my case was that the file already was there. I looked around for maybe an hour or until i realized that the path on my build machine was:

C:Program FilesMSBuildMicrosoftVisual Studiov9.0WebApplicationsMicrosoft.WebApplication.targets

While on my dev machine it was:

C:Program FilesMSBuildMicrosoftVisualStudiov9.0WebApplicationsMicrosoft.WebApplication.targets

Notice the difference? Don’t you just love Microsoft sometimes .. just copy the path and remove the space from “Visual Studio” and it works.

That was actually the only major problem I had. Otherwise, I used my brain and the articles I linked to and everything is a happy puppy.

Thanks and good night.

Categories: JavascriptTagged: asp net architecture, asp net cms, asp net control, asp net core authentication, asp net core download, asp net core hosting, asp net core signalr, asp net core vs asp net mvc, asp net developers, asp net gridview, asp net interview questions for 3 years experience, asp net logo, asp net mcq, asp net mvc life cycle, asp net upload file, asp net vs node js, asp net web api tutorials, asp net web application, crud operation in asp net mvc with entity framework, features of asp net, fileupload asp net, free asp net hosting, microsoft asp net, mvc asp net interview questions, mvc in asp net, session state in asp net, sessionstate in asp net, state management techniques in asp net, upload file asp net, web forms asp net

Post navigation

Previous Previous post: Group By with LINQ
Next Next post: Problems with Dean’s Permalinks Migration after WordPress 

Related Posts

  • What’s next for JavaScript frameworks in 2026

    #​770 — January 27, 2026 Read on the Web JavaScript Weekly Introducing LibPDF: PDF Parsing and Generation from TypeScript — LibPDF bills itself as ‘the PDF library TypeScript deserves’ and supports parsing, modifying, signing and generating PDFs with a modern API in Node, Bun, and the browser. GitHub repo. Documenso JavaScript Frameworks – Heading into 2026

    Posted by Posted on January 27, 2026
    0
  • require(esm) now stable in Node 25

    #​608 — January 22, 2026 Read on the Web Node.js 25.4.0 (Current) Released — Another gradual step forward for Node with require(esm) now marked as stable, as well as the module compile cache, along with a variety of other minor tweaks. Joyee Cheung of the Node team has written a thread on Bluesky going deeper

    Posted by Posted on January 22, 2026
    0
  • A big week for jQuery

    #​769 — January 20, 2026 Read on the Web JavaScript Weekly jQuery 4.0 Released — 20 years on from its original release, the ever-popular (in terms of actual usage) library reaches 4.0 with a migration to ES modules (compatible with modern build tools) along with dropping support for IE 10 and older. With jQuery being

    Posted by Posted on January 20, 2026
    0
  • A new guide to configuring Node packages

    #​607 — January 15, 2026 Read on the Web ⚠️ The Node.js January 13, 2026 Security Releases — Originally expected in December, these releases (of Node.js 25.3.0, 24.13.0, 22.22.0, and 20.20.0) finally landed this week, largely due to their complexity and the scope of the vulnerabilities they tackle. More on that in the next item! The Node.js

    Posted by Posted on January 15, 2026
    0
  • Can we ever fix the web dependency mess?

    #​768 — January 13, 2026 Read on the Web JavaScript Weekly Web Dependencies are Broken; Can We Fix Them? — Lea, who has worked at the heart of Web Standards for years, delivers a compelling (and educational) call to action about a problem every JavaScript developer has encountered: why is managing dependencies and introducing them

    Posted by Posted on January 13, 2026
    0
  • The story of how require(esm) became stable

    #​606 — January 8, 2026 Read on the Web 🎉 Happy New Year! Also, a quick reminder that Node Weekly is now sent every Thursday as part of a reshuffle for many of our newsletters. __Your editor, Peter Cooper npm to Implement ‘Staged Publishing’ After Turbulent Shift Off Classic Tokens — 2025 was a tricky year

    Posted by Posted on January 8, 2026
    0
Judy Alvarez

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Codepolice

  • Github
  • Atlassian
  • Flatlogic
  • Xero
  • Jetbrains
  • Figma
  • What’s next for JavaScript frameworks in 2026
  • require(esm) now stable in Node 25
  • A big week for jQuery
  • A new guide to configuring Node packages
  • Can we ever fix the web dependency mess?
https://flatlogic.com/generator
COPYRIGHT © 2026 - Codepolice