Controller not being registered when running with webpack-dev-server about angularwebpackvisualstudio HOT 4 CLOSED

Have you checked if the webapi starts when using npm start?

from angularwebpackvisualstudio.

Yes, it still shows 404.

I think I found the reason. When doing npm start or through Task Runner Explorer, webpack-dev-server runs at 8080 port and the dotnet run part of that command runs at 5000 port. I verified by posting at 5000 port, it works. But, at port 8080, it shows 404.

Is it due to launchSettings.json file? It sets the port to 5000?

from angularwebpackvisualstudio.

The solution is implemented to separate client and server. In a real world scenario they should be separated and deployed to two different servers. So the client application on port 8080 sends requests to port 5000 where the API is running and your new controller should be answering.

from angularwebpackvisualstudio.

I understand. Will close the issue now. Thank you!

from angularwebpackvisualstudio.