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
I'm trying to use Material instead of Bootstrap in an Angular project template project inside an asp.net core 2.1 solution in VS 2017.
I'm using Angular 7, but the ClientApp won't let me remove Bootstrap, since I read Bootstrap and Angular material are mutually exclusive.
Everything worked fine until I tried to remove Bootstrap. But I want to use Angular Material instead !!
This has also wasted me an entire day, since, I decided to start afresh with a new project, yet for some strange reason the ClientApp angular project in the .net core solution insists on using Angular 5.2.0, instead of the latest. So now I've got to go through the process of updating all the package.json stuff. :(
The text was updated successfully, but these errors were encountered:
No worries, I found an article, saying just delete the ClientApp folder, update the CLI, then re-add ClientApp to the .net core project.
Still only gives version 7.0.0 of angular and not the latest, but better than nothing!
I'm trying to use Material instead of Bootstrap in an Angular project template project inside an asp.net core 2.1 solution in VS 2017.
I'm using Angular 7, but the ClientApp won't let me remove Bootstrap, since I read Bootstrap and Angular material are mutually exclusive.
The problem is when I run ng serve on the command line as instructed incorrectly here:
https://docs.microsoft.com/en-us/aspnet/core/client-side/spa/angular?view=aspnetcore-2.1&tabs=visual-studio
npm start doesn't work.
Everything worked fine until I tried to remove Bootstrap. But I want to use Angular Material instead !!
This has also wasted me an entire day, since, I decided to start afresh with a new project, yet for some strange reason the ClientApp angular project in the .net core solution insists on using Angular 5.2.0, instead of the latest. So now I've got to go through the process of updating all the package.json stuff. :(
The text was updated successfully, but these errors were encountered: