Both Robert McLaws and Michael Teper have an opinion on the membershipprovider as well.

My response to Robert's post:

Obviously not everybody at Microsoft agrees with on the return types/exceptions issue. In the WSE TokenManager model, an exception is thrown if the tokenmanager is unable to authenticate a user for the service.

My biggest problem with the MemberShipProvider is: it heavily depends on the membershipuser, which is a much too specialized class, I generally don't need :
Comment
CreationDate
Email
IsApproved
IsOnline
LastActivityDate
LastLoginDate
LastPasswordChangedDate
PasswordQuestion

And their related methods.

The other problem is the CreateUserMethod, this takes 7 parameters, of which one out parameter and returns a MemberShipUser... The only 2 parameters I will regularly use are the username and the password. And why doesn't it accept a membershipuser or derived class as inputparameter, now I have to do a cast and fill my custom properties afterwards.

Basically I still believe the providermodel is great, but the membershipprovider-stuff needs some work.

Tim Sneath has the obvious answer: in reverse release order.

Steve Eichert discusses why webservices should only have a single parameter, a requestobject and a responseobject as a return value.

”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.]