Mads Nissen

This small handy tool from MS gives you a detailed insight in your SPS server. I found stuff I never knew existed and now I have another source of information when working with sharepoint.

Phui! That's one mean abbreviation:-)

In my previous posting I described how to use NAnt to auto deploy webparts to Sharepoint. I just ran across the WPPackager tool from Microsoft which enables you to create MSI installers for the WebParts.

I've been developing webparts that use regular ASP.NET Usercontrols as content for a while. Up until now we've simply hardcoded the url to the usercontrol location in the webpart class. Moving towards a more standardized product that must support differentiated deployment envrironments I wanted to place the url to the usercontrol in the webpart dwp file.

Automatically building and deploying cab files for sharepoint is a great efficiency booster. I have previously blogged about my simple, yet effective, autodeployer for sharepoint cabs. This time around I wanted to automate the construction of the cabfile itself and deploying it to the sharepoint testserver. The pseudo code for the build/deploy steps are something like this:

I've been working a lot with Continous Integration lately with CruiseControl.NET. All was going well and I had a medium sized build process set up. Suddenly the NUnit2 task in the NAnt script for one of my testcomponents started failing in a completely random fashion. The only output in the nunit2 task in nant log displayed by ccnet was <task name="nunit2" /> .

I've just updated my last GDN sample to v1.1 with more stuff after the feedback I've got since my last post about it.

We do most our SharePoint development based on ASP.NET WebForms and UserControls. WebParts are only used to host UserControls and pass information between them using Connections. WebForms are frequently used as PopUp windows triggered by the UserControls.