Tag: compatibility
-
Vault 2015 R2
Warning: A new version of Vault Professional has been released to Subscription Center. For the first time in many years, the Vault team put out a full release in between the standard yearly releases. R2 is not a service pack, which is why you need to be careful.
-
What’s new in the Vault 2015 SDK
Vault 2015 has just been released. Here is a quick breakdown of what’s new and what’s changed in the API. Overall, these changes are reactions to changes in the Vault product itself. There’s nothing new here specific to API developers.
-
Cloud Based APIs
Is using a cloud API really any different than any other client/server API? If you have developed with the Vault API, then you should already be familiar with many of the core concepts. Things like latency, user permissions and multi-user environments all still apply to the cloud. So is the cloud just a larger scale…
-
Events and Multiple Client Versions
When Vault 2012 came out, it introduced the events feature, which allowed you to write your code once and have it hook to all Vault clients on the machine. However, I want to point out that these events are version specific. This aspect wasn’t a problem in Vault 2012, because you needed the 2012 API…
-
Web Service Compatibility
Hopefully you already know that Vault 2012 clients can access the Vault 2013 server without the need for any sort of software update. This compatibility feature works at the web service API level. Basically, anything that uses the Vault 2012 APIs can connect to Vault 2013.
-
.NET 4
In Vault 2013, we shifted over to .NET 4. This isn’t just an API change, the product itself shifted too. In fact, I think all Autodesk products using .NET were told to shift over. The whole suites thing forces our products to be on the same technology platforms whenever possible. Anyway, here is what you…
You must be logged in to post a comment.