Hi all,
I have been experimenting building a native solution and have a few questions, hopefully someone might be able to give some advice to save me pulling any more hair out!
- Is it possible to build a CLR class library and load that in Microstation, without the use of bmake? I assume if this was possible the classes would need to be decorated with attributes to inform Microstation that they are commands and define the main entry point. From what I've gathered it seems the bmake takes care of this by compiling with all the correct resources and output them along with a ma file for loading the command table into microstation, however it is quite a complicated system with limited information/documentation available, and since I do not really understand how to configure it correctly I would love to remove it from the equation if possible!
- If bmake is required, is it possible to create a CLR solution and reference/call my own .NET class library? I managed to build a C++ MDL with command table etc. but as soon as I make a call to any .NET methods it fails to compile with error "System::Object not found, missing /clr option or missing import of standard assemblies?". I do not get this error in a standard CLR project that does not use a make file for compiling (compiles straight to dll).
- Is it possilble to use XML to define the command table in C++, similar to C#? Or is this something I would need to build myself (create the defines and Command Id's etc. through a pre-build routine)
Really hoping to figure out these last few pain points, as I think that a mixed language solution would provide the best of both worlds for Microstation development provided I can sort out these last few teething issues
Thanks!
Ed