XML Notepad 2006 goes 2007

| 1 Comment | No TrackBacks

Just couple of months after XML Notepad 2006 release Microsoft ships another version,  now called XML Notepad 2007. They even went and edited the article "XML Notepad 2006 Design" to be "XML Notepad 2007 Design". Cool.

XML Notepad 2006 was released on the 1st September 2006, and 2 months later it had 175,000 downloads! So it looks like this little utility has found a useful place in your toolkit which is exactly what we were hoping. Thanks for all the great feedback and bug reports; many of which have been incorporated and fixed in this new version. While this is mostly a bug fix release (like fixing the install on Vista!) there are also a few new features thrown in just for fun.

New in this version:

  • Added keyboard accelerators for find again (F3) and reverse find (SHIFT+F3).
  • Added support for loading IXmlBuilder and IXmlEditor implementations from different assemblies using new vs:assembly attribute.
  • Made source code localizable by moving all error messages and dialog strings to .resx files.
  • Added a default XSL transform.
  • New icons, a play on the Vista "Notepad" icons.

XML Notepad 2006 2007 is a tree view based XML editor, and it's not in my tool list because I can't work with XML editor which won't show me XML source, but then I'm XML geek and I feel more comfortable seeing angle brackets than tree view, while I'm sure lots of people will love it. Give it a try anyway.

I only wonder why all this stuff isn't in Visual Studio? Why is that Microsoft XML team can afford playing with another XML editor while Visual Studio XML Editor still sucks having no XML diff, no XPath search, no refactoring, no decent XSLT editor nor XML Schema designer?

Related Blog Posts

No TrackBacks

TrackBack URL: http://www.tkachenko.com/cgi-bin/mt-tb.cgi/641

1 Comment

I agree with you completely. I believe it is really rude that they assume everyone who downloads that tool is finding it useful. Many have probably downloaded it out of curiosity. And many probably because they were not pleased with the built in support in Visual Studio... :)

I was surprised when I saw there was no direct code editing, not even a separate code view... It was disappointing.

Leave a comment