This made me laugh:
Hardware components contain smoke and when they go wrong you can tell by the fact that the smoke has escaped. Some hardware also contains fire, and when you let that out the entire office stops to see what has gone wrong.
[via Jon Shute, "Things that I learnt this week"]
How many thousand times have you created a new C# class, then deleted the ?Add constructor logic here? and/or the default, useless XML Documentation comment? Far too many, I'm sure.
Solving this problem is simple: Remove them from the template that's used to generate new classes. The file is found at the following location (VS.NET 2003):
%programfiles%\Microsoft Visual Studio .NET 2003\VC#\VC#Wizards\CSharpAddClassWiz\Templates\1033
Other templates are scattered around below the %programfiles%\Microsoft Visual Studio .NET 2003\VC# directory. Simply do an in-file search for ?///? and you'll find several more.
(I think EricGu or someone else posted something about this a while ago, but I can't find the post.)
[via Jeff Key, "Remove default comments in C# files"]
An excellent article from Jim Beveridge:
ATL and Upside-Down Inheritance explains the reasoning behind the slightly eccentric design choices made in the ATL windowing framework.
Hello to Graeme! I know Graeme from the real world (shock, horror!) and it's always a pleasure to discover another real person who blogs.
Interesting stuff on Graeme's blog:
This Windows API attempts to guess if a buffer contains unicode text or not:
An enormous collection of string matching algorithms, all with explanations and java animations:
More on my quest for knowledge about Indigo/WSE/DIME:
Rich Turner has an interesting article talking about how you can develop web services infrastructure now so that it migrates well to Indigo:
On the road to Indigo: Prescriptive Guidance for Today's Technologies
How about some coverage related to Indigo, DIME and the new MTOM/XOP stuff. Specifically, with Indigo will I still be able to send binary attachments without incurring the base64 overhead. If so, then how?
I'm trying to learn about SOAP and related technologies. I have recently been working on a connected wire protocol which involves sending XML messages to and from client and server. Most of it is a request-response system with the occasional unsolicited server->client message. Each message is wrapped in a pre-defined XML envelope. Sounding a bit like SOAP to anyone? So, I'm interested in how I can replace part of this system with SOAP.
So, here's how it went in tonight's web info-quest:
I'm using microsoft technology to start with: .NET to .NET.
In the future, I will need to send binary files from the client to the server (data for transmission). Therefore I'm also looking for neat ways to send both XML messages and the occasional bit of binary data.
I started out by noticing something about DIME somewhere. Back to MSDN →
Sending Files, Attach,ments, and SOAP Messages Via Direct Internet Message Encapsulation,
Understanding DIME and WS-Attachments - sounds good, but the article is really old (ok, really old in Web Services terms).
Google for DIME and Indigo (Indigo is Microsoft's up and coming web services stack stuff, so it's a good term to see if DIME is no longer loved) → DIME is dead PASWA/MTOM is the way to go (ah-ha!) → Back to MSDN →
Messaging Specifications Index Page → XML, SOAP, and Binary Data:
Hmm, no concrete evidence of an implementation. Back to Google →
Hmm. This leaves me confused. Dime is dead, MTOM is the way forward. Only it doesn't seem that anybody has bothered to create MTOM yet. What's a developer to do?
Update: It seems that in WSE 2, Microsoft are abstracting attachments from the DIME-specific to more general attachments so that migration to MTOM will be less painful: Philip Rieck.