[CE UPDATE 12 C++] DEVEV command unknown

Stephen Holmes said:

Any ideas...

DEVENV, used in the SDK shell, starts Viz Studio 2017 if everything is set up correctly.  Here's what I see when I start the SDK shell...

**********************************************************************
** Visual Studio 2017 Developer Command Prompt v15.9.6
** Copyright (c) 2017 Microsoft Corporation
**********************************************************************

[Windows]

  Microsoft Windows 10.0.17134.648 (64-bit), Command Shell (64-bit), Standard

[Command Line]

  "C:\Windows\System32\cmd.exe" /x /k ""G:\Program Files\Bentley\MicroStation CONNECT Edition\SDK\MicroStationDeveloperShell.bat" "G
:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\" "G:\Program Files\Bentley\MicroStation CONNECT Edition\SDK\""

  Arg: G:\PROGRA~1\Bentley\MICROS~2\MICROS~1\  [G:\Program Files\Bentley\MicroStation CONNECT Edition\MicroStation\]
  Arg: G:\PROGRA~1\Bentley\MICROS~2\SDK\  [G:\Program Files\Bentley\MicroStation CONNECT Edition\SDK\]

[SDK Environment]

MS=G:\PROGRA~1\Bentley\MICROS~2\MICROS~1\
MSCEMdlappsPath=G:\PROGRA~1\Bentley\MICROS~2\MICROS~1\mdlapps\
MSCEPath=G:\PROGRA~1\Bentley\MICROS~2\MICROS~1\
MSCESDKShortPath=G:\PROGRA~1\Bentley\MICROS~2\SDK\
MSMDE=G:\PROGRA~1\Bentley\MICROS~2\SDK\
MSMDE_Long=G:\Program Files\Bentley\MicroStation CONNECT Edition\SDK\
MSMDE_OUTPUT=D:\temp\Bentley\MicroStationSDK\


Path=G:\PROGRA~2\VI44E1~1\VC\Tools\MSVC\14.16.27023\bin\HostX86\x86;G:\PROGRA~2\VI44E1~1\Common7\IDE\VC\VCPackages;G:\PROGRA~2\VI44E
1~1\Common7\IDE\CommonExtensions\Microsoft\TestWindow;G:\PROGRA~2\VI44E1~1\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Tea
m Explorer;G:\PROGRA~2\VI44E1~1\MSBuild\15.0\bin\Roslyn;G:\PROGRA~2\VI44E1~1\Team Tools\Performance Tools;G:\Program Files (x86)\Mic
rosoft Visual Studio\Shared\Common\VSPerfCollectionTools\;C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools
\;C:\Program Files (x86)\HTML Help Workshop;C:\Program Files (x86)\Windows Kits\10\bin\10.0.17763.0\x86;C:\Program Files (x86)\Windo
ws Kits\10\bin\x86;G:\PROGRA~2\VI44E1~1\\MSBuild\15.0\bin;C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319;G:\PROGRA~2\VI44E1~1\Common7
\IDE\;G:\PROGRA~2\VI44E1~1\Common7\Tools\;C:\ProgramData\Oracle\Java\javapath;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program F
iles\Intel\iCLS Client\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Progr
am Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program
 Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;
C:\Program Files\Microsoft SQL Server\110\Tools\Binn\;C:\Program Files (x86)\Microsoft SDKs\TypeScript\1.0\;C:\Program Files\Microso
ft SQL Server\120\Tools\Binn\;C:\WINDOWS\System32\OpenSSH\;C:\WINDOWS\system32\config\systemprofile\.dnx\bin;C:\Program Files\Micros
oft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;G:\PROGRA~1\Bentley\MICROS~2\SDK\bin;C:\Users\CONNECT\AppData\Lo
cal\Microsoft\WindowsApps;;G:\PROGRA~2\VI44E1~1\Common7\IDE\CommonExtensions\Microsoft\CMake\CMake\bin;G:\PROGRA~2\VI44E1~1\Common7\
IDE\CommonExtensions\Microsoft\CMake\Ninja;G:\PROGRA~1\Bentley\MICROS~2\SDK\bin\;G:\PROGRA~1\Bentley\MICROS~2\SDK\MigrationTools\;G:
\PROGRA~1\Bentley\MICROS~2\MICROS~1\

[SDKTIPS]

   [TIP] "Type 'SDKFORUM' to go to the MicroStation Programming Community"
   [TIP] "Type e.g.'SDKSEARCH SystemCallback' to locate API specific implementation or migration details"
   [TIP] "Type e.g.'SDKSEARCH CreateLineElement VERBOSE' search across all files: SDK, ParentProduct, ParentProductWorkspace"
   [TIP] "Type 'BUILDALLEXAMPLES' to validate you build environment"
   [TIP] "Type 'BUILD [VERBOSE]' to build code with log file [optional 'VERBOSE' output]"
   [TIP] "Type  e.g.'BMAKE +avilC MyApp > BuildOutput.txt' to obtain verbose sequential build details"
   [TIP] "Type 'BDNVIDEOS' to view SDK Introductory videos"
   [TIP] "Type 'SDKMACROS' to view navigation and utility shortcut macro (aliases)"
   [TIP] "Type 'SDKTIPS' to see this list of tips again"

G:\PROGRA~1\Bentley\MICROS~2\SDK\examples>devenv

G:\PROGRA~1\Bentley\MICROS~2\SDK\examples>

One other question Jon/Jan, what version of .Net have you got showing on the title bar of the SDK command dialog mine is showing

"REQUIRES: Visual Studio 2017, .NET Framework 4.6.1"

I only ask as I thought the requirement was for .NET 4.6.2 with Update 12 

Stephen Holmes said:

what version of .Net have you got showing on the title bar of the SDK command dialog

Normal:

Admin:

Stephen Holmes said:

"REQUIRES: Visual Studio 2017, .NET Framework 4.6.1"

I only ask as I thought the requirement was for .NET 4.6.2 with Update 12 

Hi Stephen Holmes,

As mentioned above there were significant changes in re-tooling for VS2017 over prior versions and this is one item I will ensure gets cleared up. As Jan mentions the requirements placed in the developer shell title are dynamic at each startup and "ask the sdk" what the requirements are directly from the mki files (for now).  This does point to an inconsistency that I noticed and will be filing a defect for to hopefully see improved for the MSCE SDK U13 release, and hopefully some additional "lesser" public requirements vs. internal heavier ones.  I will update this response once I have a defect filed.

HTH,
Bob

Stephen Holmes said:

"REQUIRES: Visual Studio 2017, .NET Framework 4.6.1"

I only ask as I thought the requirement was for .NET 4.6.2 with Update 12 

Hi Stephen Holmes,

As mentioned above there were significant changes in re-tooling for VS2017 over prior versions and this is one item I will ensure gets cleared up. As Jan mentions the requirements placed in the developer shell title are dynamic at each startup and "ask the sdk" what the requirements are directly from the mki files (for now).  This does point to an inconsistency that I noticed and will be filing a defect for to hopefully see improved for the MSCE SDK U13 release, and hopefully some additional "lesser" public requirements vs. internal heavier ones.  I will update this response once I have a defect filed.

HTH,
Bob

Thanks, Bob
much appreciated