kudu: node.js deployment: Error MSB3428: Could not load the Visual C++ component "VCBuild.exe"
Issue: npm deployment produces the following error
remote: Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
remote: MSBUILD : error MSB3428: Could not load the Visual C++ component "VCBuild.exe". To fix this, 1) install the .NET Framework 2.0 SDK, 2) install Microsoft Visual Studio 2005 or 3) add the location of the component to the system path if it is installed elsewhere. [D:\home\site\wwwroot\node_modules\tsd\node_modules\bufferstream\node_modules\buffertools\build\binding.sln]
To reproduce:
- enable git for a azure web site
- clone locally
- add a package.json (see contents below)
- git push to trigger deployment
package.json
{
"name": "s",
"description": "s",
"version": "0.6.0",
"author": {
"name": "Microsoft Corporation"
},
"private": true,
"engines": { "node": ">= 0.10.0 < 0.11.0" },
"dependencies": {
"tsd": "*"
}
}
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 1
- Comments: 31 (17 by maintainers)
Commits related to this issue
- Including socket.io as native build fails in Azure Website https://github.com/projectkudu/kudu/issues/1076 — committed to DanielLarsenNZ/Jukebox-30 by DanielLarsenNZ 10 years ago
- Add Environment variables required by MSBuild and node-gyp for building native projects. Needed for #1076 — committed to projectkudu/kudu by ahmelsayed 9 years ago
- Add Environment variables required by MSBuild and node-gyp for building native projects. Needed for #1076 — committed to projectkudu/kudu by ahmelsayed 9 years ago
Hi @davidebbo,
We’re having an issue with the following module which is not in the list of tested packages: lwip. Repro and deployment logs can be found here: https://github.com/Benjiiim/azure-appservice-test
Any advice if this should work or if we need to install more dependencies through the custom script, would be greatly appreciated.
Thanks
Actually, every module depending on node-gyp in my opinion. Your can find a list here.
Take dependencies of dependencies into account. For example, karma and protractor need socket.io.
Database drivers (sqlite3, pg/ng-native, node-oracle, node-mssql (not sure), etc.) …
Every time that I want to love Azure I run in to issues like this and end up struggling for hours trying to figure out work arounds.
This seems like a very silly limitation as all it would take to fix it is installing the appropriate build tools. Is there any plan to fix this or are we left to figure out workarounds indefinitely or switch away from Azure to a competing cloud computing provider?