Open manchuwook opened 6 years ago
Have you gotten this to work with asp.net core outside of Service Fabric? Usually the problem with these massive JavaScript frameworks is getting the webpack/NPM/Bower/whatever packaging and bundling to play nice with the rest of the SF/.NET Core build process in Visual Studio. If you can get it working with just a standalone ASP.NET Core application, you're 99% of the way there, then it's just a matter of making sure your SF application package build output matches what you had working in your standalone ASP.NET Core application.
Most support forums (Gitter, StackOverflow) say to 'just use node' or 'why are you using aspnet core'?
Which are terrible answers.
How to do I get Angular 6 installed on an existing project? I like the server-side rendering, using webpack, and having SignalR - but my stuff is no longer compiling because of the error
Which pretty much breaks all of the development I've done in the past week. I've tried to add a service (SignalR injectable), 4 models, and 2 components. I suspect it has to do with the project using Angular 4 and Angular has passed it up a long time ago, with most blogs at the very least at v5.