It's a mess.
Microsoft provides hundreds/thousands of method calls and classes but without any adequate API documentation or simple examples. NO ONE ON EARTH CAN USE IT!
I already Googled, Binged, etc... for examples, I figured out IronPython's source (but there some references that can not be fixed). Nothing works out of the box for VS10, VS12, VS13.
Microsoft, please add GOODexamples to all of your API's... it is not so difficult doing this.
Few examples of your really bad documentation style...
1) http://msdn.microsoft.com/en-us/library/microsoft.visualstudio.package.filenode%28v=vs.80%29.aspx
[Quote]A node in the project hierarchy that represents a file. [/Quote]
It's like: "A wheel of a car represents a part of a car."
2) http://msdn.microsoft.com/en-US/library/microsoft.visualstudio.package.filenode.filenode%28v=vs.80%29.aspx
[QUOTE]Parameters e: The project element that is the project item node.[/QUOTE]
What do you like to say with that?
In particular....
a) What is a project element in detail?
b) What is a project item node?
c) The type of e is ProjectElement (Something with MSBuild, right?) Ok, when I just like to create a ProjectElement instance I run in other problems... The constructor of ProjectElement requires 3 parameters
ProjectElement(ProjectNode project, string itemPath, string itemType)
Ok.... I do:
ProjectElement pe = new ProjectElement(project, @"\", "STRING FOR ITEMTYPE, BUT WHAT IS THE NAME/VALUE/GUID???");
But what are the allowed parameter values? It's not stated on any of your MSDN pages.
I just found a high level description which must be written by and for SENIOR SENIOR Programmers:
[QUOTE]ItemType:
Sets the ItemType for the item in the Project file.
[/QUOTE]
WOOOWWW, fantastic, everything is much clearer, thanks.
Do you like to have much more Examples of your unique documentation style?