Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
GitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Can't see what I am doing wrong but for the life of me, cannot get the debugging to work. Site runs fine. Running IIS 8. Made sure my app pool account has rights to the application folder is inetpub.
Same issue here - and apparently one that a lot of people are having now (plenty of reports in the original repo which is seemingly abandoned)... I am experiencing this on Windows 7 and Windows Server 2016 (with and without websockets enabled).
I can't quite fathom how Microsoft continues to push NodeJS as suitable for Enterprise development when the backbone of NodeJS support in Windows is IISNode. Really regretting spending the last 2 weeks writing this API in NodeJS under the assumption that Microsoft wouldn't be pushing using this unless it was stable, well documented, and well supported (none of which is true in this repo or the original one).
Unfortunately, it's unlikely that anyone will stumble upon this thread until they've already invested in this solution and then encountered problems... But if you're a lucky soul and you do find yourself here before writing your APIs with the plan of targeting Windows, I would advise you do a bit more research and question yourself on if you're making the right decision... I'm betting that most folks who have found their self wading through the issues here and in the original repo would say "NO".
I wanted to come back and share my small victory in the case that it helps anyone else... I could never get the official debugging to work, but I do have full debugging through VSCode currently.
To get debugging setup in VSCode, you need to modify your iisnode.yml and also add a new configuration to your launch.json.
In your iisnode.yml (or web.config), set the 'nodeProcessCommandLine' so that it includes '--inspect'. So for me, I have:
Next, in your launch.json, add a new configuration to Attach to Remove. So mine looks like this:
After getting everything setup, you can click on the debug tab on the left of VSCode. Then you select your "Attach to Remote" configuration from the dropdown at the top right of VSCode. Lastly, hit F5 or press the play icon next to your selected config.
Using this approach, I have been successfully able to debug my Express application hosted in IIS using IISNode.