1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\VC\VCTargets\Microsoft.MakeFile.Targets(43,5): warning MSB8005: The property 'NMakeBuildCommandLine' doesn't exist. Skipping...
Just starting out . . . Previous limited experience using V8i MDL.
Trying to get started to do some converting of my V8i mdl apps to Connect. Battling to get the environment set up.
I have VS2017 Installed.
Connect SDK (v10.13.00.48) builds all examples successfully. I had to download .NET Framework 4.6.2 to get it to eventually work.
'devenv' invokes VS2017 ok.
When trying to "Build" MyApp.sln, the following error occurs.
Any ideas please?
I was following the advice as per the Bentley Video on YouTube, the "MyApp" in C:\Program Files\Bentley\MicroStationCONNECTSDK\examples\DialogBoxes\myapp\MyApp.sln, just to make sure everything is working. It is a Bentley app - not mine.
Jon, I run VS2017 by keying in devenv in the Connect SDK window, as per the video (Number 3). At the end of the video, Swarnila Set suggests the user then load and build the MyApp solution in the dialog box examples supplied with Connect. I presume this is to show the user that all is in order - but I receive the error as indicated earlier, so all does not seem to be well. The video then ends, so it is not known what the outcome should be.
John Francis said:I run VS2017 by keying in devenv in the Connect SDK window
As far as I can tell, you're doing everything right. For each new CONNECT SDK, I confirm that it is able to build all examples. In the past, I have run into your sort of build problems and like to confirm that Bentley haven't broken something during the update. I verified that Update 13's SDK builds correctly when it was published in August 2019.
Some of us have several years experience of working with the CONNECT SDK and consequently have several years of installed Microsoft software to build MicroStation CONNECT apps. I think your problem boils down to having a new installation. Your installation of Viz Studio is probably OK, but the SDK tools are having trouble finding it. The build tools have no history with you and, in particular, no historical records in the Windows Registry. I don't know why that is a problem, but Robert Hook is the SDK configuration guru and I hope he can help you.
In the meantime, search this Forum for Visual Studio 2017 and see if those results provide any clues — particularly this one.
Regards, Jon Summers LA Solutions
Thank you for your time Jon. I will persevere.
Hi John Francis,
Jon was/is certainly on the most likely path. Just yesterday I have posted some SDKPreviews MKI Files (please make sure to read the referenced "NOTES"), that help more consistently target Microsoft Visual Studio versions (latest modified configuraitons) and .NET Runtime requirements (enforced better) and (Jon's suspicion) these conditions in a completely clean install environment. All these changes will be incorporated into MicroStation CONNECT Edition SDK Update 14, but area available (with caution/notes) now in the link above. Please overlay these files and confirm if your issue is resolved. Then ensure a clean install when finally moving to our Update 14 release when its time.
Thank you and HTH,Bob
Thank you Robert. I will give this a try. To re-cap, all the examples build without any issues. It seems that VS2017 is not "seeing" any Bentley info. I have tried creating a new project using a Bentley template as you have shown in this forum, but there is no "Bentley" option in the create new project window. I hope this sheds some light . . .
Just so you know, the current Bentley example build process is mostly built using bmake (a Bentley standard "make utility") and the BuildAllExamples.bat in the Examples folder dynamically executes bmake against the current arrangement of examples having .mke files (yes, even examples that only have Visual Studio managed projects or solution files available). Bmake is used for consistency and recommended for compiling the examples or projects you may create/derive from those examples. Visual Studio is typically used for Creating and Editing Code and Debugging Code in the development process, and builds mostly through Bmake in the developer shell.
The current SDK Previews > Visual Studio Extensions currently apply only to VS2015 and are in need of update (by me) for VS2017+. It is in my backlog, but I do not have an updated .vsix project at this time and the changes I make/commit should allow the templates to get into product builds and allow us to provide further development and updates more readily.
Artur Goldsweer may be close to posting some intermediate manual steps to effectively create new VS2017 projects in the interim. I will check with him shortly and see if he can provide an update for the work-around/WIP Template process. We will reply back to this thread shortly.
HTH,Bob
Thank you Robert. As a new user (to Connect) I am completely in the dark as to how to proceed with developing apps in this new environment. I was following some examples and info which I have been reading up on, so as to try to become acquainted. I did some mdl development for V8 and V8i with some very good results, but never progressed in the VS environment. When trying to progress here, and seeing these error messages, it has been somewhat frustrating. Thanks for this info about bmake - that helps me a lot. I was under the impression that all development can be now done in VS, which is not the case - just to be used for editing.
Thanks again - I will trundle along, and get there eventually. Much appreciated.