”I'll be there”

After a month in Mexico, I'm back.... and I have a decent internet connection again...

I spent the whole month working on an application using WSE 2.0 to get a soap interface on a windows service, with some decent authentication. Did I mention WSE 2.0 rocks..... more to come soon™.

Some small changes to the RTM version in the new sp1 release.

Briljant timing, since today I started developing on a realtime e-auction application, with the UI communicating over soap.tcp to a windows service acting as the broker.

For the next 4 weeks I am in Mexico working on a software project with some nice Mexican developers.

Posts will probably even less frequent then they have been in the past couple of weeks, but for now I'm enjoying Mexico very much.

Perhaps not as glamorous as the .NET framework 2.0, but not less eagerly awaited.

.NET Framework 1.1 Service Pack 1 Tech Preview provides an early look at updates and feature enhancements that will be shipped as part of .NET Framework 1.1 Service Pack 1.

.NET 1.1 sp1 Tech Preview

.NET 1.1 sp1 Tech Preview for Windows 2003

NET Framework 1.0 Service Pack 3 Tech Preview provides an early look at updates and feature enhancements that will be shipped as part of .NET Framework 1.0 Service Pack 3 .

.NET 1.0 sp3 Tech Preview

Update: more information about the servicepacks in the .NET developer center.

Very cool initiative in San Francisco, for people who can't work in an office, either beacuase there isn't any or it's too far away: the work-club, offering co-workers, i.e. other members, wifi hotspots and a cafe.

It may sound strange to join a club for work, but for studying for exams there is a similar club, the university library... a lot of quiet areas, a crappy cafetaria and other students for social interaction. I can get stuff done at home, but at the library it's just a lot more efficient.

[via: ArsTechnica]

The MSDN Library, that came with the May community preview, wouldn't show any of the topics. The solution was to change the binding "dexplore.exe" from the v2.0.40507 to v2.0.40426 in the "dexplore.exe.config"-file in the install directory, since that version of the framework is installed.

[update: I just noticed this is descriped in the readme, in point 18.2.]

Since I just got hit with four spam comments in 5 minutes, comments are disabled for now.

Not sure if this is new for VS 2005, but I don't remeber seeing it earlier:

object Convert.ChangeType( object o, Type t )

Very usefull in the following scenario:

public T ConvertFromString(string s){
     return (T)Convert.ChangeType(s, typeof(T));
}

It took me some time to find out, what options I had to enable to enable debugging in a Whidbey ASP.Net project in windows 2003 server, so maybe this is usefull for someone.

Start with a regular webproject, using the IIS Manager map a virtual directory (EKPool in this picture) to the directory where you created this webproject. Make sure it's an application on the "Directory"-tab and make sure it's using v 2.0.* of the framework on the "ASP.Net"-tab.

Allow the "ASP.NET v2.0.*" Web Service Extension, prohibited by default.

Open the "property pages" of your webproject. Change the Server property on the "Start Options"-tab to "Use custom server" and enter the path to the virtual directory you just created in the "Base Url" textbox. Check the ASP.NET debugging checkbox.

Check the web.config file for the "compilation node" :<compilation debug="true" defaultLanguage="c#" />.

Start debugging with [F5] or run the application without debugging with [CTRL]+[F5].

This also works if you create an application in the root of your website, something which won't work, when you use the integrated webserver in Visual Studio Whidbey.