Natty Gur

Today I notice buggy behavior of .NET designer. One of my client use windows user control on one of his web form to create rich client web application. To install the user control on the client side they use the object tag with code base attribute pointing to cab file responsible to register the user control assembly in GAC and register as COM object (the just follow one of MS KB's). While the page running from browser every thing works great but when they try to open the page in design mode if the got lucky they get never ending error messages "argumentexcaption  HDC". If the don’t have luck they got the following message "CLSID_CorSymWriterSXS could not be created error &H80040154". That message won't disappear unless they reinstall CLR 1.1.

I play today with XAML styles. Generally they are very
similar to the Web style but sometimes they take other
approach. For example to change style as a result of
user actions on the page XAML styles required
additional tags instead of using the OnXXX syntax.

One nice feature that I run into is Style inheritance.
By using BasedOb attribute you can specify that one
style inherits other style behavior. You can also
override certain style attributes to change the base
style behavior.

Below you can find simple code that demonstrates style
changing on user action and style inheritance.

Just finish converting of 24 web applications, on two machines cluster, from CLR 1.0 to CLR 1.1. All those application serve as one system that based on ASPX pages and assemblies using COM+ services. Due to large objects (85k +) memory clean problem of the CLR 1.0, which was solved in CLR 1.1, the aspnet_wp memory usage climb and users start to complain about performance. The only solution recommended by MS was switching to CLR 1.1.

I installed Longhorn on machine with the required system configuration and finished the subscription process. The server is running 24 hours a day without any problems or crashes. but, after 24 hours of working I get this horrible blue screen with NT_EVALUATION_TIME_EXPIRED message.  Of course after booting every think goes back to normal for the next 24 hours.

Well, I start to play with XAML. Since most of my client use Hebrew support in their application I thought it will be nice to create window application that will support right to left flow direction. It was pretty easy to find FlowDirection attribute but when I try to use it in my code:

 I heard Don Box talk about Indigo and I was pleased to hear him distinguish between Application and systems, stating that application don't actually exist in our world anymore. While I agree with this statement I think that we are going toward system of systems world. System of systems take the abstraction one level up, it's not about system it's about the enterprise and the enterprise relation to other enterprises. One of the areas that I'm strongly involved in is Competitive intelligence (CI) / intelligence systems. CI system is actually system of systems that made up from several systems that exist in the enterprise. But from the end user point it's just one system that integrated all data types and formats from different sources, usually on the same page, enabling him to draw conclusions that will benefit the enterprise.