Frustration is the word. Microsoft is widely known for creating disjointed teams that work on their own individual products and then try to jam them together at the last minute. The latest is Biztalk 2004 which is integrated with Visual Studio 2003.

Biztalk uses XSD to create document schemas. It never dawned on the Biztalk team that Studio uses XSD for strongly typed datasets. Hence after using Biztalk for a while and now(today) switching back to standard .NET development the Biztalk wizard has screwed up my datasets. You can no longer use Visual Studio to edit your datasets without it inserting the Biztalk 2003 namespace into each XSD. Worse still, you can’t remove this with the editor as it just jumps back in.

I ended up editing the XSDs in notepad (still the best IDE) and then regenerating their datasets by removing and re-inserting “MSDataSetGenerator” in the properties window of Studio.

UPDATE: I figured out the problem. The default XML editor in Studio is changed to a Biztalk plugin. To change it back, right click on an XSD and say Open with… then choose the XML Editor and hit “Set as default” in the little dialog that opens up.