Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Building project in production #32

Open
rafal-grycuk opened this issue Apr 12, 2017 · 5 comments
Open

Building project in production #32

rafal-grycuk opened this issue Apr 12, 2017 · 5 comments

Comments

@rafal-grycuk
Copy link

rafal-grycuk commented Apr 12, 2017

Hello, i have a problem with building application into the production. As far as i know, the output build should contain bundled css, js and html, which should be placed in the server. Unfortunately i cannot run build. Only the js files are created.
When i run npm run build i obtain error. I restored the packages but not it take no effect. The same problem is in "clean" project.
What seems to be the problem ?
2017_04_12_08_40_33_assets json_trading reactgrid_visual_studio_code

In addition there is no html generated.
2017_04_12_08_41_25_assets json_trading reactgrid_visual_studio_code

@rafal-grycuk rafal-grycuk changed the title Building project Building project in production Apr 12, 2017
@ashutosh1211
Copy link

Getting same error while building for production :( using node run build

@FluffyBucket
Copy link
Contributor

FluffyBucket commented May 19, 2017

Try replacing
const args = ['publish', 'server', '-o', 'build', '-c', config, '-r', 'coreclr'];
With
const args = ['publish', 'server', '-o', '../build', '-c', config];
In build task in run.js.
I got it working when replacing that, I am unsure however if you will still be using .net Core.

FluffyBucket added a commit to FluffyBucket/aspnet-starter-kit that referenced this issue May 19, 2017
@ashutosh1211
Copy link

or you can change the .cproj and add RuntimeIdentifier manually

image

@FluffyBucket
Copy link
Contributor

FluffyBucket commented May 19, 2017

Yes, but when I did that I didn't get a server.dll file that can run. Try running dotnet server.dll and see if you are able to run the dll without errors.
And you will still need to change the 'build' argument to '../build' since it will otherwise create a tree of build folders.

@ashutosh1211
Copy link

yes @FluffyBucket you are right. dotnet server.dll is not running.

koistya pushed a commit that referenced this issue May 20, 2017
jiangzm pushed a commit to jiangzm/aspnet-starter-kit that referenced this issue Jan 15, 2020
jiangzm added a commit to jiangzm/aspnet-starter-kit that referenced this issue Jan 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants