Hi m gao,
[quote user="m gao"] built 2 c# samples delivered with the latest MSTN Connect SDK[/quote]
How did you build the samples? It seems there are three options available:
- using bmake
- from Visual Studio environment
- using bat file (which should be equal to Visual Studio option, because devenv is called)
[quote user="m gao"]I got the dlls also the addin loader ma files (under C:\Users\{username}\AppData\Local\Temp\Bentley\MicroStation\10.0.0\AddInLoader1.0)[/quote]
To be precise, you did not. As Jon mentioned, .ma is temporary file and in the case of managed addins it's not produced during the building process, but it's created by MicroStation itself automatically when the addin is requested to be load for the first time.
[quote user="m gao"]but I can't load the .ma file in mstn v10.02.00.39[/quote]
How did you load the sample? E.g. if there is WPFSample example, WPFSSample.dll is created in MicroStation\Mdlapp folder. So the application should be loaded by mdl load wpfsample key-in, so in fact you ask to load dll, but MicroStation creates ma automatically ... and you don't use mdl load wpfsample.ma key-in.
[quote user="m gao"]do I still need to load .ma to subsequently load the addin?[/quote]
It's the same as it was in V8i: MicroStation need ma loader to work with addins, but it's internal MicroStation process, you work and load with dll assemblies only.
With regards,
Jan