I've recently come across a problem that I've not encountered previously. During development, it's commonplace to build an app., load into MicroStation, perform some tests, unload the app. and make some changes.
I unload my app. (*.ma + *.dll), make some modification to the source, and rebuild. The build fails to complete, with this message...
MicroStation Resource Librarian 03.09.02 ### Cannot write to output file: G:\PROGRA~1\Bentley\MICROS~2\MICROS~1\mdlapps\xxxx.ma
Note that it's the .ma file that is apparently locked by MicroStation, not the DLL. I double-check that the app. really is unloaded (in the Utilities|MDL Apps dialog) but have the same problem. The build completes only if I exit and restart MicroStation. As you'll appreciate, this is a little tedious — it gives C++ developers the same pain that .NET developers experience.
Here's some more evidence. I loaded my app. in two different ways...
1 Manual Load: Note the resource file count == 1
2 Auto-Load from Custom Palette: Note the resource file count == 2
When an app. is auto-loaded from a custom tool palette, MicroStation opens the .ma resource and doesn't let go.
Regards, Jon Summers LA Solutions
Answer Verified By: Jon Summers
Hi Jon, have you tried uninstalling Connect Advisor? I had the same problem and this fixed it. See my post here: communities.bentley.com/.../v8i-should-mdl-developers-uninstall-connect-advisor
--Piers PorterAltiva Software
Piers Porter said:have you tried uninstalling Connect Advisor?
The problem occurred some time (years) before CONNECT Advisor was introduced. If you look at the screenshots of resource use, it's pretty clear what's going on.
FYI. The MDL auto-load resource count issue was assigned Bug 658754. I cannot say exactly when this will be address however it is currently active, open and assigned within the MSCE U17.1 backlog items.