Class not registered

[LuukBoot]

Question:

Hello, I’m new to C# .NET development and recently created my first SOLIDWORKS PDM add-in. I tested the functionality in a test vault, and everything worked as expected. However, when I deployed the add-in to the operational vault, I encountered the following error: C:\Users.…\SOLIDWORKS PDM\PLugins{Vault name}{GUID}{version}\PDMADDIN2.CAF
Class not registered

Interestingly, this error does not occur on all client machines, only some of them. While troubleshooting, I tried manually adding the .dll and .caf files to the problematic machine’s PDM add-in folder. However, I noticed that every time SOLIDWORKS PDM starts, a new version of the GUID is generated for all add-ins, including mine. This seems strange because I thought the GUID should remain constant for each add-in and only should increase when a new version is generated.

Questions:

1. Is it normal for SOLIDWORKS PDM to generate a new GUID for add-ins every time PDM is started?
2. Could this be related to why the error only occurs on some client machines?
3. What are the best practices for ensuring the add-in works consistently across different machines in an operational vault?

Any advice or insights into what could be causing this behavior and how to resolve it would be greatly appreciated!

[AmenJlili]

There a lot of possible scenarios but it is mostly have to do with the local PDM vault not being able to register the add-in. I can’t see your code so I can’t really tell.

Here’s what I would do on those machines:

• I’d kill all pdm processes (Edmserver.exe, explorer.exe, sldworks.exe)
• I’d go the app data folder’s local folder (path is in the dialog box). I’d delete everything in there.
• Restart PDM.

[mwebster]

Were you able to resolve this issue? What you area describing is pretty much the exact same behavior we are seeing with some workstations after trying to deploy a PDM add-in. We have tried everything we could think of and are stumped.

Mike