Geeks With Blogs
Colin Bowern ... more of the usual bool March 2006 Entries
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

Copyright © Colin Bowern | Powered by: GeeksWithBlogs.net