Keyable draw order and other fixes.
Better draw order key loading.
Added .inst.

http://www.esotericsoftware.com/forum/viewtopic.php?p=5430#p5430
Made a 2nd "_xna" .csproj file for the C# runtimes. This is unavoidable, as microsoft is ass-backwards. The proper solution would be to add an "XNA" configuration (or even better, "XNA-XBOX" and "XNA-Windows" configuration), but Microsoft requires that any project referenced by XNA also import XNA, even if the base project doesn't depend on it.
Removed a lot of unneccessary stuff from the normal spine-csharp.csproj file, as no one else has Ultimate Edition and they were not configured properly.
Changed the XNA solution to point to the _xna csproj.
Merge pull request #108 from CloneDeath/master

Made a 2nd "_xna" .csproj file for the C# runtimes. This is unavoidable,...
No need to recompute tangents.
Bounding box support.
Fixed XNA projects.
Keyable draw order for spine-csharp.
Additive blending for spine-csharp and spine-xna.
Bounding boxes for spine-csharp.
Minor updates.
License update.

Changed from New BSD to a custom license. The new license requires a Spine license to use the code. If you have a valid Spine license, you can do whatever you like with the code. This should not be a problem for anyone using the runtimes with Spine, nothing changes. If using the runtimes without a Spine license, you now need a Spine license. This is because the runtimes were created explicitly to be used with Spine.
Event timeline fixed to fire events correctly for edge cases.
SkeletonBounds refactored so state is not stored in BoundingBoxAttachment.
updateVertices -> updateWorldVertices to match bounding boxes.
Support for rendering via PolygonSpriteBatch.
Updated monogamy projects with links to BoundingBox classes
Merge pull request #114 from RandolphBurt/monogame-project-update

Updated monogamy projects with links to BoundingBox classes
License update.

Changed from New BSD to a custom license. The new license requires a Spine license to use the code. If you have a valid Spine license, you can do whatever you like with the code. This should not be a problem for anyone using the runtimes with Spine, nothing changes. If using the runtimes without a Spine license, you now need a Spine license. This is because the runtimes were created explicitly to be used with Spine.