Name must contain only ASCII letters, digits, and hyphens. (Parameter 'name')

[Depechie]

Preview 4 of Aspire gives following exception when trying to start the AppHost:

Unhandled exception. System.ArgumentException: Resource name 'basket.api' is invalid. Name must contain only ASCII letters, digits, and hyphens. (Parameter 'name')
   at Aspire.Hosting.ApplicationModel.ModelName.ValidateName(String target, String name) in /_/src/Aspire.Hosting/ApplicationModel/ModelName.cs:line 39
   at Aspire.Hosting.ApplicationModel.Resource..ctor(String name) in /_/src/Aspire.Hosting/ApplicationModel/Resource.cs:line 30
   at Aspire.Hosting.ApplicationModel.ProjectResource..ctor(String name) in /_/src/Aspire.Hosting/ApplicationModel/ProjectResource.cs:line 10
   at Aspire.Hosting.ProjectResourceBuilderExtensions.AddProject[TProject](IDistributedApplicationBuilder builder, String name) in /_/src/Aspire.Hosting/Extensions/ProjectResourceBuilderExtensions.cs:line 27

The culprit is in defining a project like:

var basketAPI = builder.AddProject<Projects.otel_Basket_API>("basket.api")

This works fine with preview 3.

[davidfowl]

Yep, we changed the naming constraints. Change the . to a dash or underscore

[michaelrbrown]

How would we handle azure cloud SQL Server automatically generated domain registrations such as this: var sql = builder.AddSqlServer("sql-chipin.database.windows.net", password);? The ".database.windows.net" is automatically assigned by default by Azure. What am I missing? If this is for cloud native services how would it not handle this scenario?

[davidfowl]

When you use aspire with azure sql the name is generated so that it is domain safe. You never add database.windows.net as the aspire resource name. Those are logical names that are used within the app model:

aspire/src/Aspire.Hosting.Azure.Sql/AzureSqlExtensions.cs

Line 24 in ced70f6

var sqlServer = new SqlServer(construct, builder.Resource.Name);

The logical name is used as input to generating a unique name for the fqdn in the azure resource.

[mateuszjarazny]

We can restrict the names of the resources to whatever. Those are logical names. I think having an override for the service discovery name is a good feature to add

Hi @davidfowl, is there any functionality that allows such overrides already? I think that this would be a great feature for existing projects to run under .NET Aspire.

I’m working on a couple of services, lets say A and B. For development, I used to run them under IIS with modified entries in the etc/hosts file. In my current setup, Service A connects to Service B using the serviceb.dev.com URL, which is defined in the appsettings.json file.
Now, to use these services with .NET Aspire, I need to create a new appsettings.json file for the new setup. Ideally, I’d prefer to keep the existing appsettings.json file as is and use service names (including dots) in .NET Aspire, or have the ability to override the service discovery endpoints.

[davidfowl]

Why do you need to change anything to use aspire? Are you saying that you want to integrate with aspire’s service discovery or that you have to?

[paulomorgado]

@mateuszjarazny, I don't understand how this is forcing you to use another appsettings.json. Can you elaborate on that? Can you provide a sample solution?

[razvangoga]

@davidfowl encountered the same exception when trying to move and exiting project from a docker compose setup to Aspire vis-a-vis the SqlServer db name.

XX_SOMENAME_SOMEOTHERNAME is a valid DB name in SqlServer

Unhandled exception. System.ArgumentException: Resource name 'XX_SOMENAME_SOMEOTHERNAME' is invalid. Name must contain only ASCII letters, digits, and hyphens. (Parameter 'name')
   at Aspire.Hosting.ApplicationModel.ModelName.ValidateName(String target, String name) in /_/src/Aspire.Hosting/ApplicationModel/ModelName.cs:line 39
   at Aspire.Hosting.ApplicationModel.Resource..ctor(String name) in /_/src/Aspire.Hosting/ApplicationModel/Resource.cs:line 30
   at Aspire.Hosting.ApplicationModel.SqlServerDatabaseResource..ctor(String name, String databaseName, SqlServerServerResource parent) in /_/src/Aspire.Hosting/SqlServer/SqlServerDatabaseResource.cs:line 14
   at Aspire.Hosting.SqlServerBuilderExtensions.AddDatabase(IResourceBuilder`1 builder, String name, String databaseName) in /_/src/Aspire.Hosting/SqlServer/SqlServerBuilderExtensions.cs:line 71

[davidfowl]

There's an overload of AddDatabase that takes the database name and it shouldn't be getting this validation error:

var db = builder.AddSqlServer("sql").AddDatabase("db", "XX_SOMENAME_SOMEOTHERNAME");

[razvangoga]

works thanks - didn't notice the overload - i guess that here then the validation would be done on the 1st prm?

if yes - then maybe point the users to this overload in the exception message.

eg : Resource name 'XX_SOMENAME_SOMEOTHERNAME' is invalid. Name must contain only ASCII letters, digits, and hyphens. (Parameter 'name'). If you really really wanna use this name, use the .AddDatabase("db", "XX_SOMENAME_SOMEOTHERNAME") overload