WoW:Lua editors/Visual Studio: Difference between revisions

editorializing and add cats
 
(editorializing and add cats)
Line 18: Line 18:
This might become the one reason for using Visual Studio in AddOn-development. Those of you who played around with the Whidbey-Beta will know what I mean.
This might become the one reason for using Visual Studio in AddOn-development. Those of you who played around with the Whidbey-Beta will know what I mean.


The XML editor included in .NET 2003 is okay, but really nothing special. It has basic XSD support and stuff, but it really won't stand a chance against tools like [http://www.altova.com/products_ide.html XMLspy]. However, with the upcoming release of version 2005 things will change. The whole XML-Editor was rewritten in the new version and can now easily compete with most XML-Editors out there, free and commercial. So anyone who is already planning to buy Whidbey once it's released will greatly appreciate it's XML-capabilities for WoW-scripting.
The XML editor included in .NET 2003 is okay, but really nothing special. It has basic XSD support and stuff, but it really won't stand a chance against tools like [http://www.altova.com/products_ide.html XMLspy]. However, with the upcoming release of version 2005 (which almost certainly won't ship until 2006, as is the way with most MS programs) things will change. The whole XML-Editor was rewritten in the new version and can now easily compete with most XML-Editors out there, free and commercial. So anyone who is already planning to buy Whidbey once it's released will greatly appreciate it's XML-capabilities for WoW-scripting.


 
[[Category:Interface Customization]]
----
[[Category:Glossary]]
Anonymous user