July 2005 - Posts
Intresting OSS project to create a LISP subset (more like Arc) called L#. It would be interesting to hear about how well L# performs on the CLI and if .NET 2.0 features like LCG can help.
Here is an interesting post, should VS2005 go to beta 3 rather than RTM to help ease some of the concerns of the beta 2 bugs. While I have been able to convert projects without a problem (as raised in the post) one of the things I have struggled with is MSBuild and web projects. While it seems RTM have resolved these issues if I can see MSBuild before that point it would be a massive help to making long term CI decisions.
Web projects (sln files) seem to struggle when compiled with MSBuild, the asp.net precompiler requires projects referances when the code is built but this step occurs first as noted in beta 1
http://blogs.conchango.com/simonevans/archive/2005/02/26/1072.aspx
This appears to be have been carried in beta 2 and fixed for the RTM
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=11950
Your looking at a bit of MSBuild trickery to get the referances updated until the RTM is released. Any experiences with this, suggested approaches?
The web app admin system in ASP.NET 2.0 is cool for things like managing keys etc but I still feel that web.config management across different servers (lets say a set of servers for development, test and release etc) remains a SCM issue, are you finding the web app admin system is helping your SCM issues?
pointed out that the web app admin system is not available on IIS, which means it cannot be used at all to help manage keys across different enviroments.
MbUnit features a MSBuild task but as of .beta 2.0.50215 changes to MSBuild are causing issues with the virtual app domains in MbUnit, a fix for this issue is a work in progress and earlier builds of beta 2.0 are ok. If your working with this build then a work around is to either use MbUnit on the command line or to use NAnt. With NAnt you can run NAnt using the command line MSBuild task and use the MbUnit NAnt task.
On a side note I have noticed some weird things about MSBuild, if you have build warnings then:
MSBuild test.sln
Does not publish them however the following will
MSBuild test.sln /t:Clean;Build
Not sure what the default is for MSBuild but I would have thought that /t:Clean;Build would be and thus warnings would be available.
Never understood why CI is not a part of VSTS although thats certainly an area that CCNet could help with. Dion Olsthoorn has this interesting
post on running MSBuild to control the CI process (sceduled run).
Already getting some great blog coverage for the article.
Unit Testing with VSTS, NUnit and MbUnit by Jay Flowers and Andrew Stopford -- Now is a pretty exciting time for unit testing in .NET. Tremendous progress is being made on several fronts: IDE integration, process integration, and new test fixtures. Jay Flowers and Andrew Stopford explain how to use Visual Studio's new integrated unit testing, as well as the NUnit and MbUnit testing frameworks.
Kudos to Jay on the MbUnit team for working really hard on this article (and for all his efforts on the project). Not written an article in 3 years :) good to be back.
As Peli reports we now have a new wiki in the form of Confluence and a defect/task tracker in the form of Jira. With both these systems in place we can now hopefully enjoy new degrees of documentation and workflow. Lots of work going at the moment as part of a raft of infrastructure changes for MbUnit, as when I have news I will post here (although if you join the mailing lists you will hear it as it happens).
Kudos to Morten on the MbUnit team for kindly hosting and setting this up.
More Posts
Next page »