Cannot get my standalone executable to run with Vault 2025 - Need help

[dhaverstick]

I have a standalone executable that my users run to do various vault tasks without having to open the vault client. This executable has been working fine for years.

I am now porting it to the 2025 version and am running into trouble. I have moved the executable to use .Net core instead of .Net framework and have referenced the appropriate .Net core DLL's from the Vault 2025 SDK. Everything builds okay, but when I try to run the executable I get an error saying that it cannot find Autodesk.Connectivity.LicenseWrapper.dll. Yes, a copy of that DLL is in the same folder as the executable, along with a copy of AdskLicensingSDK_8.dll.

I've looked everywhere I can think of for an answer to this problem but I am coming up with nothing. Any help would be greatly appreciated!

Darren Haverstick

Paul Mueller Company

[Markus.Koechl · Accepted solution]

Unfortunately, we have not documented yet that you need two more DLLs included in your standalone applications output folder: 

I published an updated code sample for all log-in types targeting Vault 2025; the sample migrated the NET Framework version from 2024 to 2025 and added a .NET8 project. API-Onboarding-Sample--Vault-Logins 2025 (github.com)

[dhaverstick]

Thank you, Markus!

Darren

[dhaverstick]

Markus, how will that extra file, ljwhost.dll, be treated going forward? Will it be part of the Vault SDK or rolled into another dll?

Darren

[Markus.Koechl]

The file is part of the SDK ..\Core\ libraries.

[dhaverstick]

Thanks again! I couldn't find the file at first because I was searching for it using a lowercase "L"jwhost.dll instead of an uppercase "I"jwhost.dll.

Darren

[mfoster9TD82]

Hello @Markus.Koechl ,

I'm having a similar issue migrating a stand alone app from 2023 to 2025 .net8, and it's getting hung up on "Locating server"

I got your sample project to work with the dialog login but I'm not sure what I'm missing in my project.

I've added all the references and dlls in the output folder:

I'm initializing the Vault Forms Library in my WPF constructor:

public MainWindow()
{
    InitializeComponent();

    //Initialize the Vault Forms Library
    Autodesk.DataManagement.Client.Framework.Vault.Forms.Library.Initialize();
   ...
}

And I'm using this method to call the login dialog:

 private static Vlt.Currency.Connections.Connection GetVaultConnection(MainWindow window)
 {
     try
     {
         IntPtr parentWindow = new WindowInteropHelper(window).Handle;

         var settings = new Vlt.Forms.Settings.LoginSettings
         {
             AllowAnonymousLogin = false,
             AutoLoginMode = Vlt.Forms.Settings.LoginSettings.AutoLoginModeValues.RestoreAndExecute
         };

         settings.OptionsWindow.SetParent(VForms.Settings.WindowSettings.ParentType.UseSpecificWindow, parentWindow);

         return Vlt.Forms.Library.Login(settings);
     }
     catch (Exception ex)
     {
         window.LogMessage($"Vault Connection Error: {ex.Message}", "Error");
         return null;
     }
 }

And my Platform Target is x64.

Any ideas of other things I can try?

Here is an test project that is set up the same as your example:
Test Project (github.com)

Edit:
I finally got it to work, I just added all the vault SDK .dlls to the folder with my referenced .dlls and it worked...

[Arkadiusz_Budkowski7HGZ4]

Hi. I checked times for operation on vault and found connection which makes it 2x faster. What are the pros and cons of my solution to use this:
var authFlag = Vault.Currency.Connections.AuthenticationFlags.WindowsAuthentication;
var result = Vault.Library.ConnectionManager.LogIn(AutoUpdaterAdminSettings.ServerName, AutoUpdaterAdminSettings.VaultName, "", "", authFlag, null);
var conn = result.Connection;

i checked simple checking for modification dates of files on vault and this code makes 14ms / file and your solution on github addin is like 30ms/file. Also the connection is much faster this way. 

Or is it maybe better to use the:
var conn = EdmSecurity.Instance.VaultConnection;

Is there something we dont know? I was fighting with the code to make the connection for 2 days when i found out i need libraries which are not even accepted by visual studio as dependencies (ljwhost.dll). Which libraries are needed to make the connection? At the moment i kinda took them all.