[CONNECT C++] BMake .Net Platform issue

Hi Nabil Kherouf,

First start by opening the MicroStation Developer Shell using the Run as Administrator option and see if you can then proceed to compile the delivered ..\DialogBoxes\Myapp example. The yellow text is an indication the Developer Shell was not started or running as admin.  If you are unable to compile Myapp, proceed to verify that you have all the MicroStation CONNECT SDK > Requirements installed and configured; then try again.

HTH,
Bob

Hi Robert,

Thanks a lot. I didn't check  "Universal Windows Platform Development" when I installed VS2017. 

Now I'm faced with a new issue. I can't bmake a project that exits in a folder whose path contains spaces, is there any workaround this issue ?

Thanks,

Nabil 

Hi Nabil,

Nabil Kherouf said:

I can't bmake a project that exits in a folder whose path contains spaces

Did you search this forum (and others as well)? It was discussed many times. DOS 8.3 naming must be used when spaces exist.

Nabil Kherouf said:

is there any workaround this issue ?

My experience is that the simplest workaround is to place source code in folders without spaces ;-)

It allows to have such repos on different computers, at different places, and to do not have to always check whether Windows and files system are configured to support this feature.

Regards,

  Jan

Hi Jan,

I hope all is well with you! :)

I did unfortunately not research the answers on the forum about this issue. However, we've been aware of it in the past. We've always done what you suggested, which is avoid spaces in paths. We can't do that now as our data is on SharePoint and the path comes automatically with the spaces that our company name contains. 

What made me wonder whether there is a way of making it work, is that we have a different computer that builds the same project successfully despite the spaces in the path. I know it's strange but here's a screenshot (look at the first line):

 Any thoughts? 

Thanks,

Nabil

Nabil Kherouf said:

We've always done what you suggested, which is avoid spaces in paths. We can't do that now as our data is on SharePoint and the path comes automatically with the spaces that our company name contains

One suggestion is to obtain the short file name (i.e. 8.3 DOS name) of each path.  Use those short names in bmake.

Nabil Kherouf said:

we have a different computer that builds the same project successfully

It may be that that computer has a different Windows setting for long/short file names.  Search Microsoft sites for information about long and short (DOS) file and path names.d

If you were to posit that life would be so much simpler if bmake and other Bentley Systems tools were to accept Windows long file names, then I would agree with you.

Nabil Kherouf said:

We've always done what you suggested, which is avoid spaces in paths. We can't do that now as our data is on SharePoint and the path comes automatically with the spaces that our company name contains

One suggestion is to obtain the short file name (i.e. 8.3 DOS name) of each path.  Use those short names in bmake.

Nabil Kherouf said:

we have a different computer that builds the same project successfully

It may be that that computer has a different Windows setting for long/short file names.  Search Microsoft sites for information about long and short (DOS) file and path names.d

If you were to posit that life would be so much simpler if bmake and other Bentley Systems tools were to accept Windows long file names, then I would agree with you.