Event banner
Event details
timheuer
Microsoft
MicrosoftWe're looking at tooling around this and how to bridge a few concepts here. One key scenario you note here that we're keen on looking into is better multiple startup project support. Is that your key scenario/win when you use the Tye tooling? We recognize that people are working more and more with multiple microservices/clients that all need to talk to each other locally and a better F5 experience is desired here. We've outgrown some existing ones. It isn't a committed feature yet, but we're discussing/designing.
it's not just micro service to be fair
it's useful in demo env / end to end / local dev
let's say you have a monolith with 3 backend (other team / can't control)
designing 3 dumb webapi with the same set of endpoint allow to work in isolation or have specific behavior
it helps designing new code if the backend did not released it for example
that also helps having isolated end to end with predictable result and not subject to backend down time / instability / authn credential
- timheuerYep, this is a good use case as well, you're confirming some things we're trying to solve for. We know in these cases solution files for .NET developers are not enough.