-
-
Long awaited Release Candidate 1 of v0.85 is ready for NAnt. Added support for .NET 2.0 Beta 1, Mono and NUnit 2.2 are the major new features.
Buildmasters go get it!
-
-
I am currently upgrading our standard Continous Integration solution to the latest version of CruiseControl.NET when this great tip on versioning with CruiseControl.Net led me to this excellent wikientry AspNetWithoutWebProjects.
We currently have several buildsolutions running CruiseControl.NET and there is room for improvement. A more coherent versioning is very welcome. Also, maintaining ASP.NET projects for several developers with different local vdirs is a real pain so.. it's a good day to do CI.
Another great read when setting up or improving on a CCNET solution is CruiseControl Directory Hierarchy which points out a couple of considerations you should do when setting up your projects. Unfortunately there is little blogging around ccnet v0.7 yet (except for the usual releasenotes copypaste:-)
I did however stumble across Michael Swansons blog on CruiseControl.NET and MSBuild which is something we'd really like to do aswell.
In the refactoring of our buildsystem I got a peak on Peter Lillevolds buildscripts. Peter makes use of functions in NAnt that I've completely overlooked. For a long time I've enforced that directory names in properties must always have a trailing slash, but Peter doesn't care because this fixes it for him:
${path::combine(build.dir, 'XML')}
I'm sure there are more nifty tricks that I've overlooked but for now this makes my day easier:-)
ps. to those of you who attended our Continous Integration presentation on the Norwegian .NET User Group this autumn I might admit that I'll most likely convert to Peters "solutiontask-approach". Compiling just got easier on the cost of complete control.
ps again: You should not take the CruiseControl.NET Wikis "Hot referrers" literally I'm quite sure the devteam does not consider these to be "hot"...
-
-
I just received news that Microsoft has located the bug that caused local language to turn into english randomly. They're working on a fix related to the .NET framework 1.1 which is expected to resolve the bug, but have no release date for it yet.
-
-
When I figured out the Web Folder trick in IE I also solved a long-running headache.
The problem scenario is: "Users want to add multiple documents they've worked on in a Windows Sharepoint Services site as an attachement to an email, but finds it difficult to remember the url and/or open the site to select files from [File Open]".
The solution is to create a shortcut to frequently used sites and place them in "My Documents". By opening a frequently used site in IE as a Web Folder, and then right-clicking the folder in the left-side folderview they can choose "Send to Desktop (create shortcut)". Placing this in "My Documents" makes this webfolder directly available from Office. In order to select multiple files at a time, users also must change the view (in [File Open]) from Web View to Details and use Ctrl to select multiple files.
Suddenly Sharepoint got to be a lot easier than fileshares by creative use of shortcuts and Web Folders.
-
-
Moving files between document libraries on different Windows Sharepoint Services sites can be quite cumbersome.
Syntergy has a nice cut / copy / paste add-on that helps users a lot for those one-file moves. Doing batch moves though can be done easier and completely for free. I got the tip from this kb article on how to use web folders.
Open up a Internet Explorer window for the source and target folder. Use File -> Open and paste in the url of the document libraries. Make sure you check the box for "Open as Web Folder".
This lets you browse your WSS sites as web folders and supports drag-and-drop between them. Simple and effective.
-
-
The team at Thoughtworks have released a new version of their Continous Integration tool CruiseControl.NET. We've currently got CruiseControl.NET running on several of our developmentprojects and welcome this new release. It is really reassuring to see this project moving forward and taking the position as the primary CI tool for .NET awaiting the competition from Microsofts Team System.
Read the news here.