March 2008

By aaron.axvig, Sun, 03/23/2008 - 03:00

This evening I thought I'd spend an hour and see if I couldn't make a lame Silverlight project just for the sake of doing it.  Plus it would be more productive than playing a game.

So I fired up Visual Studio 2008 and went to create a Silverlight project, but there was none to be found.  I went and downloaded the Silverlight 1.0 SDK, but still nothing.  It seems that version is for working with VS 2005.  I was trying to avoid installing any beta Silverlight stuff, but I ended up grabbing the Silverlight 2 Tools Alpha.  This did allow me to create a Silverlight project.

Seeing some XAML, I went towards the end, after all the declarations and such, and typed"Hello".  Just as a test.  Went to compile...error.  So I erased that, found <TextBox> using Intellisense, and put "Hello" between the tags.  Still no loving.  So I found the Text attribute, and put "Hello" as the value of the Text attribute.  Then I got different compile errors.  Specifically, 17 of them, mostly "The type or namespace name 'Windows' does not exist in the namespace 'System' (are you missing an assembly reference?)" type errors.

 I think I've seen this before, and seem to remember fixing it by adding a reference to something, but I couldn't find anything on Google this time.  So I'm still stuck there, and will be until I either find a solution or convince myself it's not just due to alpha version tools.  Maybe I'll just go play a game instead...

Tags

By aaron.axvig, Sun, 03/23/2008 - 03:00

Yet another productive thing I tried to do tonight: get my old Mexico blog online.  As one might guess given that IIS7 is quite different from IIS6, Dasblog has some serious problems with Server 2008.  Those are resolvable, per Mr. Hanselman's instructions.

Unfortunately there are further problems.  This time with Registry changes.  According to Mr. Starr's analysis, Dasblog seems to think it's cool to pull time zone information from the Registry.  Seeing registry accesses in a web application does not make me happy:

 

NullReferenceException: Object reference not set to an instance of an object.]
   newtelligence.DasBlog.Util.WindowsTimeZone.LoadTimeZonesFromRegistry() +283
   newtelligence.DasBlog.Util.WindowsTimeZone..cctor() +76

[TypeInitializationException: The type initializer for 'newtelligence.DasBlog.Util.WindowsTimeZone' threw an exception.]
   newtelligence.DasBlog.Web.SiteConfig.set_DisplayTimeZoneIndex(Int32 value) +23
   Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSiteConfig.Read7_SiteConfig(Boolean isNullable, Boolean checkType) +4743
   Microsoft.Xml.Serialization.GeneratedAssembly.XmlSerializationReaderSiteConfig.Read8_SiteConfig() +76

By aaron.axvig, Wed, 03/05/2008 - 03:00

I just saw yesterday that FTP7 was out.  So of course I went off to install it.  When I was done, the Default Web Site on the server no longer worked, including Outlook Web Access.  Much panic ensued, as in the past OWA has been very finicky and once broken it stays broken.

It turns out that I had uninstalled the IIS6 components as part of cleaning up before doing FTP7 (I had installed the IIS 6 things for FTP6).  I'm not sure if IIS6 components and FTP7 can live alongside each other as I uninstalled FTP7 when trying to get the site working, but I would guess so.  Anyways, simply re-installing all of the IIS6 components fixed the problem.