23 May 2009

As I'm now back to Java for work and miss .NET, I’m going to mess a bit with open source projects. The one I picked is Subtext, a blog engine written in ASP.NET. I’m not an ASP.NET guru, so messing around (and maybe even help, who knows?) with a project like this will likely get me some experience.

I just installed Windows 7 RC on my PC, so I'm starting from scratch here. I installed Visual Studio 2008 Standard edition, then SQL Server 2008 Express. The code that I checked out from Subtext's SVN doesn't build with that configuration, it needs some tweaking.

As I have been struggling to get the project to build, I writing a small post to summarize all the issues that I had and how I solved them.


The first error that you will encounter when trying to build Subtext out of the SVN is this one:

Type or namespace name SQLDMO could not be found

SQLDMO is deprecated in SQL Server 2008. However, as pointed in this forum thread, there is a backward compatibility pack.

References in UnitTests.Subtext

In UnitTests.Subtext project, some of the references are broken.


As stated here, these DLLs from SQL Server 2005 have been removed from SQL Server 2008.

Delete the references to:

  • Microsoft.SqlServer.ConnectionInfo
  • Microsoft.SqlServer.Smo
  • Microsoft.SqlServer.SmoEnum
  • Microsoft.SqlServer.SqlEnum

The add the references back using “Add Reference…” dialog.

However, this is not sufficient. The project will not build and still complain:

The type 'Microsoft.SqlServer.Management.Sdk.Sfc.IDmfFacet' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.SqlServer.Management.Sdk.Sfc, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91'.

Again, using the “Add Reference…” dialog, add a reference to Microsoft.SqlServer.Management.Sdk.Sfc.


This will leave you with only two Warnings about references to CookComputing.XmlRpcV2 and Microsoft.ApplicationBlocks.Data.


However, in this state you can build the project completely. If you delete the references in the project, it will not build anymore, for a reason that I still have to identify…

And Now?

Well, technically you can build and deploy now. I’ll talk about that in coming post.

blog comments powered by Disqus