Another user got the problem now that he uses an indicator package from another vendor which also uses the System.Management.dll file but this vendor didn't put the dll file itself into their indicator zip but only referenced the System.Management.dll file in the AdditionalReferences.txt ("*Windows*\Microsoft.NET\Framework64\v4.0.30319\S ystem.Management.dll").
This ends in unhandled exception errors when both indicators are used at the same time....
So I wonder what is the correct/best way to 'bundle' such dll files from the .NET Framework.
- I think the better way is to not copy the dll file itself into the indicator zip file but use the AdditionalReferences.txt file and put in there a line with e.g. "*Windows*\Microsoft.NET\Framework64\v4.0.30319\Sy stem.Management.dll" - correct?
- Am I right in assuming that a windows update updates the files in that Windows\Microsoft.NET\Framework64\* directory?
- If these dll files gets updated in there is the folder name also changed (now "v4.0.30319")?
- If yes how often this folder name / version changes because if so I always have to check if this folder name is still the same, if not I have to correct that reference in the AdditionalReferences.txt file and put out an update for my indicator itself?
Thanks

Comment