After searching all over the BeCommunities site I found information that explained how to install the Wizards.
The short description of what I did was: Unzip the Wizards, which yields the following folders: ControlFiles, MDLProjectWizard, MicroStation AddInWizard, MSTNToolWizard I placed the folders in a folder I created: d:\mdlWizards (this was my choosing, not per directions) I then tweaked each of the .vsz files (in the ControlFiles folder) to look something like this: VSWIZARD 7.0 Wizard=VsWizard.VsWizardEngine.8.0 Param="WIZARD_NAME = MDLProjectWizard" Param="ABSOLUTE_PATH = d:\mdlWizards\MDLProjectWizard" Param="FALLBACK_LCID = 1033" I then copied all the files in the ControlFiles folder to C:\Program Files (x86)\Microsoft Visual Studio 8\VC\vcprojects (which would be different for people running 32-bit Windows or a different version of Visual Studio, I'm running VS2005) I then launch Visual Studio 2005 and select New, Project. Select Project Type Visual C++ and then pick one of the three Wizards: MicroStationAddInWizard, MDLProjectWizard, MSTNToolWizard. When I select a wizard and click OK it creates the project files. I then attempt to Build and that's when the trouble starts. I've tried each Wizard and each project doesn't build for different reasons. Below is what happened for MSTNToolWizard1 (default name of the project that I kept when using the Wizard). After attempting to fix each issue I tried to Build the project and got new error messages. MSTNToolWizard1 issue: Cannot open the include file mdl.h (and many others) resolution: right-clicked on Project in the Solutions Explorer and selected Properties. On the Properties I went to Configuration Properties > C/C++ > General and added C:\Program Files (x86)\Bentley\MicroStation\mdl\include into the "Additional Include Directories" field. issue: I get the error message #error: Define the Int64 types. resolution: In bentleytype.h where the error appears there is an #else / #endif section that just has the error message. I'm guessing this is because I'm on a 64-bit computer. I would think we could still build since VS is 32-bit. I commented out the #error ... line and then copied the typedef __int64 statements from the top section. This was a total guess so this may be wrong but it got me past the compiling aspect of this error. Any one know what should be here? issue: I get the error message: #error: this gen_dloadlib.h intended only for winNT resolution: I have no idea how to get around this so I just commented out the error for now. Any ideas how to do fix this properly? issue: Cannot open the include file microstationapi.h. resolution: Added C:\Program Files (x86)\Bentley\MicroStation V8i (SELECTseries 1)\MicroStation\mdl\MicroStationAPI to my Additional Include Directories in the Project Settings issue: Cannot open include file MSTNToolWizard1ToolCmd.h resolution: Not to sure what to do with this one since the file doesn't see the file doesn't exist anywhere. I commented out every where it was included for now. Anyone know what to do with this? issue: CMD_MSTNTOOLWIZARD1_ACTION_PLACE (and others) undeclared identifier resolution: I'm guessing these are suppose to be in the MSTNToolWizard1ToolCmd.h I couldn't find in the last issue. At this point I quit, figuring I need to get the correct answers for the above issues first.
Any thoughts on any of this would be much appreciated.
Thanks,
Mike
Unknown said:issue: Cannot open the include file mdl.h (and many others)
Unknown said:Cannot open the include file microstationapi.h
When you run the development environment batch file mstndevvar.bat it uses Windows environment variable MS as the base to set the include folders. When you install the SDK, the installer adjusts that batch script to point MS at the correct location.
The Wizards are a freeware add-on from Bentley Systems. Because they are copied, rather than installed, they don't know where MicroStation is located. We need to define, at Windows level, the location of the \MicroStation folder using environment variable MS. In addition to MS, there are a number of other Windows environment variables you may find it convenient to define.
Once MS is defined, you can use it in both bmake projects and in Viz Studio projects. Add the following to the Additional Include Directories setting of Viz Studio when building an MDL project …
$(MS)mdl\include
Add the following to the Additional Include Directories setting of Viz Studio when building a MicroStationAPI project …
$(MS)mdl\include $(MS)mdl\MicroStationAPI
Unknown said:#error: Define the Int64 types
This has nothing to do with Windows 64. MicroStation V8 uses 64-bit integers irrespective of the operating system. Both Windows 32-bit and Windows 64-bit provide the __int64 data type, and so does MDL. The MDL #include files need to know whether you're developing using bmake or Viz Studio so they can either use the available 64-bit data types or defined their own.
When you write a bmake script and %include mdl.mki, it pulls in the relevant definitions.
When you're building with Viz Studio, you need to #define winNT early on in the #include chain. Some MDL header files do that for you — for example, msmfc.h. Add that symbol to the Viz Studio pre-processor list, or put this definition in one of your headers (e.g. stdafx.h, if you're using a precompiled header) before including the Bentley headers …
#if !defined (winNT) #define winNT #endif
Unknown said:#error: this gen_dloadlib.h intended only for winNT
With winNT defined, you should find that most of those errors disappear.
We wrote some articles about Viz Studio and MicroStation development that are published on our website.
Regards, Jon Summers LA Solutions