Introduction of Microsoft.Extensions.ServiceRegistration.* packages

[thompson-tomo]

To facilitate a rich eco system which provides developers with a large amount of flexibility we should be releasing a service registration packages with the key ones being.

• Microsoft.Extensions.ServiceRegistration.Abstraction provides an interface for application to register themselves
• Microsoft.Extensions.ServiceRegistration.Aspire allows for applications to register with Aspire and provides the AddAspireRegistry method

A potential usage would be as follows:

var builder = DistributedApplication.CreateBuilder(args).**AddAspireRegistry()**;

var cache = builder.AddRedis("cache");

var apiservice = builder.AddProject<Projects.AspireApp_ApiService>("apiservice");

builder.AddProject<Projects.AspireApp_Web>("webfrontend")
       .WithReference(cache)
       .WithReference(apiservice);

builder.Build()**.RegisterToRegistry()**.Run();

With this approach we can easily use aspire registry for local development & switch to alternative in production ie Kubernetes.

[davidfowl]

This API proposal is a little bit light on details for something that you'd like to see changed before GA @thompson-tomo . Unfortunately, I don't think we'd be making any huge changes this late without fully understanding the details and implications.

Can you help us by explaining in more details what this change would look like and what it would affect?

[thompson-tomo]

The key thing is the 2 additions to the code snippet above which was taken directly from the docs:

• AddAspireRegistry() -> Indicates the registrations are to be sent to Aspire and provided by Microsoft.Extensions.ServiceRegistration.Aspire. It is Foreseeable, that the community integrates other Registry's
• RegisterToRegistry() -> Is used at the end of the build process to indicate that everything is registered. It is at this point in time which the services provided/needed are transferred to the registry in a bulk action. This would effectively going through and for the registration's actually performing the registration ie for AddRedis("")

[davidfowl]

This sounds like a cool idea that needs some more design and iteration. It's not something we will add at this point without going through those design rounds.

[thompson-tomo]

Agree, it is not something for initial release given timeline and it would need detailed design in terms of interface shape etc with implications for a number of libraries.