Its very simple, it helps to build, orchestrate and manage microservice environments/applications. All of the things that Aspire does were normally handled manually minus a few automated scripts that had to be written by you to help in this process. It has service discovery built-in, whereas in the past this was done manually via some custom nuget package or code. etc, this is just one aspect, the dashboard gives great insights as to how your microservice environment is running, etc....
I've played around with it a few weeks ago. I like that it basically just configures everything for you and I can just click "Run" in visual studio (not vscode, but visual studio) and the debugger is attached and everything... breakpoints work, integrates with docker nicely (just make sure you are running docker desktop in the background) this is basically a full-stack + deployment system ready for you. Personally, I do like having this as a kind of baseline to develop upon. It reminds me of the days of winforms where it was easy to build and deploy with something like clickonce
It looks like a progression - Service Fabric -> Kuburnetes -> Container Services -> Aspire - where configuration is simplified at each generation of evolution of the ecosystem
OK. Thats how much you love it and you already know about Aspire and what it can do. But I'm a Maui developer, so what is Aspire and can it help me? Oh and what is the learning curve like?
So…Orleans, DAPR…now Aspire? Are they competing or complementing tech stacks? I have all of them on my TODO list but not sure if one supersedes the other or what would be the best patterns to use them together. The more that comes out the more I procrastinate :-/
Correct me if I am wrong but this seems to spin up one container per service compared to related container services or functions. So wouldn't it make small projects a lot more expensive to run with service instance utilization is low? It would also be good to have a VSTS deploy template (if it does not exist) to ensure deployments are managed rather than ad-hoc 'publish'. It looks like a great starting point for first release though.
When I use .NET Aspire, my packages for external tools like database, cache, queue must be the Aspire Package or be other? Example EFCore, EasyQ. Using other libraries I keep with this trace available? And how do a connection, once that a new container is update for each run.
You can use whatever libraries you want. If you use the aspire packages you will get telemetry, resiliency, DI integration and IConfiguration support by default. That's what it does for you. If you use EasyQ then make sure they support emitting the same telemetry if you'd like to preserve those dashboard traces.
I understood nothing from this video. For sure you need another specialist who can clearly tell the story of the product. Is it a server? Is it a platform? Is it a web-application build on top of... on top of what? Is it a Linux/Windows service that run and able to monitor applications? Where this applications are running Docker/IIS/Kestrel? 2 minutes about nothing...
It looks like infrastructure as code just moved to C# so all the configuration and services are discoverable and declared in C#, like Service Fabric used to be. It looks like it is another step toward simplifying setup of container micro services as Container Services simplified Container Clusters.
![What is .NET Aspire? [Pt 1] | .NET Aspire for Beginners](http://i.ytimg.com/vi/VHzYEtd1MDM/mqdefault.jpg)
I'm still none the wiser what aspire is.
This 1000%. I keep listening to podcasts, watching "intro" videos and none start with "this is the problem Aspire solves".
Looks like a dashboard where you can 1-click basic cloud tasks. Cloud portals are intimidating for many.
It's so obvious someone's got an earful from management and was forced to make this poor presentation :D
Its very simple, it helps to build, orchestrate and manage microservice environments/applications. All of the things that Aspire does were normally handled manually minus a few automated scripts that had to be written by you to help in this process. It has service discovery built-in, whereas in the past this was done manually via some custom nuget package or code. etc, this is just one aspect, the dashboard gives great insights as to how your microservice environment is running, etc....
It’s easier to use it than it listen to podcasts about using it 😅
I've played around with it a few weeks ago. I like that it basically just configures everything for you and I can just click "Run" in visual studio (not vscode, but visual studio) and the debugger is attached and everything... breakpoints work, integrates with docker nicely (just make sure you are running docker desktop in the background)
this is basically a full-stack + deployment system ready for you. Personally, I do like having this as a kind of baseline to develop upon. It reminds me of the days of winforms where it was easy to build and deploy with something like clickonce
Rider does this without a problem, just like publishing.
So... What is .net Aspire?
That background is extremely difficult to look at. My eyes kept going out of focus like I was looking at a stereogram.
specially in 0:39
This still tells us nothing about what it is and how it's specifically used. Why should I use this over Blazor server? It looks the same.
This is the sixth video that I'm watching about what net Aspire is and I still don't know crap
Have you even watched this video once before publishing it ?
Is Aspire like service fabric?
It looks like a progression - Service Fabric -> Kuburnetes -> Container Services -> Aspire - where configuration is simplified at each generation of evolution of the ecosystem
OK. Thats how much you love it and you already know about Aspire and what it can do. But I'm a Maui developer, so what is Aspire and can it help me? Oh and what is the learning curve like?
Well that depends on if you want your maui application to run in the cloud, doesn't it.
So…Orleans, DAPR…now Aspire? Are they competing or complementing tech stacks? I have all of them on my TODO list but not sure if one supersedes the other or what would be the best patterns to use them together. The more that comes out the more I procrastinate :-/
Correct me if I am wrong but this seems to spin up one container per service compared to related container services or functions. So wouldn't it make small projects a lot more expensive to run with service instance utilization is low? It would also be good to have a VSTS deploy template (if it does not exist) to ensure deployments are managed rather than ad-hoc 'publish'. It looks like a great starting point for first release though.
This is great; everything that was once split into individual packages and libraries is now cohesive.
When I use .NET Aspire, my packages for external tools like database, cache, queue must be the Aspire Package or be other? Example EFCore, EasyQ. Using other libraries I keep with this trace available? And how do a connection, once that a new container is update for each run.
You can use whatever libraries you want. If you use the aspire packages you will get telemetry, resiliency, DI integration and IConfiguration support by default. That's what it does for you. If you use EasyQ then make sure they support emitting the same telemetry if you'd like to preserve those dashboard traces.
I understood nothing from this video. For sure you need another specialist who can clearly tell the story of the product. Is it a server? Is it a platform? Is it a web-application build on top of... on top of what? Is it a Linux/Windows service that run and able to monitor applications? Where this applications are running Docker/IIS/Kestrel? 2 minutes about nothing...
It looks like infrastructure as code just moved to C# so all the configuration and services are discoverable and declared in C#, like Service Fabric used to be. It looks like it is another step toward simplifying setup of container micro services as Container Services simplified Container Clusters.
❤❤
Looks like they all got the same hand gesture training!
I hate it. Let the people speak without moving their hands if that is their style.
I think it's normal to gesture like that when explaining something. I do it without being trained to do so.
They are "overgestured". It seems like they are trying to hypnotise me like a Jedis.
Microsoft aspire to every human pay a monthly fee for its st....d cloud services
this is lockin tech, not good