Error: %1 is not a valid Win32 application.

[kant2002]

During the run via debugger, application does not start when I load module which has native binding it produce errors

Error: %1 is not a valid Win32 application.

I have installed
VS2015
NTVS 10-22-2015 Dev Build
NodeJS 4.1.1

[mousetraps]

This looks like an error with the native module, not with NTVS. Have you tried running the app via the command line?

[kant2002]

Yes, I do try. With command line working fine.

[kant2002]

I suspect that this is something with configuration on my PC, not NTVS per se. But this could be good opportunity for docs.

[mousetraps]

Native modules are always annoying... Probably some env vars are amiss or something. Maybe try to debug with automatic exception handling turned on?

[mousetraps]

(In NTVS, that is, not NTVS src)

[kant2002]

Where could I find this setting? in the Tools -> Options -> Node.JS Tools, don't see anything like that.

[mousetraps]

Ctrl + alt + E, select all node.js exceptions

[kant2002]

Aa, this one 😄 . Let me try.

[kant2002]

I swamped with ENOENT errors

Below full stack trace from command line

module.js:355
  Module._extensions[extension](this, filename);
                               ^
Error: %1 is not a valid Win32 application.
PROJECTROOT\node_modules\lwip\build\Release\lwip_image.node
    at Error (native)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at PROJECTROOT\node_modules\lwip\lib\Image.js:3:22
    at Object.<anonymous> (PROJECTROOT\node_modules\lwip\lib\Image.js:16:3)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)

[kant2002]

BTW: When I run application from Node.JS interactive Window everything is working.

[mousetraps]

Hrm... I've been using lwip this past week and haven't run into any issues in VS. I have a hunch about what it might be, though... Could you try printing out process.version and process.arch in both your running app and in the interactive window and report the results? I have a feeling there's a node version / architecture discrepency at play here...

[kant2002]

From console

process.version = 'v4.1.1'
process.arch = 'x64'

When running from VS

process.version = v0.12.7 
process.arch = ia32

[billti]

So it looks like the native module runs fine in Node v4 x64, and not Node v0.12 x86 then. I take it you have both installed on the box. If you point to the Node v4 .exe location for the project properties to launch does it run fine?

[kant2002]

Brilliant!! @billti, I thought that you are using some internal version of Node. Forget that it could be configured in the project settings. Thanks a lot!!!

[kant2002]

Maybe it is so simple, so it is good to put it on the wiki, in the some 'well-known issues' page. I don't see such page, but I think would be good to have something like that. What do you think?