v-elenafeng

Results 19 comments of v-elenafeng

Upgrade the SDK after creating and running projects, the SDK was installed SxS not upgraded.

> Can you check if this repros when upgrading from October to November builds? Reproduced!

[WebToolsE2E][Aspire] With SDK 8.0.300 + Aspire 8.0 GA, dotnet new aspire-starter does not work due to manifest provider returned a duplicate manifest ID 'microsoft.net.sdk.android'.

This issue can also be reproduced with a clean install of VS 17.10 GA (with Aspire 8.0 GA)+ Web workload when creating a new template using the CLI, but works...

[WebToolsE2E][Aspire] With SDK 8.0.300 + Aspire 8.0 GA, dotnet new aspire-starter does not work due to manifest provider returned a duplicate manifest ID 'microsoft.net.sdk.android'.

I installed a new machine today and can still reproduce this issue, it happens randomly and the failure rate is about 50%. ![image](https://github.com/dotnet/aspire/assets/78580199/9249ef68-b5d2-4bb8-a547-b2eee88d5288)

[WebToolsE2E][Aspire] With SDK 8.0.300 + Aspire 8.0 GA, dotnet new aspire-starter does not work due to manifest provider returned a duplicate manifest ID 'microsoft.net.sdk.android'.

Close this issue as it was fixed both on Aspire 8.0.1 and 8.1 Preview 1.

Can't publish Aspire Project using Visual Studio because of failure to parse Danish time format

Checked again using the VS 17.10.4 FB, the scenario is working fine.

[WebToolsE2E][Aspire] Creating web app with MS Identity auth and aspire checked, F5 failed with 'This service descriptor is keyed. Your service provider may not support keyed services.'

> Try updating the identity packages. This is a bug that has been fixed. Thanks, after updating the identity packages I was able to run successfully. Just wondering when the...

[WebToolsE2E][Aspire] Creating web app with MS Identity auth and aspire checked, F5 failed with 'This service descriptor is keyed. Your service provider may not support keyed services.'

I'm able to repro this issue with the released VS 17.10.0. @deepchoudhery ping you again on the packages update for msi to resolve this issue. ![image](https://github.com/dotnet/aspire/assets/78580199/a266438e-9d43-4650-b741-7a86412924ad)

[WebToolsE2E][Aspire] Updated Aspire version from 8.0.0 to 8.0.1. When running the project, an exception occurred: System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.Extensions.ServiceDiscovery, Version=8.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.'

@joperezr @vijayrkn FYI on this issue that was reported for updating solution from 8.0.0 to 8.0.1.

[WebToolsE2E][Aspire] Updated Aspire version from 8.0.0 to 8.0.1. When running the project, an exception occurred: System.IO.FileNotFoundException: 'Could not load file or assembly 'Microsoft.Extensions.ServiceDiscovery, Version=8.0.1.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.'

> @BillHiebert @vijayrkn #4310 is a similar issue where the user needs to do a full clean and rebuild after updating their packages from Aspire 8.0.1 to Aspire 8.1. #4310...

[WebToolsE2E][Aspire] For a Function App with Aspire 9.2, the port number in console logs is always 7071 and does not match the port number in the dashboard

> We might be able to narrow this down by testing with different VS versions but I am not sure what versions we have access to. @captainsafia I have the...