If you are not familiar with mean.io, it is a boilerplate/framework using the MEAN stack (Mongodb Express Angular Node.js, see http://mean.io).
The issue I encounter is that I cannot create a project "From existing Node.js code" with this setup.
1. mean init myApp
2. cd myApp && npm install (at this point we have a starter kit for an app using the MEAN stack)
3. In VS try to create a project "From Existing Node.js code", use the myApp folder
4. I see "Importing project" then "Ready" but the project does not open.
5. Try to open the .njsproj manually and you get "Object reference not set to an instance of an object." then nothing
If you skip the npm install and create the project at this point, you will be able to see the files in the solution explorer but if you close/reopen the solution the project is broken and won't load.
There is something in there that Node.js tools for VS doesn't like in there but I could not figure out what.
Comments: Ironically, I have just hit that very same exception while investigating something else... Yep, the fix would be to check `json` for null before doing anything else. This will be fixed in the next build, of course. With the current sources, are you having troubles trying to build them, or hitting new bugs that you haven't seen before while running the resulting build? Any bug reports on bleeding edge stuff are especially appreciated, since this lets us iterate quickly and put the fixes out for the next release.
The issue I encounter is that I cannot create a project "From existing Node.js code" with this setup.
1. mean init myApp
2. cd myApp && npm install (at this point we have a starter kit for an app using the MEAN stack)
3. In VS try to create a project "From Existing Node.js code", use the myApp folder
4. I see "Importing project" then "Ready" but the project does not open.
5. Try to open the .njsproj manually and you get "Object reference not set to an instance of an object." then nothing
If you skip the npm install and create the project at this point, you will be able to see the files in the solution explorer but if you close/reopen the solution the project is broken and won't load.
There is something in there that Node.js tools for VS doesn't like in there but I could not figure out what.
Comments: Ironically, I have just hit that very same exception while investigating something else... Yep, the fix would be to check `json` for null before doing anything else. This will be fixed in the next build, of course. With the current sources, are you having troubles trying to build them, or hitting new bugs that you haven't seen before while running the resulting build? Any bug reports on bleeding edge stuff are especially appreciated, since this lets us iterate quickly and put the fixes out for the next release.