For the past 2 years my teams UI project and server side projects lived alone in separate git repos. Now they are one and the team would like to be able to kick off the .Net core application and trigger an Aurelia build. Has anyone done that and how did you go about doing it? I know I can just have pre/post build execute the build and call it a day.
1 Like
I usually make a bat file, containing a dotnet build/publish step and and au build step after that.
the dotnet build triggers nswag, which creates a ts client in the aurelia app, hence the serial execution.
2 Likes
The more I think about this the more I just want to leave it the way we have it (2 independent processes). I don’t like having to stop the full system to make a change that doesn’t require a full rebuild of the other. Thanks
1 Like
We have a few .net core (2&3) web apps using aurelia. Some are using the 2 method approach where we run 2 terminals; dotnet run or dotnet watch run for CS changes and au run for aurelia. Using a bat file is fine too and we have those as well. We also have some of the apps using in .NET app.UseWebpackDevMiddleware() in startup.cs. It runs your .NET app and clientside webpack and will rebuild and refresh on clientside changes all with a dotnet run or by running debug with Visual Studio.
There are a few github slns you can grab for starting points, use the aurelia CLI to build a new dotnet/aurelia project, and here’s a post talking about using HtmlWebpackPugin in .net core 3.
Having it built in to your c# side makes it easier for non frontend devs to kick off a local dev build by using the terminal or clicking the debug button in Visual Studio. My own preference is having it separate as I have more control over what’s running and how it’s running.
2 Likes