You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[WebToolsE2E][docs] When running the "Tutorial: Use .NET Aspire messaging integrations in ASP.NET Core" document using .NET CLI, there is an error.
#2034
Closed
v-reinawang opened this issue
Nov 11, 2024
· 1 comment
Issue description:
In "Tutorial: Use .NET Aspire messaging integrations in ASP.NET Core" doc, we need to make some updates to the instructions.
This issue only occurs when running the document using the .NET CLI development environment. There is no issue when using VS.
Issue:
Complete all the steps in the document using the .NET CLI development environment, the result obtained when Run and test the app locally is an error, which is different from the result described in the document.
Hosting failed to start
2024-11-11T09:15:01 System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read.
2024-11-11T09:15:01 at System.ConsolePal.ReadKey(Boolean intercept)
2024-11-11T09:15:01 at AspireSample.WorkerService.Worker.ExecuteAsync(CancellationToken stoppingToken) in C:\Users\v-reinawang\AspireSample\AspireSample.WorkerService\Worker.cs:line 31
2024-11-11T09:15:01 at Microsoft.Extensions.Hosting.Internal.Host.b__14_1(IHostedService service, CancellationToken token)
2024-11-11T09:15:01 at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List1 exceptions, Func`3 operation)
According to the error message, in Worker.cs file, Change "Console.ReadKey();" to "Console.Read();", but the expected result cannot be obtained. Display 'Stoped receiving messages' in console logs.
Expected:
After completing step 4 of the Run and test the app locally procedure, the corresponding information appears in the Console Log.
The text was updated successfully, but these errors were encountered:
v-reinawang
changed the title
[WebToolsE2E][Document] When running the "Tutorial: Use .NET Aspire messaging integrations in ASP.NET Core" document using .NET CLI, there is an error.
[WebToolsE2E][docs] When running the "Tutorial: Use .NET Aspire messaging integrations in ASP.NET Core" document using .NET CLI, there is an error.
Nov 12, 2024
Describe the issue or suggestion
Issue description:
In "Tutorial: Use .NET Aspire messaging integrations in ASP.NET Core" doc, we need to make some updates to the instructions.
This issue only occurs when running the document using the .NET CLI development environment. There is no issue when using VS.
Issue:
Complete all the steps in the document using the .NET CLI development environment, the result obtained when Run and test the app locally is an error, which is different from the result described in the document.
Hosting failed to start
2024-11-11T09:15:01 System.InvalidOperationException: Cannot read keys when either application does not have a console or when console input has been redirected. Try Console.Read.
2024-11-11T09:15:01 at System.ConsolePal.ReadKey(Boolean intercept)
2024-11-11T09:15:01 at AspireSample.WorkerService.Worker.ExecuteAsync(CancellationToken stoppingToken) in C:\Users\v-reinawang\AspireSample\AspireSample.WorkerService\Worker.cs:line 31
2024-11-11T09:15:01 at Microsoft.Extensions.Hosting.Internal.Host.b__14_1(IHostedService service, CancellationToken token)
2024-11-11T09:15:01 at Microsoft.Extensions.Hosting.Internal.Host.ForeachService[T](IEnumerable
1 services, CancellationToken token, Boolean concurrent, Boolean abortOnFirstException, List
1 exceptions, Func`3 operation)According to the error message, in Worker.cs file, Change "Console.ReadKey();" to "Console.Read();", but the expected result cannot be obtained. Display 'Stoped receiving messages' in console logs.
Expected:
After completing step 4 of the Run and test the app locally procedure, the corresponding information appears in the Console Log.
The text was updated successfully, but these errors were encountered: