Visual Studio .NET - [18] :: Программы :: Компьютерный форум Ru.Board

Получил ответ от разработчика Process Hacker с подтверждением обнаруженных мной проблем (Issues#109 присвоен статус Bug) - Это наша беседа с dmex-ом по поводу изменений в VS2017:

Код:

MS changed patch to msbuild.exe binary thats needed update ./build/internal/build.ps1 #109

@VictorVG
VictorVG commented 15 hours ago

Summary build problem:

.\ProcessHacker\bld.cmd"
Getting build information... 3.0.404 (Update solutions to Visual Studio 2017)
Setting up signature files [SKIPPED] (VirusTotal build key)
Building ProcessHacker [ERROR] C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [.\ProcessHacker\trunk\phlib\phlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140Microsoft.Cpp.Platform.targets(57,5): error MSB8020: The build tools for v141 (Platform Toolset = 'v141') cannot be found. To build using the v141 build tools, please install v141 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution". [.\ProcessHacker\trunk\phlib\phlib.vcxproj]

VS2017 installed, I set %VS150COMNTOOLS% (installer not set any enveronment, but files is copyid), but this messages is display an over and an over.

also I have build error for x64 plugin Extended tools

Error C1001 Internal error in to compiled files :: ExtendedNotifications :: .\processhacker\trunk\plugins\extendednotifications\gntp-send\growl.c string 70

then have Access Violation in to link.exe, then stop ...

Also question do you enveronment needed make? Curreent enveronment list:

Path=
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC;.py;.pyw
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2a07
VS100COMNTOOLS=$INSTALLDIR\Common7\Tools
VS140COMNTOOLS=$INSTALLDIR\Common7\Tools
VS150COMNTOOLS=$INSTALLDIR\Common7\Tools
VSSDK140Install=$INSTALLDIR\VSSDK
VSSDK150Install=$INSTALLDIR\VSSDK\

Help needed...

@VictorVG
VictorVG commented 12 hours ago

I found thats point needed correct - is ./build/internal/build.ps1 :: function BuildSolution([string] $FileName)

Old value $msBuild = :

function BuildSolution([string] $FileName)
{
# Set msbuild path (TODO: Do we need the 32bit version of MSBuild for x86 builds?)
# Needed change patch up to new msbuild.exe location
$msBuild = "${env:ProgramFiles(x86)}\MSBuild\14.0\bin\amd64\MSBuild.exe"
# Get base file name

needed change up to new value $msBuild = :

function BuildSolution([string] $FileName)
{
# Set msbuild path (TODO: Do we need the 32bit version of MSBuild for x86 builds?)
# Change patch up to new msbuild.exe location!
$msBuild = "${env:ProgramFiles(x86)}\Microsoft Visual Studio\2017\{vs_type}\MSBuild\15.0\Bin\amd64\MSBuild.exe"
# Get base file name

then M$ move msbuild in to new location and build is [SUCCESS] for r402.

dmex commented 37 minutes ago

Yep, the location for msbuild has been changed but that is not the only problem.

The main issue is that since msbuild is now part of the Visual Studio installation there are other issues:

All msbuild related registry configuration (e.g. installation location) are now non existent.

Separate folder paths for msbuild depending if Community, Professional or Enterprise versions of Visual Studio were installed.

Users can customize the install location for Community, Professional and Enterprise in completely different folders and hard drives.

Microsoft recommends this tool: https://github.com/Microsoft/vswhere

We need to use the ISetupConfiguration2 COM interface in order to discover the installation path of Visual Studio and check for msbuild (just like the vswhere tool).

I'm testing those changes but it'll take some time...

.
Так что стоит взять на заметку ибо коли мы на это нарвались, то зачем всем заново делать ту же работу по поиску и устранению проблем для которых известны способ предотвращения и решение если они у вас возникли?

Добавлено:
По подсказке dmex скачал утилиту MS vswhere.exe v1.0.47.17602 (Visual Studio Locator) и её исходники с гитхаба. Очень интересно, потому цитирую выписку из README.md без перевода поскольку то, что там написано может помочь в устранении ряда проблем при использовании VS2017:

Цитата:

Visual Studio Locator
=====================

Over the years Visual Studio could be discovered using registry keys, but with recent changes to the deployment and extensibility models a new method is needed to discover possibly more than once installed instance. These changes facilitate a smaller, faster default install complimented by on-demand install of other workloads and components.

vswhere is designed to be a redistributable, single-file executable that can be used in build or deployment scripts to find where Visual Studio - or other products in the Visual Studio family - is located. For example, if you know the relative path to MSBuild, you can find the root of the Visual Studio install and combine the paths to find what you need.

You can emit different formats for information based on what your scripts can consume, including plain text, JSON, and XML. Pull requests may be accepted for other common formats as well.

Example

If you wanted to find MSBuild - now installed under the Visual Studio 2017 and newer installation root - you could script a command like the following to find the latest version installed.

Код:

@echo off

for /f "usebackq tokens=1* delims=: " %%i in ("vswhere -latest -requires Microsoft.Component.MSBuild") do (
if /i "%%i"=="installationPath" set InstallDir=%%j
)

if exist "%InstallDir%\MSBuild\15.0\Bin\MSBuild.exe" (
"%InstallDir%\MSBuild\15.0\Bin\MSBuild.exe" %*
)

You can find more examples in our wiki.

Добавлено:
P.S.

Hunta

Это ваши личные представления, хотя и неточные, и если вам интересно, то давайте поговорим в ПМ или в другом месте чтобы другим не мешать.

Насчёт стоимости накопителей вы неправы - стоимость массовых накопителей (по статистике доли данной ёмкости в каждом классе) начиная с момента их появления всегда располагалась примерно в нижней части среднего ценового диапазона для их класса иначе производство становится убыточным и прекращается. Это банальная экономика - изделие производится до того момента пока на рынке существует на него спрос и заменяется новой моделью по мере готовности той к производству, хотя новая модель не обязательно будет иметь какие либо внутренние отличия от прототипа или смены названия.

----------
Жив курилка! (Р. Ролан, "Кола Брюньон")
Xeon E5 2697v2/C602/128 GB PC3-14900L/GTX 1660 Ti, Xeon E5-2697v2/C602J/128 Gb PC3-14900L/GTX 1660 Ti

Модерирует : gyra, Maz
Версия для печати • Подписаться • Добавить в закладки
Страницы: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51