Geeks With Blogs
Colin Bowern ... more of the usual bool Build and Deployment Items related to automated build and deployment processes.
Greedy Application Mentality with TFS
I set off intending to experiment with Team Foundation Server recently to potentially replace our Subversion deployment. As I built up my virtual machine for the TFS application tier I went to install the data tier on our beefy 64-bit SQL Server machine and was stopped by a problem: SQL Server 2005 Reporting Services service is installed on the data-tier computer. The service should instead be on the application-tier computer. Uninstall SQL Server 2005 Reporting Services from the data-tier computer ......

Posted On Thursday, June 8, 2006 9:07 PM

Installing with Native Images and Debug Symbols
For some of our projects we're looking to not only deploy assemblies to the GAC, but generate native images and copy the debug symbols to the GAC (which buys us line numbers in exceptions -- it's much easier to debug when you know the line number!). I've been experimenting with the VS2005 Setup Project to try and automate the process. During this experimentation realized a number of short comings: Cannot have an assembly be used as a Custom Action and deployed into the GAC at the same time. Solution: ......

Posted On Thursday, March 23, 2006 9:37 PM

Filtering .NET 1.1 functionality when using MSBuild and MSBee
We try to be good developers and this includes ensuring our warnings are taken care of. A standard part of our debug builds includes treating warnings as errors. When we were faced with migrating a project to a split .NET 1.1/2.0 build using MSBee we found it lacked the introduction of a preprocessor directive that would allow us to make the critical decisions in the code. One example where we needed this information had to do with the C# compiler (CSC) in .NET 1.1 lacking assembly signing options. ......

Posted On Sunday, March 12, 2006 6:49 PM

Suppressing References in Build Output
On our build server we don't have any of our dependent applications (e.g. Commerce Server, BizTalk Server) installed because it's cheaper on the licensing and the build server is actually a Virtual Server image running on my dev box where I don't feel like giving up excess resources to build processes. :) One of the things that has bugged me for a while is the fact that the build process copies referenced assemblies even when Copy Local set to false. We store all of our references on a network share ......

Posted On Sunday, March 12, 2006 1:15 PM

MSTest using a Test List via Command-Line
Converting from NUnit to MSTest I've seem to have hit a little snag. I can't run MSTest on the command line while focusing on a subset of the tests. MSTest introduces the concept of Test Lists which allows me to segregate the tests that will run on the build server versus the ones that require a development machine or test environment for smoke testing. It seems when you run the command line with the specified test list: mstest /testmetadata:tests.vsmdi /runconfig:localtestrun.tes... /testlist:BuildVerification... ......

Posted On Sunday, March 12, 2006 12:59 PM

MSBuild support for .NET 1.1 targets
The MSBuild team just posted beta 1 of the “MSBee” toolkit which enables building .NET Framework 1.1 applications with MSBuild. For those of you moving towards MSBuild and still have a few 1.1 apps lingering this bring the build process under a single tool. On a related note I've written a few custom tasks already to generate publisher policy assemblies, use FxCop 1.35b1, Nullsoft Installation System, and the Red-gate SQL Toolkit. I'm working to get them added to the MSBuild Tasks Community ......

Posted On Wednesday, February 15, 2006 9:40 PM

A More Complete Stack Trace when Debugging Assemblies in the GAC
Have you ever had the need to get line numbers from an exception stack trace for an assembly in the GAC? If you work with BizTalk Server the answer is likely yes. To debug Commerce Server pipeline components which I have traditionally put custom C# pipeline components in the GAC and then registered for COM interop. I've found having line numbers indespensible when apps are running in the production test environment. I went searching for the answer and came across it. I thought I'd write it down here ......

Posted On Monday, February 6, 2006 7:17 PM

Delay Signing defeated! D'oh!
Development machines here use a delayed signing for building binaries. Only during the build process on the build server does a public/private key pair get used for signing assemblies. When using the unit testing features of Visual Studio 2005 we are prompted to provide a key for re-signing an assembly after instrumentation has been applied. If we provide the public key it will fail. If we provide the public/private key pair it will work. Has anyone else managed to get this working? Here's what I'm ......

Posted On Saturday, January 21, 2006 3:13 PM

Copyright © Colin Bowern | Powered by: