Dime Casts.Net -- Inform and Educate in ~10 Minutes or Less. Using Web Deployment Projects with Visual Studio 2005. Microsoft Corporation November 2005 Abstract Visual Studio 2005 provides deployment support through its Copy Web Site and Publish Web Site features. While these are ideal for many scenarios, there are other, more advanced scenarios where developers need the following capabilities: More control over assembly naming and output. This white paper describes a solution to these advanced scenarios and introduces a new feature called Web Deployment Projects for Visual Studio 2005.
To install the Visual Studio 2005 Web Deployment Projects feature, download and run WebDeploymentSetup.msi. Web Deployment Projects Web Deployment Projects is an add-in package to Visual Studio 2005. A Web Deployment project is an MSBuild project file for a Web site. Web Deployment projects do not change the way Visual Studio 2005 Web site projects build. Feature Summary A Web Deployment project provides the following features for building and deploying ASP.NET 2.0 Web sites: Installing Web Deployment Projects Compilation Page.
Add Sandcastle doc generation to your NAnt builds. Add Sandcastle doc generation to your NAnt builds A critical step in your automated build process is documentation generation. This article explains how to add documentation generation to NAnt scripts using Sandcastle. By: Brett Burch (www.brettresources.net) Date: June 13, 2007 Printer Friendly Version Assuming you have a tree structure as follows, adding automated generation through the September CTP of Sandcastle into your NAnt build process is very painless. I have included the Sandcastle icons, scripts, and styles that come with the download in my CVS tree. There are a few targets that this target requires in addition to the obvious build target. The critical piece which generates the documentation for you (following the build of your source) is the GenerateDocumentation_tokenreplaced.bat file.
Here is that .bat file in its entirety: The change to the sandcastle.config file mentioned comes in line 53 of the sample file, where becomes . (note the file extension change). How to Hook Up a VS.NET 2005 Solution With CruiseControl.NET in a Few Minutes - Johan Danforth's Blog. This is a short "primer" on how to get your CruiseControl.NET (CC.NET) Continuous Integration (CI) Server up and running with a very small configuration, and it will only take you about 5 minutes or so. I’m pretty new to CC.NET so I thought I would share some of the stuff I learned about it when setting it up. I've used it before, but that was some time ago and now I’m planning on using it for an upcoming project so I had to brush things off and see what had changed lately.
I’m listing some NAnt resources as well here, even though I’m not covering NAnt now (but probably will in a future update). If you want to read about NAnt and CC.NET, Joe Field got a great article on it, and I'm sure there are other CC articles out there. Updates Nov 25, 2006 - Added information about how to use msbuild.exe and a small sample configuration. Why CruiseControl.NET? So why would you like to use something like CruiseControl.NET? Tools and Products I'm using these tools and products: Resources Download Installing. Manish Agarwal : MSbuild tasks to integrate/customize Team Foundation Version Control functionality with Team Build.
Instrumental Services Inc. Fear and Loathing : MSBuild, NAnt, NUnit, MSTest, and frustration. Oh bother. Visual Studio 2003 and Cruise Control.NET. Simple and elegant. A basic NAnt script to build the solution and you're good to go. Run NUnit, output goes to a format CC can understand and Bob's yer uncle. Let me quantify this. Enter Visual Studio 2005.
Msbuild /t:rebuild solutionname.sln (or whatever target you want like Debug or Release) Like I said, if that's all it was no problem but it gets real ugly real fast. First there's VSTS unit test projects. <msbuild> <executable>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe</executable> <workingDirectory>D:\ccnet\projects\ProjectName</workingDirectory> <projectFile>SolutionName.sln</projectFile> <buildArgs>/noconsolelogger /p:Configuration=AutomatedBuild /v:diag</buildArgs> <targets>Build</targets> <timeout>600</timeout> <logger>C:\Program Files\CruiseControl.NET\server\ThoughtWorks.CruiseControl.MsBuild.dll</logger></msbuild> Remember that I said this sever did not have Visual Studio installed. It's ugly. Grrr. Using CruiseControl.NET with MSBuild - CruiseControl.NET.
CruiseControl.NET includes an MSBuild Task to integrate MSBuild (.NET 2.0) projects. The MsBuild Task page is the reference for the task, so that will always contain the most up-to-date documentation, but this page acts as a tutorial. Decide what to build Normally, you'll want to build your project's solution file, but you may want to build a specific project file instead. You'll also need to choose whether you want to build a specific target or not. By default, building your solution with no specific target is the best way to start. In any case, before trying to get CruiseControl.NET to work, make sure you can run MSBuild manually on the command line on your build server for your desired file/target combination. Once you've done this, move on to the next step. Get the XML Logger CruiseControl.NET uses the XML files produces by various tools in order to produce styled results. Place this dll in your working directory, which will usually be the one where your target file is located.
MSBuild Overview. MSBuild introduces a new XML-based project file format that is simple to understand, easy to extend, and fully supported by Microsoft. The MSBuild project file format enables developers to fully describe what items need to be built as well as how they need to be built with different platforms and configurations. In addition, the project file format enables developers to author re-usable build rules that can be factored into separate files so that builds can be performed consistently across different projects within their product.
The following sections describe some of the basic elements of the MSBuild project file format. Items Items represent inputs into the build system and are grouped into item collections based on their user-defined collection names. These item collections can be used as parameters for tasks, which use the individual items contained in the collection to perform the steps of the build process. Properties <PropertyGroup><BuildDir>Build</BuildDir></PropertyGroup> Tasks. MSBuild Task Tutorial: Label SourceSafe Project - The Code Project - C# Programming. Introduction While attempting to automate my build process using MSBuild, I have been unable to find a MSBuild Task to label projects in Visual SourceSafe. So, I decided to roll my own using C#. Since you are reading this, you are probably aware that MSBuild is the new build platform from Microsoft.
If you are unfamiliar with MSBuild, check out the list of resources at the bottom of this page for an introduction. Tools Involved During the course of this tutorial, I use the following tools: Visual Studio 2005 Microsoft Visual Studio 2005 Web Deployment Project Microsoft Visual SourceSafe 6.0 MSBuild Step 1: Create your MSBuild Task Project Start by opening Visual Studio 2005 and creating a class library project. Step 2: Add the Label Project Class Create a new class file and name it LabelProject.cs. Add the following code to the LabelProject.cs file: Step 3: Add Necessary References You will need to add two references to your VSSTasks project. In my case, the path to the SSAPI.DLL is: Example:
Practical .NET2 and C#2: An introduction to MSBuild - The Code Project - Book Chapters. Download source - 6.23 Kb Content Introduction The .NET 2 platform is delivered with a new tool named msbuild.exe. This tool is used to build .NET applications. It accepts XML files which describe the sequence of tasks for the build process, in the same spirit as makefile files. Actually, in the beginning of this project, Microsoft had code named the tool XMake. Until now, to construct your .NET applications, you needed to: rither use the Build command in Visual Studio, or use the Visual Studio devenv.exe executable as a command line, or use a third party tool such as the open source tool named NAnt, or even use batch files which called the csc.exe C# compiler. MSBuild aims to unify all these techniques. Building a multi modules assembly without MSBuild Here, we will create an assembly with: A main module .
Place in the same folder both the C# source files (Foo1.cs and Foo2.cs) as well as an image file named Image.jpg. Foo2.cs Foo1.cs Hi from Foo1 Hi from Foo2 .proj files, targets and tasks . Items. Trace of Thought (Scott Colestock) Building and Deploying BizTalk 2006 Solutions with MSBuild. Change is nothing, everything is. » Going agile with Biztalk 2006. Designing a Build System with NAnt. NAnt is a very, very powerful tool. I have previously written about what it does, but I've never really written about how to use it. Like most powerful tools, know how to use it correctly is more important than knowing it exists because you can develop some pretty bad habits if you use it incorrectly. It is easy to fall in love with NAnt's power. You can do everything from checking out source code, creating the AssemblyInfo.cs file, build the code, unit test the code, build documentation from the code, install the code, and finally check the code back in from a single script that is very, very short and simple.
NAnt makes you feel like you can accomplish any build task for any project. And you can! The trick, however, is knowing how to create your build scripts such that they are maintainable by yourself and others. Once you have your targets defined others must know they exist in order to use them. Now we come to the nitty gritty. Now we simply have three files that control our builds: Jean-Paul S. Boodhoo's Blog - NAnt Starter Series. Well, for the last 2 months I have been using Mutt as my primary email client, and I have not missed gmail at all!!
I spend the majority of my day inside a shell based environment, and a large majority of my workflow/tooling has been heavily modded to allow me to do the majority of my computer related activities from a shell. I edit all my code in vimI manage keychain entries using the command line clientsI have a easy to customize automation/expansion library that allows me to add new shell automation tasks easilyFor the rare times that I use twitter, I use a vim plugin for that! I compose blog entries in vim You get the point! I have occassionally messed around with using links as a browser client. In reality, between chrome+vimium or firefox+vimperator, I have my mouseless browsing covered. Focused, specific tools that do one job and do it well This post is mostly for my own journalling purposes, but I am sharing it in the event that it proves useful to others. Getting Started Sending Mail. Managing .NET Development with NAnt.