@ismcagdas
Perfect, we have used this to create the bundles, thank you very much for the clarification.
That would be great. I had a look at doing it in the batch file, but couldn't figure out how to exclude the node modules without switching it to Powershell or some other half decent scripting language. At this stage BAT files should should be like the Doedoe.
Hi Folks, I actually found the problem that was causing the issues I was experiencing, I'm not sure if it's related to other who are facing similar issues.
I was running the "Delete BIN OBJ Folder.bat" before doing a release build. I found that this was deleting some bin folders in the node_modules folder (I presume this was unintentional), which was causing the release build on the npm run create-bundlesto fail. I had not noticed this in our build output. When switching back to Debug I was clearing down the node modules folder and and doing an npm install again, which is why I did not experience the issue when developing.
Hi Folks, Could not get this working with Razor pages in a class library, but I could get it working with standard MVC Pages in the class library. I'm not too familiar with MVC but this is an option for us anyway, to separate out the various different views that we have. If anyone has success with Razor pages please let me know and I'll progress on from there, but for now the effort is not worth it, we may be best till this is supported in the base boilerplate framework.
I'm using .NETCore 2.1. I'm inheriting the controller from AbpController, and returning a view from there. It works with a very simple page, just having some difficulty with Models being passed in at the moment, they are always null on the page. I was not aware of the ABPRazorPage, I will see if that may help with my Model issues.