Looking for SDK DLLs

[shallN6L5D]

Good morning,

We have a web app that connects to Vault, our ERP system and Forge Viewer to display drawings and models for non-CAD users (yes I know the Vault thin client exists, but that requires a login...)

I need to make some changes to it, which requires recompiling. Now that we are on Vautlt 2024, I referenced the new set of DLLs in the SDK but some seem to be missing according to the messages displayed in Visual Studio. I confirmed that these aren't in C:\Program Files\Autodesk\Autodesk Vault 2024 SDK\bin\x64\

AdskLicensingSDK_5.dll

Autodesk.Connectivity.AdSSOWrapper.dll

Autodesk.Connectivity.WebServices.dll (though I have the ...WCF.dll)

Autodesk.DataManagement.Client.Framework.Vault.Forms.dll

There may be more; this was just what I spotted comparing the previous build to what's in the SDK.

Where could I find versions of these DLLs that are compatible with Vault 2024?

cheers

Simon

[Nick_Hall]

Hi Simon

For 2024, you will need the following files for licensing

AdSkIdentitySDK.config

AdSkIdentitySDK.dll

AdskLicensingSDK_7.dll

The best way to get hold of these files is to install the Vault SDK and look in the C:\Program Files\Autodesk\Autodesk Vault 2024 SDK\bin\x64

Hope this helps 

Nick

[shallN6L5D]

Hi @Nick_Hall ,

Thanks for confirming. Yes I installed the 2024 Vault SDK and have those three to use as references.

Visual Studio is showing errors due to not being able to load "Autodesk.Connectivity.AdSSOWrapper.dll" which I have since been told has been deprecated.

Maybe it's outside the scope of this forum; if this reference is no longer needed, how do I remove it from the Visual Studio solution?

cheers

Simon

[Nick_Hall · Accepted solution]

Hi Simon

It's usually a case of finding the reference in the Solution Explorer tree, and using right-click -> Remove

Where you find it depends on the version of VS you are using. In 2022, for example, it will probably be in a subfolder of "Dependencies"

Hope that helps

Nick 

[shallN6L5D]

@Nick_Hall That seems to have done it, after some more fiddling with Visual Studio.I did eventually get it to build without errors.
I haven't been able to test it yet as I need to set up an environment with .net 4.8.1...