Msbuild error msb4132

Пригласить эксперта

npm install --global --production windows-build-tools

• 
  Показать ещё
  Загружается…
  

Теги:  MSBUILD  npm

MSBUILD: ошибка MSB4132: не удается распознать версию средства «2.0». Доступные версии инструмента: «14.0», «4.0».
PS E:ProjectnodejsStudy> npm install --msvs_version 2015
PS E:ProjectnodejsStudy> npm config set msvs_version 2015 --global```

Интеллектуальная рекомендация

Вам также может понравиться

Статьи по теме

• Версия набора инструментов Msbuild
• Windows 10 64bit под Nodejs Ошибка «MSBUILD: ошибка MSB4132: …»
• инструмент управления версиями nodejs и инструмент управления исходным кодом npm
• Nodejs Версия Управление инструментом: NVM
• Установите инструмент управления версиями nodejs (nmv), уменьшите версию nodejs
• Узел Управляющий версию и инструмент управления источником NPM
• Запись: решение проблемы отчета об ошибке установки npm
• Инструмент управления версиями Nodejs small note-nvm
• Nodejs Введение и инструмент управления пакетами и номер версии
• Введение в Nodejs и использование инструментов npm

популярные статьи

• Глава 5 Заявление о тернарной операции JavaScript
• Весенняя архитектура исходного кода-кода
• [ACMcoder] Number Sequence
• Там, где есть люди, есть реки и озера, тише ~~!
• Python выходной XML-файл
• HDU 1733 Escape (максимальный поток + алгоритм динамики)
• Hiveerver2 Конфигурация сервера и начать
• Windowsphone7 пользовательский -покраснение ввода пароля
• Spring Boot Integrate MongoDB Learning Notes (2020.11.23)
• Узнайте Ethereum Deployed Smart Contracts (4) -Remix пишет первый смарт -контракт (Ubuntu20.04)

рекомендованная статья

• SQL Server 2016: статистика запросов в реальном времени
• Tomcat
• MINDSPORE! Я любил эту существующую структуру глубины обучения!
• Пример устранения неполадок при установке Microsoft Office Communications Server 2007 R2
• Удовольствие с javascript — сводка баллов знаний
• Нарисуйте маленький Gif-домик с помощью ps (1)
• Технология сеанса Приложение — Код подтверждения Вход в систему
• Процесс компиляции и запуска Android
• Демонстрация двухслойной простой нейронной сети
• PHP извлекает возвращенные данные, последующий код продолжает выполнять инкапсулированную функцию

Связанные теги

• nodejs
• Vue
• unsatisfiedlinkerror
• Итак, библиотека
• Java Learning Plan
• java
• внешний интерфейс
• заметки
• c#
• excel

As you might be aware, PARSE service is shutting down beginning of 2017. This was a really great solution to quickly spin up the infrastructure needed to build an app. I still have some of my apps relying on that infrastructure and I think it’s time to make the move to

my own self-hosted PARSE server

(for local Development). Here you will find a quick guide through the initial configuration required to have your PARSE server up and running in no time.

PARSE is actually really easy to set up. You just need a NoSQL DB (MongoDB in this case) and then get the latest source code from GitHub to create your own PARSE self-hosted instance. My sandbox is a Windows 2012 R2 and I will guide you through the required steps in there.

The prerequisites are as follows:

• Node 4.3
• MongoDB version 2.6.x or 3.0.x
• Python 2.x (For Windows users, 2.7.1 is the required version)

Installing MongoDB.

Notice that I had to run the command twice as the folder that MondoDB needs was not there: C:datadb. I created the folder manually and then ran again the executable. Now MongoDB is up and running awaiting for connections on port 27017.

Installing Node.js.
Next step is to download and install Node.js. You can get the latest version here. I will install version 4.4.4 LTS which is the recommended for most users. Download the installer and continue clicking next until it is completely installed on your machine.

Installing Python.
The required version for Windows is 2.7.1. In my case I will install 2.7.11 as it’s the recommended version from Python. You can get the latest installer from here. Once the setup is completed you will have to reboot your machine to make sure the configuration is updated.

Downloading PARSE server example.
Head to PARSE server source code on GitHub and download the PARSE server example from here. Unzip the zip file under C:Parse for example. Once everything is in place, open node.js command prompt with admin rights and run the command npm install under C:Parse folder:

During the installation I hit a small bump with the following error message:
MSBUILD : error MSB4132: The tools version «2.0» is unrecognized. Available tools versions are «14.0», «4.0».

To overcome this issue, just install the MSBuild Tools from VS2013. This can be found here. Now we are ready to start our PARSE server.

Starting PARSE server.
Remember to start mongoDB first here as the server was restarted from installing Pyhton. MongoDB should show that its waiting for connection. Here are some logs when the system is up and running:

Configure PARSE:
Open the file index.js under C:Parse and edit the sections appId and masterKey

In my case, I mentioned the appId as ‘thunderParse’ and the masterKey as a nice key (base64 string).

Run PARSE server via npm:
Once configured, run in the same command line the command npm start.

Now parse is up and running and is ready for requests.

Configuring and Starting PARSE Dashboard.
Now that our PARSE server is running, we can configure and start the PARSE dashboard which is a web base application to manage our PARSE apps.

To get PARSE dashboard, you only need to type the following from npm:

Now we can go to localhost:4040/apps and we will see our application described there:

Testing our self-hosted PARSE server.
Now is the time to test our self-hosted PARSE server. To test it out, we just need to use curl or any other mechanism that we like. I’ve used curl and Delphi as I already had some libraries prepared for it. Here is the command with curl:

And here with Delphi:

And here are the results of the App writing to Parse server:

Next step is to bring this online and host it somewhere else like Heroku, AWS, AZure or Scalingo.

I hope you find this useful.

Jordi