Robert McLaws: FunWithCoding.NET

I've come to the conclusion that .NET doesn't really make coding easier (yet), because most Framework classes are incomplete, and use Inheritance as an excuse to leave them that way. Case in point: XmlTextWriter.

Or are the workspaces wigging out tonight?

When I posted about this before, someone noted that cycling through all the items would be a performance hit. Well, as you can see, I'm really only cycling thru the tables in the DataSet, and in the case of the DataReader, I'm only accessing a property that already exists.

Right now, I have all my web services under one project, secured behind SSL. I have not decided if I want to move the to a better location, like http://webservices.interscapeusa.com, or something like that. Basically to move them out of the SSL security. Now, I'd like some opinions in terms of the effect... is the latency of SSL combined with the serialization of data into XML substantial? Is it worth it to have your data stream encrypted, or would it be better to use WSE to make sure the data is encrypted and not the whole stream? Is there something I'm not considering here? Please leave me comments, thoughts, and suggestions. Thanks.

“Be sure to read the EULA” - John Tobler

My long-awaited article on Data Access Layer security is here! None of what I talk about is really new information, but it is put forth in a very unique way. Here's an excerpt:

MS made a lot of information about Whidbey public today. While I cannot elaborate in any way about the features, I can confirm that they exist, and that they are pretty awesome. They've done an outstanding job enhancing the developer experience. And this is just the Alpha.

Having just registered for and been accepted to the Visual Studio Integration Program, I've been going through the included Help collection, and found some neat little tidbits. These actually have nothing to do with the VSIP SDK, but the SDK did lead me to some great docs in the regular VS.NET 2003 Help Collection.