More adventures with Orcas on Longhorn


Let’s be clear from the start, if you read the readme.htm (which I did, uncharacteristically) for Orcas Beta 2 it does not list Windows Server 2008 as a currently supported operating system so I can’t blame anyone else for my pain….

So despite the warning signs I ploughed ahead anyway to install Orcas Beta 2 to on my main system which was running Windows Server 2008 Beta 3. As I reported a couple of days ago I had what seemed to be a minor problem initially with beta 2 which I managed to fix.

However it turned out that this was really just a lesser symptom of a more complex (though simple when you understand it) issue.

I discovered, on trying to create an AJAX enabled web site, that I could not compile it. Again I got the dreaded “Unrecognized tag prefix or device filter ‘asp’ “ error and this time I also got an error that “the type System.Web.UI.IScriptManager could not be found in assembly System.Web.dll version 2.0.0.0”. Sure enough, a bit of reflecting showed clearly that I did not have that type in my System.Web.dll which (located in my ‘D:WindowsMicrosoft.NETFrameworkv2.0.50727’ directory) showed as being version 2.0.50727.1320.

After some further messing around to try and fix this, by uninstalling and reinstalling ASP.NET Futures June package (though I’m not saying that broke it, as I messed around with a number of things), I also managed to lose all controls from my toolbox:

clip_image002

which isn’t very helpful.

No amount of uninstalling, reinstalling, running devenv.exe /setup etc would restore them.

So, asking around a bit one of the developers helpfully suggested that IScriptManager did not used to be in earlier versions of System.Web.dll and that beta 2 should bring me up to version 2.0.50727.1378. I checked with a colleague Carlo who had beta 2 installed and sure enough he had version 1378.

Hmm, so how come I’ve been short changed and only have version 1320?

After much gnashing of teeth and pulling of hair the answer became apparent. In Windows Server 2008, the Microsoft .NET Framework 3.0 is included as part of the OS and this includes the updated core 2.0 runtime known as ‘Redbits‘.

But here is the deal. As soon as you include something as part of the core operating system you lose the freedom to just patch it or update it as and when you feel like it. It then has to be updated as part of the operating system. Now for a released operating system that means a hotfix or a service pack. But when we are dealing with beta operating systems that, unfortunately means you’ve got to wait for the next build.

So the bottom line is that Orcas beta 2 is not supported (read ‘won’t work’) on Windows Server 2008 beta 3. If you are part of the preview program for Longhorn you may have access to the June CTP build in which case you can install Orcas beta 2 and it will work.

After installing the June CTP of Windows Server 2008 my Redbits were up to version 1373 and running and my toolbox was back to normal:

image

But hang on. Where are the AJAX Extensions?

Then I realised that this time it was user error – I’d tripped myself up on one of the new features or Visual Studio 2008 – multi-targetting. When you create a new project you can now choose which version of the framework you want to target and the IDE will only show you those features that are applicable. In my case I had accidently left the choice from the last project I had created:

image

Once I selected 3.5 as the target:

image

I had my toolbox items back to the way they should be:

image

Cheers

Doug

Comments (6)

  1. Buck Hodges on TFS 2008: Command line help for tf.exe now prints to the console. Jason Prickett on TFS…

  2. linearburn says:

    I booted off the longhorn cd and replaced the dll files with the ones from my windows vista directory i now have 2.0.50727.1378. however i am still getting that issue so im thinking that this issue runs a little deeper the orgional message im geting even after replaceing the files

    Parser Error Message: Could not load type ‘System.Web.UI.IScriptManager’ from assembly ‘System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a’.

    Source Error:

    Line 80: </div>

    Line 81: <br />

    Line 82: <asp:ScriptManager ID="ScriptManager1" runat="server">

    Line 83:                 </asp:ScriptManager>

    Line 84:                 <cc1:Media ID="Media1" runat="server" AutoPlay="True" Height="113px"

    Source File: /default.aspx    Line: 82

    ——————————————————————————–

    Version Information: Microsoft .NET Framework Version:2.0.50727.1320; ASP.NET

    Version:2.0.50727.1320

    so im thinking that long horn is eather cacheing the dll’s or somthing is afoot

  3. linearburn says:

    i did manual check the dll in the .net folder btw to verfy

  4. linearburn says:

    this is beta 3 longhorn server

  5. Hi linearburn

    I wouldn’t recommend direct substitution of DLLs like that. There is a lot more to .NET assembly installation such as NGEN, GAC etc.

    As mentioned in the blog post

    "So the bottom line is that Orcas beta 2 is not supported (read ‘won’t work’) on Windows Server 2008 beta 3. If you are part of the preview program for Longhorn you may have access to the June CTP build in which case you can install Orcas beta 2 and it will work."

    If you don’t have access to the June CTP you could always use Virtual Server and install Orcas in a guest OS which is supported.

    Regards

    Doug

  6. Web developer interested in preparing for IIS7 will be interested to know that the Release Candidate

Skip to main content