Some time ago I complained about the fact that a TypeConverter for Types was missing from the .NET Framework.
At the time I had search for one in the framework but only found internal or private implementations.
As it turns out, the version 2.0 of the .NET Framework introduced a TypeNameConverter that does practically the same thing as my TypeTypeConverter, beside the poor naming.
I say poor naming because the documentation for TypeConverter states that “The most common type of converter is one that converts to and from a text representation.“. This converter does not convert from text to a Type Name but to an instance of Type. Nevertheless, it’s in the framework and you should use this one instead of mine.
For those who can’t (or don’t want to) deploy .NET Framework 3.5, the service packs included for the 2.0 and 3.0 versions of the framework are available as standalone downloads.
Visual Studio 2008 and .NET Framework 3.5 has finally shipped.
MSDN subscribers can download the final version of Visual Studio 2008 from MSDN Subscription Downloads, but anyone can get a trial version or an Express Edition.
The .NET Framework 3.5 contains many new features building incrementally upon .NET Framework 2.0 and 3.0, and includes .NET Framework 2.0 service pack 1 and .NET Framework 3.0 service pack 1. and is also available for download.
You can read all about it from various teams and team member’s blogs:
Today, S.Somasegar announced at TechEd Developers EMEA, amongst other things, that they the product team at Microsoft is putting the finishing touches on Visual Studio 2008 and .NET FX 3.5. They are on track to shipping these products before the end of November 2007. They will have the marketing launch for these along with Windows Server 2008 and SQL Server 2008 at the end of February.
Safira (a Portuguese company) has been involved in a big SharePoint project and developed a tool (SPOME) that they are sharing as a CodePlex project, Check it out.
There’s a thread going on the Alt.Net Conference list about User eXperience Architecture.
I think there’s a bit of confusing between UI/UX and painting screens.
My bank has both VRU and SMS user interfaces for costumers and they have nothing to do with screens.
The bottom line is I thin there’s a need for User eXperience Architecture experts. It’s more than matching colors.
Glenn Block has announced that, after the announcement that Acropolis won’t be out so soon, Practices & Practices is releasing a WPF Composite Client.
The Acropolis Team has announced that Acropolis is going to enter a new phase.
When a web page uses scripting to close a browser window that was opened by the user and not opened by some action on another page, Internet Explorer pops up a question to the user warning that “The webpage you are viewing is trying to close the tab.” (in this case, Internet Explorer 7) and asking the user for permission to close the tab.
Before Internet Explorer 7, all that was needed to do was setting the window.opener property to a non null value:
window.opener = self;
Unfortunately, Internet Explorer 7 isn’t fooled by this. Internet Explorer 7 knows if the window was opened by the user or not, regardless the value of the window.opener property.
Fortunately, Internet Explorer can still be fooled:
Going one step further, if you want all your calls to the window.close method to work this way, you can change the method implementation like in the following example:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
// Save a reference to the original method.
var windowClose = window.close;
// Re-implement window.open
window.close = function ()
<input type="button" value="Close Me!" onclick="window.close()" />
<input type="button" value="Close Me!" onclick="windowClose()" />
Joern found a nasty bug in my code. I’ve uploaded the updated source code in all articles.