dotnet core and angular node dependency?

Question

Having a hard time trying to figure out why my dotnet new angular application has a node dependency when running through iis? Using Visual Studio Code and dotnet core 1.0.4, after publishing, my application still has a dependency on node.js? Not sure why. We are running the application through iis, but our production server does not have node installed and this results in a 500 status code. We are using Microsoft spa package which has angular 2.

Has anyone else had any similar issue?

How can I remove the node dependency?

Stephen Wilson · Accepted Answer · 2017-06-06 15:00:27Z

1

It looks like your using the Microsoft.AspNetCore.SpaTemplates for this. If so, you have two options to create a production build:

Use the command dotnet publish -c Release
Use the publish option under the build menu in Visual Studio 2017

A good tutorial and walkthrough can be found here

answered Jun 6, 2017 at 15:00

Stephen Wilson

1,5141 gold badge15 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Greg Brethen Over a year ago

so by using option 1, then there will be no node dependency?

Stephen Wilson Over a year ago

Correct, once you do a production build, any web server capable of serving static files should be able to host your application.

Praneeth Reddy · Accepted Answer · 2017-06-06 14:53:33Z

0

You need to deploy the build.

you can get the build static content through.

 ng build --prod --aot

It will create a dist folder deploy that code.

answered Jun 6, 2017 at 14:53

Praneeth Reddy

4243 silver badges7 bronze badges

Collectives™ on Stack Overflow

dotnet core and angular node dependency?

2 Answers 2

2 Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related