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
Mark Anderson wrote:
"I am sure that at the Developer Conference we can answer all of your questions. There are some sessions that will have some open time and there is always the in between time."
I would love to see a class that includes the following:
Walks thru the recommended way of setting up Visual Studio to work with MicroStation development.
When do you have to use bmake and when can you build with Visual Studio
Discusses MDL, MicroStationAPI and Add-ins and talks about which are recommended for different type tasks.
Hands-on exercises with building each of the different types
It would be great to have a class like this early in the time schedule so that the other sessions would be more understandable for those that are new to MicroStation development or like me haven't done MDL in quite a while.
Sounds like you just set my prime objectives for the Tips session during the Developer Conference.
mark anderson [Bentley]
Visit me at https://communities.bentley.com/communities/other_communities/bentley_innovation/default.aspx
Hi Mike, Jon and Mark.....
So Mike, is your VS2005 setup on the Win 7 x64 O.S. fully functional and working?
If so, kudo's to you!
I looked at loading VS2005 onto my Win 7 laptop, but was scared off by several articles and forum postings I came across on the MSDN forums.
All the postings encountered many issues just to load VS2005 onto a Win 7 O.S. computer, and some of the work-arounds outlined just seemed too tedious, so I abandoned my attempt before it happened.
This looks like a great subject for a "How to" document.... ;-)
Looking forward to using it when (or if) you get it done!
Bert
Hi Bert,
I have VS2005, VS2008, VS2010, and VB6 all running on Win 7 x64. VB6 has some issues but works well enough for some of the older small VB projects which I have to tweak on occasion.
Honestly I don't remember having any (or at least not many) issues running any of the Visual Studio versions on my Win 7 x64. My company is a Bentley partner and I do customization work, which is mostly in VBA. I'm also the original developer of VersaCAD. We sold the company 25 years ago and reacquired VersaCAD (the product) about 12 years ago. So most of my VS work has been C/C++ with the updating of VersaCAD.
I wrote a VersaCAD to MicroStation translator in MDL about 20 years ago and have done very little with MDL since. I teach the VBA beginning and Advanced class for Bentley and in the advanced class show how to call MDL from VBA so I've had some recent exposure to MDL but nothing serious. My struggles with MDL now are more dealing with trying to get the "plumbing" all setup in order to edit/compile/run/debug thus this original post. I've been working thru many different tutorials, example files, & wizards and running into hitches getting many of them to work. I'm a little frustrated with myself at this point.
Anyway, sorry for the trip down memory lane, back to your question. As said I have no real problems running VS2005 on Win 7 x64. I don't think the problems I've been struggling with have to do with my computer being 64-bit. All Visual Studio versions are 32-bit programs and generally I've had no issue running 32-bit programs on a 64-bit computer, other than maybe printer drivers.
I did an internet search for VS problems running on Win 7 x64. There are some issues regarding stuff like the redirection of System32 to SysWOW64 but I didn't really see a flood of major issues. I guess it will likely depend on the kind of apps you develop and whether they are related to features that are different between x32 and x64.
If you already have VS2005 it's an easy process to install it and see if it works with your projects. You can always remove it if it doesn't work for you.
FWIW the only reason I'm using VS2005 instead of VS2010 for the MDL testing is that seems to be what Bentley folk recommend. I've got enough issues without ignoring that recommendation.
Unknown said:Is your VS2005 setup on the Win 7 x64 O.S. fully functional and working?
I have Viz Studio 2005, 2008 and 2010 installed on Windows 7 x64. There were no installation problems. The main operational problem I have is that Microsoft is becoming increasingly reluctant to permit a network directory to be used as a Viz Studio project directory. With Viz Studio 2005 and 2008 I can specify a network location for a project, but Viz Studio 2010 won't allow it.
I believe that Bentley Systems recommend Viz Studio 2005 to build MicroStation applications using C++. That ensures that Microsoft Foundation Classes (MFC) and other stuff are compatible with MicroStation. If you're not using MFC, then I believe that the later versions will work. However, Microsoft are focussing on .NET and C++ hasn't changed much over those versions of Viz Studio. The bigger changes have been in the .NET languages.
Prefer Viz Studio 2005 for MDL and MicroStationAPI development: it's 100% compatible with MicroStation and doesn't impose Microsoft-invented network restrictions.
If you're using .NET, then all Viz Studio versions use the same V2 CLR so the choice is unrestricted.
Regards, Jon Summers LA Solutions