Hi guys,
We downloaded the Metronic 5.1 files from the .Net Zero download page, then copied the tools folder into the Metronic folder within our .Net Zero project.
We’ve then followed the steps outlined by Metronic documentation as follows: From within the tools folder we’ve: • Run npm install --global npm@latest • Run npm install --global yarn • Run npm install --global gulp-cli • Run yarn install • Run gulp –prod
After this point the file structure outlined by Metronic is different to the Metronic structure in .Net Zero From within the dist/default and dist/default/assets folders we’ve: • Run npm install <- this struggles to find all the right dependencies • Run ng serve <- this fails completely
Changes made colors in src/sass/framework/_config.scss and src/sass/demo/default/_framework-config.scss files have no visible effect even when gulp –prod is run again after applying the changes.
Are there different steps we need to take into account with regards to the .Net Zero differences of the Metronic implementation?
1 Answer(s)
-
0
Hi @DavidHarrison,
In AspNet Zero, it is a bit hard to rebuild Metronic because probably you will need to make lots of changes. I don't know Metronic's rebuild code but it probably depends on relative folder locations etc...
Because of this, we have a separate Metronic repository on GitHub <a class="postlink" href="https://github.com/aspnetzero/metronic">https://github.com/aspnetzero/metronic</a>. We re-build Metronic on this repository and copy the related files into AspNet Zero's source code.
You can follow a similar approach.
