Monday, February 24, 2014

Autodesk Vault Programmer’s Cookbook. 1.3. Objects of Vault



Navigation:

|
|

There's so-called “model of labor” by Mardakhayev, that’s corresponding to IDEF0 model.

It describes the mechanism of labor. So, for hammering a shelf:
  • What is – boards, nails
  • What should be – assembled shelf
  • Object of labor – separate nails and boards
  • Instrument – hammer
  • Algorithm – “Keep calm and hammer on”
Applying to Vault API, the model of work with Vault is:

Sunday, February 23, 2014

Autodesk Vault Programmer's Cookbook. 1.4. Methods of Vault API services



Navigation:

|
|

All the methods could be divided into groups by operation types – first verb in the method’s name. Let’s look how are distributed types with more than 4 methods:


As you can see, it’s: Get, Update, Delete, Add, etc. I think, it would be more honestly to start learning right from more often methods. Fortunately, they are sorted in complexity ascending order. So in the same way we’ll learn them.
Communication with the Vault server takes the form of SOAP commands over HTTP. You can check this, watching client-server dialog with Web Debugging Proxy, like Fiddler. We can imitate this executing PowerShell code that gets all groups.

Friday, February 21, 2014

Tuesday, February 18, 2014

Autodesk Vault Programmer's Cookbook. 2.3. Windows Authentication



Navigation:

|
|

Problem

Establish Vault connection, using Windows credentials.

Solution

Use WinAuthCredentials instead UserPasswordCredentials.


Sunday, February 16, 2014

Autodesk Vault Programmer's Cookbook. 2.1. Login



Navigation:

|
|

Problem

Establish Autodesk Vault connection.

Solution

Create WebServiceManager from Autodesk.Connectivity.WebServices.dll with credentials parameters.