Roo understands the api contracts, so I don't have to explain the types in react.
Roo understands what the api is needed for and can design from top to bottom based on the scope of the app.
It is easy to pick up a new tool, like hangfire. Roo just sets everything up.
2/2
I'm having an absolute blast developing a .net + react app in a mono repo with Roo utilizing Claude.
Using memory bank to explain the scope, coding patterns, styles, preferences, etc...
1/2 ๐งต
@DevLeaderCa Honestly, with more and more help from ChatGPT or other AI. Unless it's just pure interest, then there is not much point. Do you really want to know what a similar code would look like, ask your go to AI
Aspire 9 upcoming features ๐งต:
First, you'll be able to use Aspire 9 with .NET 8 and .NET 9! It will no longer require a call to dotnet workload install, and instead uses an MSBuild SDK. This should simplify CI/CD integration and getting started immensely! All you need is NuGet!
#dotnet #aspire
@milan_milanovic Blazor or react. I like the new dotnet Api with react(typescript) template.
Luckily I get to experiment a bit from time to time at work.
We generally use react as our frontend devs swear to not use blazor. So it is just me on smaller projects now and then
@Saggn@florinpop17 Omg ๐๐ There is no releasing to test first, everything with kids is production related, unless you count the first kid as a test kid (which is fair play). And I can say that, since I have two