Ways to deploy my DLL to Microstation MA file

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. 

Parents
  • 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.

    With regards,

      Jan

Reply
  • 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.

    With regards,

      Jan

Children
No Data