Using reg keys and a UNC-Path

Add-in Express™ Support Service
That's what is more important than anything else

Using reg keys and a UNC-Path
How to start an add-in from a unc path? 
Subscribe
Norman Neubert




Posts: 13
Joined: 2022-06-09
Hi,

I've read the other thread from 2009 stating that its better to install an addin locally. I understood it. Doesn't make sense for me though.

Networks paths work great if you use a network drive like X:\ or so. Doesn't work for \\Servername\....

How to do it:

1) Put relevant files on UNC-path that is accessible via drive letter
2) During each login set relevant reg keys for user.

Why do it like this: The customer wants it, the files exist only once, every user has the same installation, installation only needs 20 reg keys. Not connected to the drive? Then it works tomorrow or connect to the network. Customer is happy.

Driveletters aren't that brilliant though.

So the question is: Why doesn't it work for UNC? Other COM-Dlls just work nice on UNC. Can this somehow be changed in Add-In Express?

Thanks in advance, looking forward to your answer.

Kind regards

Norman
Posted 11 Mar, 2024 21:28:06 Top
Andrei Smolin


Add-in Express team


Posts: 18833
Joined: 2006-05-11
Hello Norman,

Norman Neubert writes:
Can this somehow be changed in Add-In Express?


I don't think Add-in Express or your add-in participate in this game. Such things should be controlled by admins (directly or inderectly) and you should talk to them to solve this issue. If, however, it turns out - and I don't think this will ever occur - that Add-in Express can do something to change this, just let me know.

Regards from Poland (GMT+1),

Andrei Smolin
Add-in Express Team Leader
Posted 18 Mar, 2024 18:22:15 Top
Norman Neubert




Posts: 13
Joined: 2022-06-09
Hi Andrei, thanks for your reply.

the problem is that it is nothing an admin can solve. The problem is that the addin starts with X:\Myfolder but doesn't start with \\Myserver\share\Myfolder where \\Myserver\share is X:.

It must be something in the adxloader.dll that causes this issue. It's this key that doesn't work:

[HKEY_CURRENT_USER\Software\Classes\CLSID\{148E5F0E-DD94-4122-861B-XXXXXX}\InprocServer32]
@="\\\\Server\\share\\myaddin\\adxloader64.dll"
"ThreadingModel"="Apartment"
"Assembly"="MyAddin, PublicKeyToken=XXXXXXX"
"CodeBase"="file://///Server/myaddin/myaddin.DLL"
"Class"="myaddin.AddinModule"
"RuntimeVersion"="v4.0.30319"

Should work as it does for X:. But it doesn't. Can you please check this?

Kind regards
Norman
Posted 18 Mar, 2024 21:32:46 Top
Andrei Smolin


Add-in Express team


Posts: 18833
Joined: 2006-05-11
Hello Norman,

https://www.hanselman.com/blog/giving-a-mapped-network-drive-fulltrust-with-net-code-access-security

Regards from Poland (GMT+1),

Andrei Smolin
Add-in Express Team Leader
Posted 20 Mar, 2024 17:47:23 Top
Norman Neubert




Posts: 13
Joined: 2022-06-09
Dear Andrei,

wow, brilliant! Now I understand it and what you meant! Thank you so much, I'll test it!

Kind regards
Norman
Posted 20 Mar, 2024 21:37:20 Top