[CONNECT C#] Cannot load dll on Windows 10

Hi all,

I have some custom tools that are developed with C#. With appropriate compiler switches and configuartion I made the code running on both: 32bit Microstation v8i SS3 and 64bit Microstation CONNECT / AECOsim.

It works perfectly on my own developer machine and on my coworkers machines (they dont have Visual Studio or stuff installed) all with WIndows 7 and all with both versions of Microstation / AECOsim.

Now we got some new PCs with Windows 10. Somehow it is not possible to load the dlls into Microstation on that Windows 10 PC. I tried both: Keyin "mdl load ..." and browsing for dll via Mdl-Dialog.
As the workspace is the same, the configuartion is the same and, well, everything else is the same except Windows version I really have no idea what kind of error that could be. Microstation is not helping very much: it just gives me the usual "... could not be loaded".

Maybe someone has an idea where to search for errors? Or even HOW to search? I have no idea. I mean as it is running on the other systems it should not be useful to install Visual Studio on that Win10 machine to try to debug with Windows 10. Or maybe that would be useful indeed?

Regards
Stephan

Parents
  • Stephan,

    In addition to Jan's questions can you also provide the following?

    1. What is the exact error number and/or message displayed?
    2. Do you experience problems on clients attempting to load a Release build?
    3. What are your current Project values for:
      1. Solution Configuration. e.g. Debug or Release?
      2. Solution Platform. e.g. ANY CPU, x64, x86, other?
      3. Application Target (.NET) Framework. e.g. v8i: v3.5/v4.0, CONNECT: v4.6.1
    4. If possible zip and attach the output from the MicroStation Developer Shell, type: set > c:\temp\%COMPUTERNAME%-SDKCFG.txt

    Thank you,
    Bob



Reply
  • Stephan,

    In addition to Jan's questions can you also provide the following?

    1. What is the exact error number and/or message displayed?
    2. Do you experience problems on clients attempting to load a Release build?
    3. What are your current Project values for:
      1. Solution Configuration. e.g. Debug or Release?
      2. Solution Platform. e.g. ANY CPU, x64, x86, other?
      3. Application Target (.NET) Framework. e.g. v8i: v3.5/v4.0, CONNECT: v4.6.1
    4. If possible zip and attach the output from the MicroStation Developer Shell, type: set > c:\temp\%COMPUTERNAME%-SDKCFG.txt

    Thank you,
    Bob



Children