generated from Lemon-Code-Academy/lemonbot-dotnet
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Moving to .NET Aspire #109
Labels
bot
All issues related to BOT
management-tools
All issues related to the web app which manages the channel
refactor
Comments
albx
added a commit
that referenced
this issue
Oct 11, 2024
albx
added a commit
that referenced
this issue
Oct 15, 2024
albx
added a commit
that referenced
this issue
Oct 15, 2024
albx
added a commit
that referenced
this issue
Nov 2, 2024
albx
added a commit
that referenced
this issue
Nov 9, 2024
albx
added a commit
that referenced
this issue
Nov 11, 2024
albx
added a commit
that referenced
this issue
Dec 20, 2024
albx
added a commit
that referenced
this issue
Dec 21, 2024
I'm moving KITT to .NET Aspire. Up to now I decided to split each functionalities in a separate web api process. Up to now these are the Bounded Context:
The UI will be a Blazor Web App with global WebAssembly interactivity. With this feature all the project will be also migrated to .NET 9 |
albx
added a commit
that referenced
this issue
Dec 28, 2024
albx
added a commit
that referenced
this issue
Dec 28, 2024
albx
added a commit
that referenced
this issue
Dec 31, 2024
albx
added a commit
that referenced
this issue
Jan 3, 2025
albx
added a commit
that referenced
this issue
Jan 3, 2025
albx
added a commit
that referenced
this issue
Jan 11, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bot
All issues related to BOT
management-tools
All issues related to the web app which manages the channel
refactor
Analyze the possibility to move the KITT project to .NET Aspire
The text was updated successfully, but these errors were encountered: