[MIcrostation 10.15.02.11 french and SDK 10.16.00.80] Unable to load c++ dll

Rémy Weill said:

I get error message "MDL Loader: Could not load application" when trying to load c++ sample.dll (created from c++  template)

What do you mean by 'created from C++  template'?

A C++ app. must have a DllMdlApp resource.  Look in ..\DialogBoxes\myapp\myappcmd.r to see an example.  When you build your app, that resource is compiled and placed in your Weill.ma file.  When you type mdl load Weill, MicroStation looks in that file to find the DLL name.

Jon Summers said:

What do you mean by 'created from C++  template'?

Hello John

I mean I use the templates provided here:  https://communities.bentley.com/products/programming/microstation_programming/m/mediagallery/274053 

The C# sample works well while the c++ one compile but refuse to load

I can load .ma apps and .dll build from c# source code. I cannot load .dll build from c++ source code

Rémy

Hi Rémy,

Rémy Weill said:

I can load .ma apps and .dll build from c# source code. I cannot load .dll build from c++ source code

it's not correct, because:

• NET addins (e.g. written in C#) are "dll file only". No .ma loader exists, and it is created automatically by MicroStation at background.
• Native applications (written in C++) consists from .ma (loader) and .dll file(s).

Regards,

  Jan

Hello Jan,

Ok. I was trying to load a .dll while I should have load the corresponding .ma file (But, I didn't find  it)

Thanks for the explanation

Remy

Hi Rémy,

Rémy Weill said:

I was trying to load a .dll while I should have load the corresponding .ma file

in its basic (minimum) version, the only responsibility of .ma file is to define task id and in what dll file, the entry point (main() in normal C/C++ apps) is defined:

• In C++ applications, the entry point is MdlMain() function. In .r file, DllMdlApp structure has to be defined and it specifies task id and .dll file to be loaded. .r file is not supported by VS and bmake + rcomp has to be used.
• In C# applications, the entry point is class, inherited from AddIn class. Task id (and other optional parameters) is defined using attributes. (I guess) using reflection, MicroStation addin loader analyzes dll assembly and creates proper .ma file at background.

Rémy Weill said:

But, I didn't find  it

When application is built using bmake, there are always rules defined how to compile .r > .rsc and how to create .ma from this .rsc.

Regards,

  Jan

Hi Jan,

Jan Šlegr said:

When application is built using bmake, there are always rules defined how to compile .r > .rsc and how to create .ma from this .rsc.

That is the trick. the myapp.ma file is not created in my case even if the rules are included in the myapprsc.mki file

The build process stops to the .mi file

Maybe this has something to do with the french version of microStation because of the attempt of translation ?

Hi Rémy Weill,

Can you confirm these two items?

1. Verify the MicroStation Developer Shell (shortcut properties) is set to Run as Administrator?
2. Can you provide us with verbose build output logs? e.g.
    - Navigate to myapp (or your app) and type: build verbose
    - OR, bmake +avilC AppName.mke > %temp%\App-Build-Verbose-Output.txt

Thank you,
Bob

Hello Robert

Robert Hook said:

Verify the MicroStation Developer Shell (shortcut properties) is set to Run as Administrator?

Yes it is.

Robert Hook said:

Can you provide us with verbose build output logs?

Pleas find attachedBuild-myapp-Verbose-Output.txt

Rémy Weill said:

the myapp.ma file is not created in my case even if the rules are included in the myapprsc.mki file

Please post your make (myapp.mke) and include (myapprsc.mki) files.

Hi Rémy Weill,

I suspect it does have something to do with your install of MicroStation, but in my honest opinion not (yet proven) related to language, but possibly due to timing and conditions (required).

The MicroStation SDK even though things have been improved (unfortunately) still requires Microsoft 8DOT3NAME compliance. So on the Drive letter and/or at the time you installed MicroStation; I suspect Microsoft 8DOT3NAMES were not (fully) enabled on your system.

The reason (and evidence from the log) I believe this is the case is because the MicroStation SDK path on your C: drive are definitely using 8DOT3 names; showing use of: e.g. MICROS~1.

Where your MicroStation Product path on your D: drive does not appear to be using Microsoft 8DOT3 names; showing incomplete paths and file names in the log.

I would suggest enabling Microsoft 8DOT3NAMES on your C: drive then simply re-installing MicroStation since this will ensure new/required 8DOT3NAMES will be generated and available to the MicroStation SDK.  The alternate is to install MicroStation product in a path without having (any) spaces and this would accomplish the same effect.

Bob

Target: D:\Program
[== Building D:\Program, (C:\Users\ADMINI~1\AppData\Local\Temp\Bentley\MICROS~1\objects\myapp.mi) ==]
rlib @C:\Users\ADMINI~1\AppData\Local\Temp\Bentley\MICROS~1\objects\make.opt
MicroStation Resource Librarian 03.21.02
Macro (myapprsc.mki:45): ERRORLEVEL=0
End: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapprsc.mki
Resume: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapp.mke at line 146
End: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapp.mke
Thu Oct 21 15:36:45 2021, elapsed time: 0:05

Hi Rémy Weill,

I suspect it does have something to do with your install of MicroStation, but in my honest opinion not (yet proven) related to language, but possibly due to timing and conditions (required).

The MicroStation SDK even though things have been improved (unfortunately) still requires Microsoft 8DOT3NAME compliance. So on the Drive letter and/or at the time you installed MicroStation; I suspect Microsoft 8DOT3NAMES were not (fully) enabled on your system.

The reason (and evidence from the log) I believe this is the case is because the MicroStation SDK path on your C: drive are definitely using 8DOT3 names; showing use of: e.g. MICROS~1.

Where your MicroStation Product path on your D: drive does not appear to be using Microsoft 8DOT3 names; showing incomplete paths and file names in the log.

I would suggest enabling Microsoft 8DOT3NAMES on your C: drive then simply re-installing MicroStation since this will ensure new/required 8DOT3NAMES will be generated and available to the MicroStation SDK.  The alternate is to install MicroStation product in a path without having (any) spaces and this would accomplish the same effect.

Bob

Target: D:\Program
[== Building D:\Program, (C:\Users\ADMINI~1\AppData\Local\Temp\Bentley\MICROS~1\objects\myapp.mi) ==]
rlib @C:\Users\ADMINI~1\AppData\Local\Temp\Bentley\MICROS~1\objects\make.opt
MicroStation Resource Librarian 03.21.02
Macro (myapprsc.mki:45): ERRORLEVEL=0
End: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapprsc.mki
Resume: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapp.mke at line 146
End: C:\PROGRA~1\Bentley\MICROS~1\examples\DialogBoxes\myapp\myapp.mke
Thu Oct 21 15:36:45 2021, elapsed time: 0:05

Hi Bob

I have enabled 8dot3names on drive D:

D:\>fsutil 8dot3name query d:

The volume state is: 0 (8dot3 name creation is enabled).
The registry state is: 2 (Per volume setting - the default).

Based on the above two settings, 8dot3 name creation is enabled on d:

and unisnstall/reinstall MicroStation and sdk on drive D:

But it seems the problem is still there (even worse..)

D:\Program Files\Bentley\MICROS~2\examples\DialogBoxes\myapp\myapp.mke(58) : error : Missing Dependency: Files\Bentley\MICROS~2\examples\DialogBoxes\myapp\myappcmd.r
BMAKE: call trace
line: 58, D:\Program Files\Bentley\MICROS~2\examples\DialogBoxes\myapp\myapp.mke
Fri Oct 22 12:51:58 2021, elapsed time: 0:01

Remy

Rémy Weill said:

D:\Program Files\Bentley\MICROS~2\examples\DialogBoxes\myapp\myapp.mke(58) : error : Missing Dependency: Files\Bentley\MICROS~2\examples\DialogBoxes\myapp\myappcmd.r

The first file (myapp.mke) continues to use a Windows long file name D:\Program Files\....

The error tells us that the build process can't find file Files\Bentley\ ... \myappcmd.r.  In other words, the file path has been split at the space character in Program Files.

Hello John,

Yes, I saw.

The problem is that changing shortname behavior only creates the short names for new files and folders. Not for existing ones.

I have rename Program files and reinstall and it's working now

Many thanks John, Bob and Jan for your help

Remy