Hoping someone can help me with this problem.
I made a c# wpf addin for MicroStation, its a dll. I can load it fine on my end. but i have sent this to someone else and when they try and load it they get error message that says 'OHDOTSHEETMANAGER' is not trusted. OHDOTSHEETMANAGER is the name of the app.
then in the Message Details it says this...
'OHDOTSHEETMANAGER' could not be loaded because 'OHDOTSHEETMANAGER' does not have an authorized digital signature.
i found this post.
https://communities.bentley.com/products/microstation/w/microstation__wiki/15724/utility-cannot-be-loaded-because-its-not-digitally-signed
but i checked and the user has MS_SECURITY = NONE.
so i shouldn't need to have it have an authorized digital signature.
anyone run into this before? i works fine on my computer, are there additional things within MicroStation that control this?
JD
Update for everyone.
I believe I have somewhat managed to track down the issue. so the way we deliver our CADD standards is I wrote a sync app that syncs our cadd standards from an FTP site, this way they don't have to download the whole set of standards just to get a few files that were updated.
it appears that as long as the sync app downloads the dll file, it works. but if the user goes and downloads the dll manually, that's when the not trusted error happens.
Anyone know what might be causing this? I also upload the ftp files on my end via a app I wrote to help streamline the whole process. im using WinSCP in my app to download the files.
Hi John Drsek,
The Microsoft Windows Explorer informational message "The file came from another computer and might be blocked to protect the computer." can be attributed to the Microsoft Attachment Manager and enabled to protect users from malware and viruses.
If you truly trust the sources and wish to unblock an individual file or Easily Unblock All Files in a Directory Using PowerShell, PowerShell or in some cases Microsoft SysInternals tool Streams -d FileName may be of some help.
HTH,Bob
tried this still not working
HI John Drsek,
My next recommendation (favorite detective tool) would be to use Microsoft Process Monitor (procmon) to determine what may be happening behind the scenes that normal users (like us) are not readily able to see/observe. It will give you detailed insights related to File, Registry, Access, Call Stacks, find and (empirical) Application Design Insights and load orders.IMHO. The Microsoft Attachment Manager article should have provided all the standard entry points to know/be aware of. Hopefully Microsoft Procmon will provide those additional (software) insights we do not have at this time. Procmon has a very effective filtering system to leverage and learn (a Microsoft Tutorial and plenty of other procmon tutorials are available) what type of problems you are encountering.