There are a couple of issues that have already been found with the latest SDK. I want to make sure everyone knows about them upfront.
UserIdTicketCredentials and WebServiceCredentials
Please avoid using UserIdTicketCredentials and WebServiceCredentials in Autodesk.Connectivity.WebServicesTools.dll. We found an issue where they log out of Vault incorrectly in certain cases.
If you don't know what these classes are, it's because they are new in Vault 2012. The classes are used to provide login information to the new WebServiceManager class.
Workaround: The links below contain fixed versions of the classes. Basically the logout capability has been disabled so there is no danger for accidental logout. To use, just add the .cs or .vb to your project and use the UserIdTicketCredentials_bugfix or WebServiceCredentials_bugfix classes in place of the normal classes.
Click here for the C# fix
Click here for the VB.NET fix
Menu resets still needed for custom commands
I had this fixed. I swear. Unfortunately, something happened between my fix and the final release. So when you deploy new Vault Explorer commands, you will need to reset the menus before you can see it in the menu bar.
The good news is that toolbars don't need a reset and menus are much more stable than they were in Vault 2011. You should no longer see cases where the entire menu bar gets jumbled because a custom command was deployed or removed.
Workaround: Do a menu reset after deploying a custom command. The reset command can be found manually by right clicking on the menu bar and running the Customize command. Programmatically, a reset can be done by deleting the menu.xml file in %AppData%\Autodesk\[Vault Product]\Objects\Menu.xml.
It's the same as the Vault 2011 workaround.
Subscribe