Recent content by theoxyde

I figured as much. Besides, if an attacker can proxy into the network... they can probably sniff out some of the unencrypted credentials floating about the local ether. SSL becomes pretty useless at that point. Got indemnification? Heh.

I've seen several OEM machines shipping with .NET 1.1 preinstalled, mind you these are all XP Pro systems. I don't know if XP Home systems are getting it or not. Maybe the next version of Office will have some .NET components. That would probably have the best chance at widespread deployment...

I need a second opinion on this... I have been designing a web application for a client and the question came up about our implementation of SSL. Normally, when we are designing an app that can potentially be sending secret information about, we recommend the client use SSL. This particular...

AUTO and AUTO, ELEMENTS is fine if there is only one result being returned. I'll look into the EXPLICIT though.

I had the opportunity to see a bit of Whidbey in action at Dev Days, and like the guy there said... they are growing apart in some ways, but becoming more alike in others. For instance, VB is now getting XML commenting like C# has enjoyed since day 1. Both are getting Smart Tags, but only VB...

You have to use SQL Server "Personal Edition" on WinXP. All of the other editions require a server OS. SQL Server PE usually ships on a CD with the other editions.

Is there any way to get a root element into a FOR XML AUTO query? For example: select * from tableA join tableB on tableA.id = tableB.idA for xml auto Each record for tableB is nested properly within the tableA result, but there is no root node above tableA's results. I've seen examples...

On a lighter note though... more RAM certainly won't hurt, and it's cheap in proportion to the rest of the system. Finding the ins-and-outs of performance issues in database is, unfortunately, a lot more than "get the fastest hardware available".

Quite right! I've never seen a cutting-edge coder with a trendy haircut.

I think you are probably keeping with the "spirit" of the license anyways, even if not the letter.

There are a number of variables there besides simply hard disk configuration. Indexes play a big part in database performance, as well as the arrangement of data on the disk subsystem. An index can have an effect on where data is stored. Small random transactions will naturally be latency...

I qualified my statement with "may". I agreee with you though. Some probably will, but the vast majority will probably blame the creators of whatever product was exploited.

On the positive side... a rash of virus outbreaks may cause people to start taking security seriously.

It all depends on context. Sometimes it is easier to design things in VB... sometimes C#. Everybody that works for me has to know both, because we use both. Most of our middle-tier components are designed in C# and most of our GUIs are in VB, but there are exceptions to each of those...

The XMLTextReader would be your best bet, but your sample isn't valid XML. The :'s in the tags will throw exceptions. If you can get rid of those, then you can use the XML text reader... otherwise you will have to design your own custom parser. Second, you will need an opening and closing...