Bug in dotnet try command ( red area when executing code ) #938

abdou31 · 2021-05-15T03:45:27Z

Describe the bug

I'm trying to execute dotnet try to try code samples of this repo but when I'm try run the code, I got this red area without any message.

What can I do in this case????

I really need help to fix this problem because I'm following a Linkedin course that use this tool .

dotnet --version
5.0.203

dotnet --list-sdks
2.1.524 [C:\Program Files\dotnet\sdk]
2.1.700-preview-009618 [C:\Program Files\dotnet\sdk]
3.1.200 [C:\Program Files\dotnet\sdk]
3.1.409 [C:\Program Files\dotnet\sdk]
5.0.203 [C:\Program Files\dotnet\sdk]

dotnet --info
SDK .NET (reflétant tous les fichiers global.json) :
Version: 5.0.203
Commit: 38xxxx
Environnement d'exécution :
OS Name: Windows
OS Version: 10.0
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\5.0.203\

Host (useful for support):
Version: 5.0.6
Commit: 478b2f8c0e

.NET SDKs installed:
2.1.524 [C:\Program Files\dotnet\sdk]
2.1.700-preview-009618 [C:\Program Files\dotnet\sdk]
3.1.200 [C:\Program Files\dotnet\sdk]
3.1.409 [C:\Program Files\dotnet\sdk]
5.0.203 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.All 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.24 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.24 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 3.1.2 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 3.1.15 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 5.0.6 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Did this error occur while using `dotnet try` or online?

dotnet-try
online

What kind of error was it?

User Interface (UI): For example the output never displayed
Service Error: For example "The service is temporarily unavailable. We are working on it"
Other:

Screenshots

Please complete the following:

OS
- Windows 10
- macOS
- Linux (Please specify distro)
- iOS
- Android
Browser
- Chrome
- Edge
- Safari

Update:
I saw that the problem come from Kaspersky Antivirus, so when I disable the antivirus, the error is gone.
But this is not a good solution , I would like to know how can I add an except for the localhost??

The text was updated successfully, but these errors were encountered:

Flash0ver · 2021-06-08T23:40:38Z

I have this issue now as well, where the network tab of my browser says:

{
"exception": "System.AggregateException: One or more errors occurred. (Unsupported log file format. Latest supported version is 9, the log file has version 13.)" ...,
"message": "An unhandled exception occurred."
}

Also, dotnet try verify fails to verify my project:

...
Unhandled exception: System.AggregateException: One or more errors occurred. (Unsupported log file format. Latest supported version is 9, the log file has version 13.)
 ---> System.NotSupportedException: Unsupported log file format. Latest supported version is 9, the log file has version 13.
   at ...

And, I have a déjà vu:
I believe I have experienced this error roughly a year ago with "latest supported version 7, but log file has version 9" or similar.

It seems that it worked fine with the .NET Core SDK 3.1.409, but then broke for me after installing the .NET Core SDK 3.1.410.
And now it does not work anymore since I have the Microsoft.NETCore.App 3.1.16 runtime installed on my machine.
It still works fine on a different machine, where I still have the Microsoft.NETCore.App 3.1.15 runtime installed.

Repo project: https://github.com/Flash0ver/F0-Talks-MutationTesting/tree/main/presentation

jonsequitur · 2021-06-08T23:55:28Z

Yup, this looks like it's due to a change in the log format for MSBuild. We'll look into whether we can support multiple versions and/or roll forward to .NET 5.

mezJihad · 2021-10-05T13:38:11Z

I have same probleme, if any one can help please

ssedlak · 2022-01-19T14:02:10Z

I can't tell if I am missing something or something is wrong that I can't fix. Uncaught (in promise) Error

MaartenGDev · 2022-01-27T20:18:59Z

global.json can be used to fix the log version error.

I used the following steps to fix the "Unsupported log format error":

Install preview version of dotnet try (source: https://github.com/dotnet/try/blob/main/DotNetTryLocal.md)

dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-try

Clone sample repo

git clone https://github.com/dotnet/try-samples.git
cd try-samples

Create global.json inside the try-samples folder

touch global.json

Place the following contents in global.json in the try-samples folder. Use the latest .NET 3.1 that you have installed (dotnet --list-sdks)

{
  "sdk": {
    "version": "3.1.416"
  }
}

Run dotnet try in the try-samples folder:

dotnet try

The internal server errors should be fixed. Run dotnet try verify if any other error occurs.

ssedlak · 2022-01-30T05:08:19Z

@MaartenGDev
I did everything except I was not able to clone the repo. I tried to just add the json into my existing directory, but still a red box.

MaartenGDev · 2022-01-30T13:17:01Z

@ssedlak2278 This error happens if you do not have a SSH key configured in your GitHub profile. You can try cloning using:

git clone https://github.com/dotnet/try-samples.git

You need to follow the steps in #938 (comment) again after cloning the repository.

ssedlak · 2022-01-30T14:11:30Z

@MaartenGDev It worked! Thank you.
I did have to restart my brower before it worked, probably because I've had it open a week.

Hultner · 2022-02-09T10:20:20Z

global.json can be used to fix the log version error.

I used the following steps to fix the "Unsupported log format error":

Install preview version of dotnet try (source: https://github.com/dotnet/try/blob/main/DotNetTryLocal.md)
dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-try
Clone sample repo
git clone https://github.com/dotnet/try-samples.git
cd try-samples
Create global.json inside the try-samples folder
touch global.json
Place the following contents in global.json in the try-samples folder. Use the latest .NET 3.1 that you have installed (dotnet --list-sdks)
{
  "sdk": {
    "version": "3.1.416"
  }
}
Run dotnet try in the try-samples folder:
dotnet try
The internal server errors should be fixed. Run dotnet try verify if any other error occurs.

Doesn't help for me, tried in multiple browsers as well. Verify outputs a bunch of errors for me as well.

It would be neat if there were a docker-image with a known working configuration so one could pull and run that image and just run the samples without worrying about problems in local environments.

I run MacOS and have tried in Chrome as well as Safari.

MaartenGDev · 2022-02-09T11:59:42Z

@Hultner which version of .NET 3.1 do you have installed? Can be checked using dotnet --list-sdks?

Hultner · 2022-02-09T12:26:21Z

@Hultner which version of .NET 3.1 do you have installed? Can be checked using dotnet --list-sdks?

$ dotnet --list-sdks
2.2.105 [/usr/local/share/dotnet/sdk]
2.2.204 [/usr/local/share/dotnet/sdk]
3.0.100 [/usr/local/share/dotnet/sdk]
3.1.416 [/usr/local/share/dotnet/sdk]
6.0.101 [/usr/local/share/dotnet/sdk]

Looks like 3.1.416, which I also added to the global.json file according to your instructions.

cherepo · 2022-03-08T23:45:22Z

Same error on a Mac (not M1)

2.2.207 [/usr/local/share/dotnet/sdk]
3.1.413 [/usr/local/share/dotnet/sdk]
3.1.416 [/usr/local/share/dotnet/sdk]
5.0.202 [/usr/local/share/dotnet/sdk]
5.0.401 [/usr/local/share/dotnet/sdk]
5.0.405 [/usr/local/share/dotnet/sdk]
6.0.200 [/usr/local/share/dotnet/sdk]

jeremy7710 · 2022-03-21T05:20:33Z

global.json can be used to fix the log version error.

I used the following steps to fix the "Unsupported log format error":

Install preview version of dotnet try (source: https://github.com/dotnet/try/blob/main/DotNetTryLocal.md)
dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-try
Clone sample repo
git clone https://github.com/dotnet/try-samples.git
cd try-samples
Create global.json inside the try-samples folder
touch global.json
Place the following contents in global.json in the try-samples folder. Use the latest .NET 3.1 that you have installed (dotnet --list-sdks)
{
  "sdk": {
    "version": "3.1.416"
  }
}
Run dotnet try in the try-samples folder:
dotnet try
The internal server errors should be fixed. Run dotnet try verify if any other error occurs.

This works for me, Thanks.
I'm on a win10.

vasveone · 2022-04-16T05:17:51Z

Just added the global.json as advised from @MaartenGDev in my project folder and works fine!

{
  "sdk": {
    "version": "3.1.416"
  }
}

yimaiyan · 2022-05-26T02:13:45Z

same error in macOS(not M1), as advised from @MaartenGDev in my project folder but failed to fix this issue.
Can anyone help? Thanks!

thanh-tran-tien · 2022-08-03T09:00:22Z

global.json can be used to fix the log version error.

I used the following steps to fix the "Unsupported log format error":

Install preview version of dotnet try (source: https://github.com/dotnet/try/blob/main/DotNetTryLocal.md)
dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-try
Clone sample repo
git clone https://github.com/dotnet/try-samples.git
cd try-samples
Create global.json inside the try-samples folder
touch global.json
Place the following contents in global.json in the try-samples folder. Use the latest .NET 3.1 that you have installed (dotnet --list-sdks)
{
  "sdk": {
    "version": "3.1.416"
  }
}
Run dotnet try in the try-samples folder:
dotnet try
The internal server errors should be fixed. Run dotnet try verify if any other error occurs.

BIG LOVE! BRO

cheema-corellian · 2023-10-17T03:17:03Z

I followed the instructions in this comment

At first it did not fix my problem. dotnet try verify did not run successfully. The browser still showed red. I then restarted my browser, and the red box in the browser went away. Success!

Here is what my global.json looks like:

{
  "sdk": {
    "version": "7.0.402"
  }
}

For me, it is OK to ignore the dotnet try verify errors, for now.

Godaday · 2024-07-26T07:08:36Z

This is the process I followed to resolve the error, for your reference.

mkdir mydoc

cd mydoc

dotnet new console -n myApp -f netcoreapp3.1

cd myApp

create a new file "global.json"

{
  "sdk": {
    "version": "3.1.416"
  }
}

in file version node content look your local sdk list

dotnet --list-sdks

 cd mydoc

create file doc.md

# My Interactive Document:

```cs --source-file ./myApp/Program.cs --project ./myApp/myApp.csproj
```

dotnet try verify
dotnet try

it's worked

jonsequitur added the bug label May 16, 2021

colombod mentioned this issue Aug 16, 2021

FileFormat Version not supported phmonte/Buildalyzer#184

Closed

atifaziz mentioned this issue Nov 24, 2021

Missing example for Generate morelinq/examples#33

Open

MaartenGDev mentioned this issue Jan 27, 2022

Error while executing code - Internal Server Error #971

Open

ConnerPhillis mentioned this issue Aug 17, 2023

Internal Server Error #980

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bug in dotnet try command ( red area when executing code ) #938

Bug in dotnet try command ( red area when executing code ) #938

abdou31 commented May 15, 2021 •

edited

Loading

Flash0ver commented Jun 8, 2021 •

edited

Loading

jonsequitur commented Jun 8, 2021

mezJihad commented Oct 5, 2021

ssedlak commented Jan 19, 2022

MaartenGDev commented Jan 27, 2022 •

edited

Loading

ssedlak commented Jan 30, 2022 •

edited

Loading

MaartenGDev commented Jan 30, 2022 •

edited

Loading

ssedlak commented Jan 30, 2022

Hultner commented Feb 9, 2022 •

edited

Loading

MaartenGDev commented Feb 9, 2022

Hultner commented Feb 9, 2022 •

edited

Loading

cherepo commented Mar 8, 2022

jeremy7710 commented Mar 21, 2022 •

edited

Loading

vasveone commented Apr 16, 2022

yimaiyan commented May 26, 2022

thanh-tran-tien commented Aug 3, 2022

cheema-corellian commented Oct 17, 2023 •

edited

Loading

Godaday commented Jul 26, 2024 •

edited

Loading

Bug in dotnet try command ( red area when executing code ) #938

Bug in dotnet try command ( red area when executing code ) #938

Comments

abdou31 commented May 15, 2021 • edited Loading

Describe the bug

Did this error occur while using dotnet try or online?

What kind of error was it?

Screenshots

Please complete the following:

Flash0ver commented Jun 8, 2021 • edited Loading

jonsequitur commented Jun 8, 2021

mezJihad commented Oct 5, 2021

ssedlak commented Jan 19, 2022

MaartenGDev commented Jan 27, 2022 • edited Loading

ssedlak commented Jan 30, 2022 • edited Loading

MaartenGDev commented Jan 30, 2022 • edited Loading

ssedlak commented Jan 30, 2022

Hultner commented Feb 9, 2022 • edited Loading

MaartenGDev commented Feb 9, 2022

Hultner commented Feb 9, 2022 • edited Loading

cherepo commented Mar 8, 2022

jeremy7710 commented Mar 21, 2022 • edited Loading

vasveone commented Apr 16, 2022

yimaiyan commented May 26, 2022

thanh-tran-tien commented Aug 3, 2022

cheema-corellian commented Oct 17, 2023 • edited Loading

Godaday commented Jul 26, 2024 • edited Loading

abdou31 commented May 15, 2021 •

edited

Loading

Did this error occur while using `dotnet try` or online?

Flash0ver commented Jun 8, 2021 •

edited

Loading

MaartenGDev commented Jan 27, 2022 •

edited

Loading

ssedlak commented Jan 30, 2022 •

edited

Loading

MaartenGDev commented Jan 30, 2022 •

edited

Loading

Hultner commented Feb 9, 2022 •

edited

Loading

Hultner commented Feb 9, 2022 •

edited

Loading

jeremy7710 commented Mar 21, 2022 •

edited

Loading

cheema-corellian commented Oct 17, 2023 •

edited

Loading

Godaday commented Jul 26, 2024 •

edited

Loading