the newest node.js 0.12.0 doesnt work together with the sqlite3 package. i found nvm for windows: nvm for windows https://github.com/coreybutler/nvm-windows/releases . i thought nice to use the old and new node.js versions on 1 computer.
after installing nvm for windows in c:\nvm , i get in visual studio 2013 in debug that there is a fault in npm : illigal characters in path resulting in exit debug program . Outside Visual Studio it works fine.
As I mentioned in my comment, I had a very similar problem. After installing node.js for purpose of using gulp I could not do a successful build. I would get the following error:
C:\Visual Studio
Projects\MyProject\packages\RazorGenerator.MsBuild.2.2.6\build\RazorGenerator.MsBuild.targets(21,9):
error : Illegal characters in path.
After searching around I guessed that the problem had to do with the node.js utilizing "illegally" long path names. For some background go here: https://github.com/joyent/node/issues/6960
My solution was to install the Flatten Packages tool: https://visualstudiogallery.msdn.microsoft.com/cd0b1938-4513-4e57-b9b7-c674b4a20e79?SRC=VSIDE
I ran flatten packages on the "node_modules" folder, tried to build (failed but with a different error), restarted Visual Studio, and everything now seems to build ok. Hope this helps.
UPDATE
One thing to keep in mind is that, by design, Flatten Packages will move files up in the directory structure. As a consequence, however, Visual Studio will still look for some of the folder/files in the OLD location; VS will shows the [!] symbol to show that the file was there but no longer is. These old file references can gum up the build, so you need to simply delete these old file references/directories.
Since this post still is on top when searching for this topic..
I also had this problem with "Illegal characters in path" and found that the best solution for me and my team was to make Visual Studio use the latest npm version (>= 3.0) since the node_modules folder depth doesnt get as deep as with npm2 (used by Visual Studio).
This solution will work for you in the background, not needing to run extra commands and tools for flattening the folder.
See my post here for a complete how to: http://newsweb.se/how-to-use-visual-studio-2015-with-latest-nodejs-npm/
Related
I am trying to install the netCDF4 package for Python 3 on my Windows 8 PC. I have already worked through some bugs like adding the visual studio directory to PATH. However, I don't make good headway with the current issue:
when I run
pip install netcdf4
the output indicates that the file io.h could not be found. In fact, a search across the C:/ directory shows that I don't have this file on my PC.
An internet search indicates that the file io.h is somewhat outdated and not used anymore. Is there a way that I can get it from somewhere?
Is there a place where I can
After some more trial and error, I found a solution and I hope that by posting it here it might save somebody else some time.
The only Visual Studio environment that I had installed was Visual Studio Community 2017. What solved my problem was that, additionally, I installed the default (= not changing any of the default modules) version of Visual Studio 2017 Desktop Express. Afterwards,
pip install netcdf4
worked flawlessly.
In Visual Studio Installer, I selected the Node.js development option. It runs successfully. But, if I try to run cmd node -v. It tells me node does not exist.
I tried a few other things including uninstalling and reinstalling the Node.js development option in VS Installer. Plus installing the latest version of node from the website.
However, when I try to run the pre-packed Angular solution that comes with VS 2017 I have issues. The solution will not even start.
The best I have been able to do is install Node 6.10.3. Once I do that, the web site comes up. But, I get a JavaScript error in the vendor.js file. I am able to continue but I get this error when I try navigate to another menu item. Plus the Hot Module Replacement does not seem to be working. (It does not automatically recompile my TypeScript file if I made a change).
I think the key is getting the Node.js development option installed correctly since I am able to run the pre-packed Angular solution on another PC and the Hot Module Replacement works fine.
Please let me know if anyone has any ideas on how to resolve.
I had a similar, if not the same, issue. Check the Visual Studio installation directory (2017 Professional in this case) for Node:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Microsoft\VisualStudio\NodeJs
If the executable is there, add the directory to your PATH.
I've tried everything, I have the proper version of Python (Python27), Windows SDK 8.1 is installed, Visual C++ is also installed, but the build still fails. I'm using Visual Studio 2015 Community editor btw. When I try to execute node-gyp buildfrom cmd I get the following error:
> C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.t
argets(44,5): error MSB8020: The builds tools for v140 (Platform Toolset = 'v14
0') cannot be found. To build using the v140 build tools, either click the Proj
ect menu or right-click the solution, and then select "Update VC++ Projects..."
. Install v140 to build using the v140 build tools. [C:\Users\Programming PC\Do
cuments\GitHub\node-addon-examples\1_hello_world\node_0.10\build\hello.vcxproj]
This error prompted me to go into to Visual Studio and see if the project can at least build and run from there, it doesn't.
Please help I looked at all of the other questions pertaining to this issue but none of their solutions have helped me.
Took a lot of research but I found the solution(s). First, to get rid of the MSB8020 error either add the VisualStudioVersion environment variable and set it to your version of visual studio or execute node-gyp build with this flag /p:VisualStudioVersion=14.0 (In my case).
I actually got different errors after I solved this one and I believe they are well worth mentioning.
Error MSB4175 then showed up, basically indicating that it cannot find Microsoft.Build.Tasks.v12.0.dll (Do a search on this .dll to find out where its usually located), copy and paste it to the path that it's looking for it in.
Now here is the kicker, the last error that interrupts node-gyp is because of a missing .lib file. Npm doesn't create the following file ...\.node-gyp\4.3.1\Debug\node.lib. So you need to go here and download a node.lib and mkdir Debug\ and put node.lib in there.
Afterwards node-gyp should build without errors.
I installed cordova globally via npm (nodejs version 5.1.0)
Cordova v5.2.0
When I run cordova run android or cordova run or cordova build it does nothing, no errors, just a blank line (in powerShell no blank line at all)
Also with option --verbose or -d
Even when I make a completely new project it won't work.
Wat does work is cordova compile, but the compiled .apk is an old version. Probably because prepare moves the latest files from www into the platforms folder.
Now I could manually copy those of course, but that's not a solution to this.
I did just freshly install android studio and jre8, i thought it might need jre7, but after installing that, no change. (changed %PATH% var as well)
Then I remembered that cordova needs ant which is never mentioned here: https://cordova.apache.org/docs/en/latest/guide/cli/index.html
But after adding all the right %PATH% variables, still the same problem. Nothing.
I've been looking for error logs but I can't find any (%USERPROFILE%/.cordova). Any suggestions where to find them?
Furthermore, node works fine for the rest
I've tried removing and re-installing cordova as well.
I do see the npm.exe process running for about one second.
Also, running windows 10
javac 1.8.0_65
adb version 1.0.32
Visual Studio 2012 becomes corrupt when I tried to install WiX 3.8. This is what happens...
Following a successful WiX install I try to run VS2012 and get the splash screen followed by this error "Exception has been thrown by the target of an invocation". Clicking on ok simply places me on the desktop. The only solution is to re-install VS2012. I tried un-installing everything and starting over several times but no luck. I cannot find any information on this exact topic anywhere online including WiX forums. Does anyone have ideas on what I should try next?
Rudy
I just had the same problem after installing WiX 3.8. Basically even more problems as Explorer and other system application could not be started anymore.
The root cause was a change in the PATH environment variable which ended up to be more than 2048 chars and therefore the %windir% var was not accessible anymore.
Try to remove some unnecessary paths in PATH environment variable as described here:
https://superuser.com/questions/355594/windows-7s-path-and-environment-variables-are-corrupted
At least for me, it worked afterwards again.
Cheers and good luck