Nice article. I’m sure many folks might not appreciate that you can create and develop the app entirely separate from the asp.net back end - i.e. it doesn’t logically depend on the app.net core build at all as the build of the production app is performed with npm and can just be lifted out of the web app directory. Curious about which route you would take for a new project? I went for 2 separate projects - I like that I can build and deploy the app separately from the back end in CI - makes a nice logical division between the 2 parts of the code base as well I think.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Nice article. I’m sure many folks might not appreciate that you can create and develop the app entirely separate from the asp.net back end - i.e. it doesn’t logically depend on the app.net core build at all as the build of the production app is performed with npm and can just be lifted out of the web app directory. Curious about which route you would take for a new project? I went for 2 separate projects - I like that I can build and deploy the app separately from the back end in CI - makes a nice logical division between the 2 parts of the code base as well I think.