Miklós Pathy
Miklós Pathy
> Looks to be a duplicate of #218 There is a fix listed there too I tried. It causes 245 errors.
> So unless I'm overlooking something, it appears the exception was thrown when handling one of the other resources in your manifest. A project that reproduces this issue would help....
> Are you using Aspire 9.1? [@colinnuk] No. As far as i know it is 9.0.something. The default, comes with the latest Visual Studio.
@John-Leitch Thank you for the info. Fortunately it turned out I actually do not need to expose of the port manually, The Aspire somehow exposes it without the dockerfile. So,...
I downloaded the current master source for debugging, and it is working. I tried this with the latest nuget, so maybe a new release could solve this problem.
I have the same problem. It behaves totally differently on different devices, so it is impossible to fix it with a simple rotate.
Exactly the same problem with the latest official Microsoft Dotnet Docker image, and with the Docker Desktop terminal.
Hi, thank you for you answer. I played a little with the $TERM variable values. Default is `linux` in debian. In case of Putty, it is `xterm`. On the system...
Interesting. In Docker Desktop on Windows 10, the best solution is `Application.UseSystemConsole = true` The next best solutions are `xterm-16color` and `xterm-256color`. However these, results strange menu and window borders....