Denis Bauer

Installing TFS Beta3 and WSS

DBauer — Tue, 27 Sep 2005 15:36:00 GMT

If you are trying to install TFS Beta3, make sure that you configured WSS in server farm mode (during GUI setup). If you don't do that, because you don't RTFM (as I often do), you might get the error message:

"Windows SharePoint Services is not configured as recommended by Team Foundation Server

Windows SharePoint Services configuration does not meet Team Foundation Setup recommendation."

Alternatively, WSS installation can be started silently with:
C:\>DownloadDirectory\STSV2.EXE /C:"setupsts.exe /remoteSql=yes /provision=no /q"
where DownloadDirectory is the path to the location on your hard drive where you saved the downloaded file.

Visual Studio 2005 Beta2 and SQL Server 2005 April CTP: Install order and version info

DBauer — Mon, 18 Apr 2005 06:19:00 GMT

With the download availability of Visual Studio 2005 Beta2 and SQL Server 2005 April CTP on MSDN subscriber downloads it's about time to update my post on compatibility of the different builds.

Once again let's take a look at the version of the CLR that comes with each product:
VS.NET 2005 Beta2: 50215.44
SQL Server 2005 April CTP (aka IDW14, 9.00.1116.08): 50215.44

So there should be no problem installing both sidy-by-side and even the install order shouldn't matter this time. I've tried it out on my laptop (Yukon first then VSTS) and indeed everything worked out just fine. Please note that you'll need SP2 on WinXP or SP1 on WS2003 and Office 2003 SP1 (if you want to use VSTO).

Another note: When talking to a MS person they refer to Beta2 as 50215.45 because that is the correct version number. Why is that? 50215.45 = 50215.44 + updated SQL Express. So with regards to the binaries there is no difference between .44 and .45. You'll notice that all System.* assemblies are labeled .44.

Now you might ask which version of Avalon and Indigo is compatible with Beta2? And until now the answer is "None". As I described in the previous post the March CTPs required PD7 builds of the CLR to run. So basically if you want to use Avalon or Indigo stick with PD7 or wait for a new, upcoming CTP build of Avalon+Indigo.

Visual Studio 2005 & SQL Server 2005 Febuary CTP, Indigo and Avalon March CTP

DBauer — Thu, 17 Mar 2005 19:55:00 GMT

Now that all the interesting releases of last week and this week are publicly available (for MSDN subscribers) many people both internally and externally wonder what can be installed together. Let's check the version numbers of the CLR each product uses:
VS.NET 2005 Feb CTP (aka PD7): 50110.28
SQL Server 2005 Feb CTP (aka IDW13): 50110.27
Indigo & Avalon March CTP: 50110.28

This shows that you can install all into one machine but the install order is important:
1. Install the Whidbey Framework 50110.28 from Visual Studio 2005 onto the machine
2. Install Yukon which skips the .NET Framework installation because there is already a newer version
3. Install Visual Studio
4. Install Indigo and Avalon as described in the documentation

I've tested this in a virtual machine and at least the installation worked without problems. I haven't yet tested a lot of the other stuff though.

Have fun and let me know if it works :)

Crossposted from my homepage

Announcing Reflector.SQL2005Browser

DBauer — Tue, 08 Feb 2005 20:17:00 GMT

Reflector.SQL2005Browser

The SQL 2005 Assembly Browser is a little add-in for Lutz Roeder's .NET Reflector that can be used to browse .NET assemblies stored in a SQL Server 2005 (Yukon) database.
You can connect your local Reflector installation to a remote SQL Server instance, list the databases and its assemblies and download them directly into .NET Reflector.

http://www.denisbauer.com/NETTools/SQL2005Browser.aspx

Differences between System.Web.UI.LiteralControl and System.Web.UI.WebControls.Literal

DBauer — Tue, 08 Feb 2005 18:41:00 GMT

Mike Ogden pointed out the fact that the DynamicControlsPlaceholder (DCP) does not correctly recreate System.Web.UI.LiteralControl. At first I was very perplexed because I was somehow sure that I successfully tried that before. However, I must have mixed it up with the System.Web.UI.WebControls.Literal which works without problems.

That raises the question why there are two different controls and how they differ. The major difference is that the LiteralControl does not persist the Text property in ViewState, which is why it is recreated emptily by the DCP. The Literal, however, takes a LiteralControl as a child and saves its Text in ViewState:

protected override void AddParsedSubObject(object obj)
{
 if (!(obj is LiteralControl))
 {
 throw new HttpException(HttpRuntime.FormatResourceString(
 "Cannot_Have_Children_Of_Type", "Literal", obj.GetType().Name.ToString())); 
 } 
 this.Text = ((LiteralControl) obj).Text; 
}

So, if you want to use literal controls with the DynamicControlsPlaceholder make sure that you use Literal instead of LiteralControl.