If it is not possible to avoid using the dll, alternative way could be to add dll as the resource file and dynamically copy the dll on add-in load and use the AppDomain::AssemblyResolve notification to properly resolve references at runtime.Unit Testing binaries should not be compiled into the target add-in output folder. For example could be added to the project as a part of Moq framework for Unit Testing. This library may be a part of another package which is not necessarily to be in the add-in project. Once found, inspect how to avoid using this dll.It might be required to comment out the code and remove the references one-by-one to find the dll which is causing the problem.Note, it is recommended to clear the bin (output) folder as the dll might no longer be used in the project, but still present in the output folder. References tree of the add-in project Resolution The issue will be reproducible even if dll is not used in the project but just present in the folder.

This error happens if project is using the libraries which are not compatible with SOLIDWORKS PDM. You can open that by pressing the Win key + R to launch Run. Firstly, you can fix it with Component Services. If playback doesnt begin shortly, try restarting your device. If you’ve encountered class not registered error, here are a few ways to fix it. Cause: the add-in registration succeeded but the add-in's class ID could not be found in the registryĮrror when adding add-in to the PDM vaultĪdd-in works correctly while debugging Cause How to fix the error - Notification dll has not been registered, program will not work correctly. NET add-in is added to the vault via PDM Administration tool: Error creating the add-in COM object from the dll 'name.dll'.

Notification dll not registered