-
Re: dll on the server or local machine
Do you mean the shared directory as the server of your add-in? I have never tried this but not sure that this will work. Your dlls need to be registered as the COM components on the local machine so this might fail if you access it from shared directory.
Are you trying to build the automatic deployment system so all your clients are running the same version of the add-in (like it is done in ePDM)?
If you are developing the stand-alone application and you do not need to register for COM - this will be an easier task.
-
Re: dll on the server or local machine
Hi Artem,
I understand that the DLL needs to be registered as the COM component on the local machine, but can the DLL folder be saved in the shared folder in the server
The reason for this is when I make changes to DLL, the users don't have to copy it over to their local machines as what I did with all the macros
-
Re: dll on the server or local machine
Hi Chris,
You may need to map your shared path to a mapped drive to make it work. But there several issues:
- If you added new com component user will need to rerun the registration on a client machines
- If any of the users loaded the SolidWorks - dlls will be locked and you cannot replace them until they are released
- Not sure that SolidWorks will accept shared dlls.
Personally I would not suggest to have an add-in in the shared location.
Thanks,
Artem -
Re: dll on the server or local machine
it is working, we have been using Aton SolidPDM and all other macros and applications for years from network drive. Disadvantage of this is, that you can't replace file with new version when someone is using it.
-
Re: dll on the server or local machine
Artem, Ivana
Yes, there are pro/con of putting macros on the server
Pro: The end users don't need to copy to their local machines and always access to up-to-date macros - No need to send out updated macros to the users
Con. Macro is locked if any user is using it but it's not too bad since the macros are not updated every day and I can ask all users to shutdown SW so I can replace the old macro with a new one or just wait until the end of the day to do it
Not sure if I can do the same with DLL since SW is connected to DLL each time SW is open while macro is linked to SW when the user wants to run it? Am I correct here?
is it ok if one DLL can be linked to diff. SW on diff. local machines?
-
Re: dll on the server or local machine
here is no problem with same dll on different local machines (+-100)
Users have readonly rights on directories where macro and add-in's
-
Re: dll on the server or local machine
This is the way to want to proceed - Thanks for confirmation, Ivana
Have you experienced any problem such as the SW running slow?
-
-
-
-
-
-