I have a shared library (stand alone .dll file. No .ma file.) Is there any example of this in the CONNECT SDK?
Hi Ken Adams,
As Mike requests, if you can provide some brief information related to your workflow or needs it may help provide better recommendations early on.
As Jon suggests, for MDL (.cpp Native Code) both a .DLL + .MA are required "to load" an application and access functionality defined in the .DLL library file - and - common Microsoft DLL library dependencies and common address space interactions are possible w/o need for Inter-Process Communication (a.k.a. IPC named pipes and queues preferred).
For MDL (.cs Managed Code) only a .DLL (standalone) file is generated as output; however behind the scenes the MicroStation .NET loader will create a temporary .MA image if not present "to load" a MDL .NET Addin application.
Bob
Sorry I was not more clear about my goal. I have a SS3 DLL I am trying to upgrade to CONNECT. It is a set of common functions that several other MDLs call. It has no .ma file itself.
I am simply trying to convert the make file at this point.
My SS3 make file looks a little different than my other make files. It has no cmd or typ resources or mki file. It is not as obvious how to use 'myapp' as a template to update this for CONNECT.