Posts

I have been having a problem with a new automated CI build under Team Build that I have added to an old Visual Studio solution. The solution is fairly big, but in essence it contains a shared data type assembly, a web site front end and a back end web service. The problem was on the Team Build drop share in the _PublishedWebsitesproduced by team build I was finding a old version of the shared data type assembly. However in the release directory of the same build I found the correct newly built version of the assembly. ...

I have been struggling today with a problem that a PostBuild event on a C# project works fine on my development PC but failed on a Team Build box. The project is based on the Codeplex SharePoint Visual Studio Project Template that uses post build scripts to create a deployment WSP. It turns out the problem was an unwanted condition on the PostBuildEvent in the projects .csproj file. It was like this: ...

Interested in finding out more about Microsoft’s Cloud computing strategy and the technology behind Azure? Yes - well you are in luck there are more UK Microsoft road show events in February. They are in Cambridge, Edinburgh and the one we are hosting in Bradford on the 13th. For more details and links to registration see http://blogs.msdn.com/ukisvdev/archive/2009/01/14/new-dates-for-azure-technical-briefing-announced.aspx

I have posted in the past on porting our ASP.NET bug tracking systems into Sharepoint and also linking it to TFS. The idea being that the initial customer support contact is tracked in the call tracking system e.g. is it switched on, is there paper in it….., and then escalated to TFS when development effort is required. To do this escalation my webpart calls a WCF service to access the TFS API - why you ask? The TFS API is 32bit only and you cannot call it directly inside a Sharepoint 64bit server farm. ...

The details of the February meeting of the Agile Yorkshire User Group (new name, and new web site is on the way, watch out for posts) The session is on developers experiences of TDD, another view from the coal face. See you there, 2nd Wednesday of the month as usual….

DDD community events are getting another venue this year, Queen’s College in Taunton on the 23rd of May. It has been decided that some of the speaker will be regulars from other DDD events; including myself speaking on Scrum. However all the other slots will be filled in the usual submission and voting manner, with the added rule the speaker should be new to the conference circuit (speaking to user groups is allowed and encouraged). So is this you? do you fancy speaking? if it is then submit a session. ...

You can vote for sessions at SQLBit IV as of today at http://www.sqlbits.com/information/PublicSessions.aspx, you do need to join the site first. Note joining the site is not the same as registering to attend the event which has not opened yet.

I have been working on an internal legacy application at our place that is being slowly moved from ASMX to WCF services. At present the services are a mixture of the two and there is a new WCF based client making connections to both types as needed. This work has been going on for a while on Vista development boxes without any problems. However when I opened the solution on a Windows 7 box (Beta 7000 build) I found I could not access the WCF services hosted locally using Visual Studio 2008’s WebDev.Webserver.exe (Cassini) server. ...

I am using Windows 7 Beta on my main PC, whilst trying to install an application today I hit a problem, the installer failed on start-up. Firstly I thought it was a corrupt MSI so I tried another application, but it did the same. When I checked the Windows Application event log I found the following Faulting application name: msiexec.exe, version: 5.0.7000.0, time stamp: 0x49432105 Faulting module name: ntdll.dll, version: 6.1.7000.0, time stamp: 0x49434898 Exception code: 0xc0000005 Fault offset: 0x00000000000ebbaa Faulting process id: 0x7dc Faulting application start time: 0x01c97a77da8e8b3e Faulting application path: C:WindowsSystem32msiexec.exe Faulting module path: C:WindowsSYSTEM32ntdll.dll ...

Just seen that there has been a calls for speakers for DDD Belfast, another chance to meet up with like minded developers.