[求助]：如何在VisualC++6.0下调试MDL文件

bluewood_cn

最近想学 MDL二次开发。无奈开发资料太少。
看了一点点资料，说是用mdl自带的编译器可以 编译mdl。
因为 自己对Visual C++ 比较熟悉， 但是不是很懂makefile那样的手工配置（也都是VC 害的）， 不知道 mdl可以用 VC++6.0 进行开发和编译吗？
因为AutoCAD上的ObjectArx开发，提供了objectarx的 向导可以很方便的建立工程， 不知道 MS提供了没有，望各位高手指点。

如何在 VC 下面调试MDL呢?请各位高手帮助解决呀。；）

GeoTri

当然可以，也可以用向导来生成VC框架再开发用于MicroStation的DLL。

bluewood_cn

谢谢了。现在已经 作了一个例子了。

不过我现在又遇到一个问题。 如果进行调试呢？ 好像是不能在 VC里面进行调试的。 如果不能 ，那怎么调试。会不会想 VC一样的 方便呢。 因为毕竟不是专业的去搞他的开发，只是用于自己的项目中，如果很难调试的话，就不好了。呵呵

/////////////////////////////////////////////////////////////
已经解决了，解决如下
/////////////////////////////////////////////////////////////
Here is some information on this that was in a previous edition of
BDNZine.

After the application is built!
Once the application is built the next major task will be debugging. In
order to debug
Native Code applications you will need to attach to the ustation.exe
process. There are
two ways to do this. First is to start MicroStation in the debugger. To
do this you need to
use this command line from the MicroStation Development Shell:
msdev %ms%\ustation.exe
this will start the Developer Studio IDE with MicroStation loaded.
You can then set the debug breaks at the functions in your application.
The altemate
method is to start MicroStation and then start your debugger, in this
example Developer Studio (msdev). Then inside Developer Studio attach to
the ustation.exe process from the Build -> Start Debug -> Attach to
Process menu item.

From this list select the ustation.exe process. Now you will need to add
your dll as an
additional dll to debug from the Project-> Settings menu select the
first tab then in the
combo box select additional dlls. Then in the main section select the
dll to debug.


Once you have MicroStation running in the debug environment you can then
set break points on your functions.  One tip here is to use the first
method of starting MicroStation under the debugger and then setting a
break point at MdlMain to catch your application at load time.  As a
drastic step or for initapps you can use the code line in your app:
__asm int 3;
This will cause the application to halt at this instruction but only
works when the application is being actively debugged.