I know Microsoft.Extensions.* and System.Diagnostics.* version 9 can be used on .NET 8.0, but there's a supportability issue you are imposing on users that you can't do.
.NET 8.0 didn't change t...
### Package
OpenTelemetry
### Package Version
Versions 1.10.0 and those that take dependencies on it.
### Runtime Version
net8.0, netstandard2.1, netstandard2.0, net462
### Description
.NE...
> Well I it’s be great if you can provide me with a repro so I can try it before you get it to see if it’s indeed fixed
Sure.
I've created an Aspire starter project and added Docker support to th...
### Title
Jen Gentleman
### Bluesky profile url
https://bsky.app/profile/jenmsft.bsky.social
### Twitter profile (url or username)
https://x.com/JenMsft
### Category
windows
### Type
micro...
### Title
David Fowler
### Bluesky profile url
https://bsky.app/profile/davidfowl.com
### Twitter profile (url or username)
https://x.com/davidfowl
### Category
dotnet
### Type
microsoft
> Can you make a repro? I am testing with a later Aspire 9.0 build and podman and everything works just fine.
I can wait a few days for the release and get back at this.
The same app host can receive telemetry from a container running an ASP.NET Core 8 application when using **Docker Rancher** (with persistent containers), but is not able to receive telemetry from ...
> This (I think) causes other types of issues, like "WithPgAdmin()" doesn't seem to work anymore (nor does the "WithPgWeb()". Will be good to see if this can get resolved.
Works with DbGate 5.3.1
I ended up adding this before building and running the app host:
```csharp
// Aspire 9.0.0/Rancher bug
{
if (await IsRancherDesktopAsync())
{
foreach (var resource in builder.Resou...
@baronfel,
Trying to debug this, I found out that `my.repository.name` is not normalized, but `My.Repository.Name` is normalized into `my-repository-name`.
| `containerRepository` | `normalizedIm...
@baronfel,
`my,registry.com:123/my-repository` is considered valid and not normalized.
However, `my,registry.com:123/my.repository` is normalized to `my-registry-com-123/my-repository`.
I don't ...
> > `init` only fields do not guarantee that.
> > You can use a `struct`. That will always be copied, thus, not a good idea if they are big.
> > One strategy I use some times is using a context t...
`init` only fields do not guarantee that.
You can use a `struct`. That will always be copied, thus, not a good idea if they are big.
One strategy I use some times is using a context type (think `...
`ImagePushParameters.RegistryAuth` seems to be an unused property.
`Docker.DotNet.ImageOperations.PushImageAsync` makes no use of it and uses a `AuthConfig` parameter instead.
Is this intended?
Maybe a `ContainerFullyQualifiedImageName` property would work.
If supplied, it would ignore `ContainerRegistry` and `ContainerRepository` and use it instead.
1. Use .NET SDK to produce an archive of the container image.
2. Load the container image: `docker load --input <path to the image archive file>`
3. Push the desired image tags to the registry: `do...
I'm specifying my container repository as:
```xml
<ContainerRepository>myregistry.com:123/$(AssemblyName)</ContainerRepository>
```
But the `ParseContainerProperties` task "normalizes" it to "myr...
> > Is the plan to take [#6381](https://github.com/dotnet/aspire/pull/6381) for 9.0 GA? I'd think we should right?
>
> Yes, that was my plan. So people don't use the Aspire library with the 3.0.0 ...