User-dependent path for .addin files

[ziyad_nuwayhid]

Hello everyone,

Is it possible to have a user-dependent for the <Assembly> property in the .addin files?
We want to be able to place the .dll files in a sharepoint folder and have the addin file point towards there.

But the path where our sharepoint folder is synced is in the user folder.

The path would look like this :

<Assembly>C:\Users\user.name\Company_SharePoint\InventorExporter.dll</Assembly>

From my understanding every user would have to to replace user.name with their user.

Is there a way to use something like C#'s 

Environment.GetFolderPath(Environment.SpecialFolder.UserProfile)

to get the user folder or do we have to find a solution outside the user folder?

Thank you and Kind Regards

Ziyad

[Pineapple2024]

https://help.autodesk.com/view/INVNTOR/2023/ENU/?guid=GUID-52422162-1784-4E8F-B495-CDB7BE9987AB

The following four locations are supported. You can choose any one of the four depending on the needs of your add-in. Your .addin file can exist in any one of the following four locations or any subdirectory. The "%XXXX%" portion of each of the paths is an operating system defined variable. When using Explorer you can enter it as part of the path and Explorer will evaluate it to use the actual path defined by the variable.

All Users, Version Independent
Windows 7/8.1/10 - %ALLUSERSPROFILE%\Autodesk\Inventor Addins\
All Users, Version Dependent
Windows 7/8.1/10 - %ALLUSERSPROFILE%\Autodesk\Inventor 20xx\Addins\
Per User, Version Dependent
In Window 7/8.1/10 - %APPDATA%\Autodesk\Inventor 20xx\Addins\
Per User, Version Independent
In Window 7/8.1/10 - %APPDATA%\Autodesk\ApplicationPlugins

[JelteDeJong · Accepted solution]

You could run a Powershell script like this after you have installed the addin.

$path = 'C:\ProgramData\Autodesk\ApplicationPlugins\test.addin'

$xml = [xml](Get-Content $path)

$node = $xml.SelectSingleNode('//Addin/Assembly')
$node.InnerText = $env:USERPROFILE + '\Company_SharePoint\InventorExporter.dll'

$xml.Save($path)

(Pro tip: You could do the complete installation using PowerShell)

[ziyad_nuwayhid]

Thank you for your reply Pineapple2024.
Sadly this does not suffice since we don't want to deploy the .dll's locally to the user, because then they would have to update their local file when we do updates to our AddIns.
We were hoping to have one central deployment folder, so that we only have to setup the addin files for each user initially.

[ziyad_nuwayhid]

This isn't quite what we want, but it comes closest. Thank you