.NET Brain Droppings

I'm a Microsoft Certified Architect (MCA)... Feel free to ask me about the program...

May 2003 - Posts


SoapExtensions suck!!!!

If you've ever worked with Remoting and you've done ChannelSinks or MessageSinks then never mess with SoapExtensions; you will rip your hair out...

The Remoting guys made extensibility elegant; the WebServices guys made extensibility painfull!!!

Update: After a nights sleep, I'm a little more rational.  Maybe they don't outright suck, but I'd still rather create server-side sinks in Remoting...

[Listening to: Man Should Surrender - Pailhead - (4:42)]

The CodeDOM rocks!

I've been doing a lot of work lately with the CodeDOM namespace, and I've got to applaude Microsoft for this one. If you need to generate langugage agnostic code, this is most definatly the way to do it.

I'm in the middle of creating a proxy generator that generates a client-side proxy for a web service (sort of like wsdl.exe does, only the proxy is spicific to our ESB architecture), and I needed to create either Visual Basic or C# source files; CodeDOM to the rescue.

The code I currently have in place is pretty complicated, but I'm going to scale it down and post a bit of it in my codesnippet section that way its a bit more consumable. I just had to applaud MS on this one; way to go guys!

[Listening to: My dog growl as she chases her tennis ball around]

The BlogRoll is gone...

The BlogRoll has been put out to pasture. It was severely out of date, and if I were to actually list every blog I read in a linked fashion on the right-hand column, you would have to scroll 50 miles down...

As an alternative, I may create a story that contains links to all the blogs I read, but even that would take some work. As an alternate, I'm going to list a few of my favorites below:
Joel on Software
Chris Brumme
Brad Abrams
The Scobleizer Weblog
Kent Sharkey's Blog
Mark's Mind

I'm sure it comes as no surprise that most of these are MS bloggers; its always nice to get a view of what goes on inside the walls!

[Listening to: Cracker - OhGr - (03:32)]


Well, after more than 2 1/2 years, I've unsubscribed myself from the DevelopMentor hosted DOTNET lists. I just can't deal with the volume anymore. Not that I was really a high volume poster anyway, but I did lurk, and would help out if I could.

The reason I say "if I could" is that my day job just didn't allow enough time to keep up with the volume of those lists. Many times, I would let the email filter into a spicific folder, then I would flip through them in the evening. The problem with that is most times, by the time I found a post I could answer, someone beat me to it...

So, for a bit of nostalga, I though I'd include a link to my first post at the DOTNET list. Apparently, I was having problems commiting changes in a dataset (notice I called it ADO+, for those of you who missed the pre-beta1 PDC bits from Aug. 2000, .NET was called NGWS and everything was a + [ADO+, ASP+, etc.], correct me if I'm wrong, but I think NGWS stood for Next Generation Windows Services).

Anyway, whose got time for a discussion list when there's all these kick ass blogs to read! =)

[Listening to: Harsh Stone White - Skinny Puppy - (06:58)]


Luke's new release of my favorite rss aggregator (sorry Mark =) makes me wonder; does anyone out there use the web browser to read blogs anymore? I used to, but several months ago, I realized that it was futile to attempt keeping up with the 50+ blogs using a web browser (espically when one of them is Scoble's =). For me, the primary reason to use an aggregator is that it keeps track of read/unread/updated items. When you read as many blogs as I do, it is impossible to remember if you've read a post, and there is just no way to do that with a web browser.

There's another reason I ask this question. It seems that when I post a entry using w.blogger, it never looks quite right in the browser. I think it may have to do with the way the css works at dotnetweblogs, but I'm not sure. So after posting, I go back and tweak it using the online editor to make it look pretty. Funny thing is, the post looks fine from the aggrigator. So here's my question; do any of my 3 readers (including me) view this blog via the web browser? Just curious. Because if more people use an aggrigator than the web browser I'm going to stop cleaning the post up and use w.blogger exclusively.

[Listening to: You Often Forget - Revco - (08:52)]

Is it pronounced nant or n-ant?

This is kinda funny. When I talk to different people about using NAnt, I hear it pronounced two different ways. So which one is it? How do you pronounce it... I have to admit, I say nant, all one word. Given that both the N and the A are capitalized, I may be wrong, but I'd like to get some input from the community...

[Listening to: Rodent - Skinny Puppy - (05:50)]

(Error 0x80090022) tattoos, I'm buying

(Error 0x80090022) For customized troubleshooting information for this connection, click Help. Thanks. That was really helpful. I was just reflecting on how much better my life would be if I could just have my own 0x80090022 to care for. As a user, don't you just gnash your teeth with this kind of stuff? As engineers we've got to realize that no normal user, upon seeing HRESULTs in error messages, ever whacks their forehead and says: "Oh! Right! The old (Error 0x80090022) silent context acquisition gag. Of course. I remember that one."

I agree 100% with Scot on this one. If there are any people out there reading my blog who manage development teams, you need to read this entry in full; then once you've read it, you need to allocate enough time in your project plan to have someone other than a developer (PM, BA, QA resource) to write up the text of all these error messages.

Of course as developers, we have to do our part; and a big portion of that is to use resource files for the error message text. You should try to never compile down an error message into your code. Set up a strategy for how you will handle and present error messages early in the game. Very often this is overlooked until the last minute and can prove to be a real pain late in the schedule if not handle soon enough.

So how do I know all this? Because early on in my last development effort, we didn't set up any type of strategy, so by the time we hit UAT, we had error messages popping up from 8 different developers, all written differently (most having less than 5 words), and people were wanting them changed. Ugghhhh.... The next one will not be that way!

[Listening to: Assimilate - Skinny Puppy - (06:58)]

Thanks ScottW

I want to take a second out to thank ScottW for providing our blog space. I did this early on when I started blogging here, but I think it needs to be said again. I know as a developer we get a lot of satisfaction in knowing that tools/apps we build are useful for our customers/consumers, but taking on an undertaking as large as dotnetweblogs has to be a labor of love. I'm sure its a lot of work to keeping it running AND working on the new features we never let up in requesting.

Good job man! Keep it up!

[Listening to: Deity - Ministry - (03:24)]

w.blogger test post
Sweet, I like this. I think using a tool like this will prompt me to blog a little more. While I love being a part of the dotnetweblogs community, I was't too keen on the web based interface. Rock on...

And look, no more manually typing the currently playing track!

[Listening to: Impossible - Ministry - (07:43)]

More Posts « Previous page