Replies: 1 comment
-
With the next version of the dotnet watch will support aspire apps. You'll be able to change .NET projects without tearing down the app host. If you are using visual studio today, you can use CTRL + F5 instead of F5 to launch without debugging. This will make it possible to rebuild individual projects without tearing down the app host. Persistent executable is planned but not for this scenario and not in scope for any release as yet |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
The container lifetime was added to allow containers to be persistent between runs of aspire.
Is there an option, or any plans, for this to work with NPM apps or other 'external' projects?
Our aspire project starts up multiple angular apps, they are all using the NodeJS hosting package that end up running an ng serve.
This means our angular apps have hot reload built in. But each stop/start of the aspire project tears them down and makes them build back up. This takes up an unnecessary period of time. There are only a few cases in where we would want to start the compile again from scratch for these clients.
Beta Was this translation helpful? Give feedback.
All reactions