I am trying to find a way to deploy my dll built in c++ to my microstation application. Could you please suggest the steps to deploy it and convert to microstation ma and dll file? I am using Micrstation v8i SS6.
Hi Ajomon,
unfortunately, it's not clear what you are asking about :-(
Ajomon George said:I am trying to find a way to deploy my dll built in c++ to my microstation application.
"To deploy" typically means to make a system (application) available to a user. In desktop world, the synonym is "to install". So there is a contradiction in the combination of words "deploy to my MicroStation application".
So what do you mean by "deploy" term in the described context? How to use some external dll in custom MDL code?
Ajomon George said:Could you please suggest the steps to deploy it and convert to microstation ma and dll file?
To deploy and to convert are two different activities.
It's possible to write MicroStation application (native C/C++) or MicroStation addin (C# or other NET language) and to link/reference some other dll in such project. But details are missing to provide more information.
Ajomon George said:I am using Micrstation v8i SS6.
Nothing like MicroStation v8i SS6 exists. Please specify the used product exactly, share its name and build number. When talking about MicroStation V8i, several versions of V8i (SELECTseries 4) were released, followed by MicroStation V8i (SELECTseries 10). So the version you mention is wrong or you do not use MicroStation, but some different product.
With regards,
Jan
P.S. Please, do not pollute the discussion by so many assigned tags. Why to do that? Where is any benefit to use 3x MicroStation and 4x programming-related terms as tags? How it helps?
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
Hi,
one more comment, specifically about linking native DLL in V8i environment:
When you have own MicroStation application (code, that can be compiled to .ma and .dll files and run in MicroStation environment) and you want to use (e.g. to link dynamically at runtime) some 3rd party dll and to consume its functionality, you have to be careful about used compilers.
MicroStation V8i (and all products based on its engine) requires native application to be compiled using Visual Studio 2005 (I guess VS2005 Professional is the only officially supported) to ensure MicroStation and the application use the same C runtime. It requires the linked dll has to be also built using VS2005 compiler. See g.e. DLL hell article that well describes this issue.
When this requirement is not met (the application is built using newer Visual Studio or it is, but the linked dll not), the application will probably not work or, at least, will be unstable, especially because of memory management issues. There are several ways how to solve this situation, but they are not typically not simple and not universal.