• State Not Answered
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 543 views
  • Users 0 members are here

Setting up VS 2017 C++ project for debugging

Daverode
Offline

I'm trying to setup a vs 2017 c++ project to debug a MDL project I created with Microstation SDK Command Utility.

I'm using Promis.e Connect Update 10 (Latest Build). I'm not 100% sure what version of Microstation that translates to, but the add-ins I've created with VS in C# and the MDL add-ins I've created recently with bmake work as expected. I'm just trying to get debugging setup so I can take advantage of some of VS's debugging tools as I am new to C++ and just stumbling my way through at the moment.

I've got to the point of building the project and keep getting the error:

----Error C1189 #error: Data Alignment must be defined in basedefs.h

In the basedefs.h file this seems to have something to do with WinNT not being defined. I did find a previous post concerning this:

https://communities.bentley.com/products/programming/microstation_programming/f/microstation-programming---forum/182307/connect-c-setting-up-c-visual-studio-project-problems/705315#705315

but couldn't understand much of it.

I tried pre defining WinNT(Not sure I did that correctly either) and while it eliminated that error, now I've 17 new very wordy and complicated looking errors concerning memaloc and string defs of all types...

Another issue I may have is that I will be debugging this on a remote machine which I do all the time with my C# Add-ins.. just not familiar with C++ and MDL Command prompt to get this going.

Any insight will be greatly appreciated. 

Thanks

Dave

Parents
  • 0 Offline
    Daverode said:
    I am new to C++ ... I'm trying to setup a vs 2017 c++ project to debug a MDL project

    I recommend that you start with one of Microsoft's example projects and build an executable (.exe) Windows app.  Then debug your executable using the Microsoft tools.

    Once you're comfortable building and debugging an executable, then you can move on to building and debugging a DLL.  Again, I recommend starting with a Microsoft demo app and DLL, without the complexity of the MicroStation overhead.  Note that the debug application is always the .exe — you attach the DLL in Viz Studio to that running process.

    Once you're comfortable building and debugging a normal DLL, you can start with your MicroStation project, which is by definition a DLL.  When debugging your DLL, MicroStation is the host process.

     
    Regards, Jon Summers
    LA Solutions

  • 0 Offline in reply to Jon Summers

    Thanks Jon,

    I'll try that and see what happens. Getting ready to go on vacation so I probably won't respond again until first week of June

    Thanks for the quick response

    Dave

Reply Children
No Data
Communities
Support and Services
Training and Learning
Social Media