You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Module 7: You seem awfully certain Visual Studio users have npm installed #33
You spent a lot of time telling us how to install datatables.net via npm and simply assumed that we have npm. I'm using Visual Studio 2019, I have that node.js editing option installed, and even the command line console via Visual Studio has no clue what npm is.
I'm probably going to spend time trying to figure out a different way to install datatables.net, but I'm not going to bother with npm.
The way I see it, if the course isn't about npm, and the instructor never bothered to make sure that we knew how to get our hands on npm, and the course is marketed to beginners, then npm isn't of any importance to said course.
npm comes with Visual Studio - it's really just a powershell with a network connection to the repository - go to Tools->NuGet Package Manager->Package Manager Console.
I find it can be a bit tricky to "operate" compared to some CLI's. It seems to help if you carefully and continually use the tab-completion key while you are typing in the package location - this gets a more predictable response. And don't try to close the npm with the "exit" command - it will sometimes lock up VS. Close the window with your mouse.
Activity
stevek180 commentedon Apr 28, 2021
Sadly, the course author Scott Allen passed away over a year ago, so there won't be a response.
montoner0 commentedon Jun 9, 2021
@francisco-chavez I wonder why you didn't complain about lack of information about Visual Studio installation in the course.
costarec commentedon Dec 18, 2022
npm comes with Visual Studio - it's really just a powershell with a network connection to the repository - go to Tools->NuGet Package Manager->Package Manager Console.
I find it can be a bit tricky to "operate" compared to some CLI's. It seems to help if you carefully and continually use the tab-completion key while you are typing in the package location - this gets a more predictable response. And don't try to close the npm with the "exit" command - it will sometimes lock up VS. Close the window with your mouse.