dotnet try verify failed after updating VS2019 to v16.6

[yanxiaodi]

Describe the bug

After the build 2020 I update VS2019 to v16.6 then my dotnet try project cannot verify successfully.

Did this error occur while using dotnet try or online?

• [x] dotnet-try
• [ ] .NET Jupyter Notebook
• [ ] 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"
• [x] Other:

Screenshots

If applicable, add screenshots to help explain your problem.

Please complete the following:

• OS
  • [x] Windows 10
  • [ ] macOS
  • [ ] Linux (Please specify distro)
  • [ ] iOS
  • [ ] Android
• Browser
  • [x] Chrome
  • [x] Edge
  • [ ] Safari

The only change I remember is that I updated VS2019 to v16.6.

dotnet try version: 1.0.19553.4+001b36724d769e844a53b22e3833a23caed3dc68 dotnet version: 3.1.300 VS2019 version: 16.6.0

Steps:

• Use dotnet try to create a demo project.
• Run dotnet try verify.
• The below error shows:

Unhandled exception: System.AggregateException: One or more errors occurred. (Unsupported log file format. Latest supported version is 7, the log file has version 9.) ---> System.NotSupportedException: Unsupported log file format. Latest supported version is 7, the log file has version 9. at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(Stream stream) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 53 at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(String sourceFilePath) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 37 at Buildalyzer.AnalyzerManager.Analyze(String binLogPath, IEnumerable`1 buildLoggers) at WorkspaceServer.Packaging.Package.LoadDesignTimeBuildFromBuildLogFile(Package package, FileSystemInfo binLog) --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at System.Threading.Tasks.Task.Wait() at WorkspaceServer.Packaging.Package.TryLoadDesignTimeBuildFromBuildLog() at WorkspaceServer.Packaging.Package..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) at WorkspaceServer.Packaging.RebuildablePackage..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) at WorkspaceServer.Packaging.PackageBuilder.GetPackage(Budget budget) at WorkspaceServer.PackageRegistry.<>c__DisplayClass10_0.<<GetPackageFromPackageBuilder>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at WorkspaceServer.PackageRegistry.Get[T](String packageName, Budget budget) at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.CompileWorker(Workspace workspace, BufferId activeBufferId, Budget budget) at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.Compile(WorkspaceRequest request, Budget budget) at WorkspaceServer.Servers.WorkspaceServerMultiplexer.Compile(WorkspaceRequest request, Budget budget) at MLS.Agent.CommandLine.VerifyCommand.<>c__DisplayClass0_0.<<Do>g__ReportCompileResults|3>d.MoveNext() in F:\workspace_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 192 --- End of stack trace from previous location where exception was thrown --- at MLS.Agent.CommandLine.VerifyCommand.Do(VerifyOptions verifyOptions, IConsole console, StartupOptions startupOptions) in F:\workspace_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 87 at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context) at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context) at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at MLS.Agent.CommandLine.CommandLineParser.<>c__DisplayClass8_0.<<Create>b__7>d.MoveNext() in F:\workspace_work\1\s\MLS.Agent\CommandLine\CommandLineParser.cs:line 180 --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseErrorReporting>b__22_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass8_0.<<UseTypoCorrections>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseSuggestDirective>b__7_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseDirective>b__6_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseHelp>b__20_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass4_0.<<UseVersionOption>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<RegisterWithDotnetSuggest>b__23_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass5_0.<<UseExceptionHandler>b__0>d.MoveNext()

Sometimes the below error also occurs:

Unhandled exception: System.InvalidOperationException: No design time or full build available at WorkspaceServer.Packaging.Package.CreateRoslynWorkspace() at WorkspaceServer.Packaging.Package.ProcessFullBuildRequest(Budget budget) at WorkspaceServer.Packaging.Package.<SetupWorkspaceCreationFromBuildChannel>b__54_0(Budget budget) at WorkspaceServer.Servers.Roslyn.PackageExtensions.GetCompilation(IPackage package, IReadOnlyCollection1 sources, SourceCodeKind sourceCodeKind, IEnumerable1 defaultUsings, Func`1 workspaceFactory, Budget budget) at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.CompileWorker(Workspace workspace, BufferId activeBufferId, Budget budget) at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.Compile(WorkspaceRequest request, Budget budget) at WorkspaceServer.Servers.WorkspaceServerMultiplexer.Compile(WorkspaceRequest request, Budget budget) at MLS.Agent.CommandLine.VerifyCommand.<>c__DisplayClass0_0.<<Do>g__ReportCompileResults|3>d.MoveNext() in F:\workspace_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 192 --- End of stack trace from previous location where exception was thrown --- at MLS.Agent.CommandLine.VerifyCommand.Do(VerifyOptions verifyOptions, IConsole console, StartupOptions startupOptions) in F:\workspace_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 87 at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context) at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context) at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at MLS.Agent.CommandLine.CommandLineParser.<>c__DisplayClass8_0.<<Create>b__7>d.MoveNext() in F:\workspace_work\1\s\MLS.Agent\CommandLine\Co--- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseErrorReporting>b__22_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass8_0.<<UseTypoCorrections>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseSuggestDirective>b__7_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseDirective>b__6_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseHelp>b__20_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass4_0.<<UseVersionOption>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c.<<RegisterWithDotnetSuggest>b__23_0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.CommandLine.Invocation.InvocationExtensions.<>c__DisplayClass5_0.<<UseExceptionHandler>b__0>d.MoveNext()

[colombod]

3.1.300 introduces changes that breaks current version of dotnet-try. We are working on an upgrade to address this.

To get his working 3.1.101 should be used

[colombod]

We did also change package name to align it with other Microsoft products, are you using the package dotnet-try or Microsoft.dotnet-try?

[marikkan]

I also have the same problem after MS Visual Studio Update to v16.6.

I installed using the following command: dotnet tool install -g --add-source "https://dotnet.myget.org/F/dotnet-try/api/v3/index.json" Microsoft.dotnet-try

How can we install v3.1.101?

[JakubHolovsky]

Hello, I am also experiencing this issue on our project:

System.NotSupportedException: Unsupported log file format. Latest supported version is 7, the log file has version 9.

and I am wondering how to fix it with installing the older version. Well I am able to go to Visual Studio modify the installation but what happens is that when I uncheck 3.1.300 then it also uninstalls Xamarin, Web Development tools etc. once I tick them it checks 3.1.300 again. So I am kind of left out all broken. (since I need web development tools & xamarin)

Could you please suggest how to deal with this using the latest version of VS?

[colombod]

PR #841 contains work to address such issue. can you test installing the latest version following the instructions for the latest build from master.

Tool version 1.0.20305.1 is the release related to #841

[yanxiaodi]

Hi, @colombod thanks for your effort. It works now. My current version is v1.0.20305.1+a5177e5bf1d0589f520abe3a96eeed3b2c4b2c86

[colombod]

@yanxiaodi Thank you for using the tool and providing feedback!

[marikkan]

Mine works as well, but I need to run it with admin privileges. Thank you for your help.

On Sat, 6 Jun 2020, 10:13 Diego, [email protected] wrote:

@yanxiaodi https://github.com/yanxiaodi Thank you for using the tool and providing feedback!

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dotnet/try/issues/842#issuecomment-640000930, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADRUFLHRJ4ST4UFNOHXHTDRVHUCLANCNFSM4NIKWEBA .

[colombod]

Why with admin rights? What is the issue that you encounter ? Did you originally installed the tool as admin or normal user?

[marikkan]

I'm not sure, I might have installed it as an admin. That might be why I am encountering this. Anyway, it is resolved now, so no worries. Thanks for your interest.

On Sat, Jun 6, 2020 at 6:24 PM Diego [email protected] wrote:

Why with admin rights? What is the issue that you encounter ? Did you originally installed the tool as admin or normal user?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dotnet/try/issues/842#issuecomment-640077513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADRUFKQHWYVYNYRIO5SQNLRVJNTJANCNFSM4NIKWEBA .

[colombod]

I'm not sure, I might have installed it as an admin. That might be why I am encountering this. Anyway, it is resolved now, so no worries. Thanks for your interest.

On Sat, Jun 6, 2020 at 6:24 PM Diego [email protected] wrote:

Why with admin rights? What is the issue that you encounter ? Did you originally installed the tool as admin or normal user?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/dotnet/try/issues/842#issuecomment-640077513, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADRUFKQHWYVYNYRIO5SQNLRVJNTJANCNFSM4NIKWEBA .

This is wonderful, glad I was able to help you

[Barokai]

PR #841 contains work to address such issue. can you test installing the latest version following the instructions for the latest build from master.

Tool version 1.0.20305.1 is the release related to #841

works for me too now, just the given uninstall statement didn't work had to use dotnet tool uninstall -g dotnet-try instead of dotnet tool uninstall -g Microsoft.dotnet-try

[borsnoemi11]

I know this issue was closed but the exact same thing is still happening with the newest dotnet-try version. Could it be that I'm doing something wrong or with the recent versions this bug occurred again?

I have tried the following:

• The latest official dotnet-try version (1.0.20474.1)

• The abovementioned 1.0.20305.1 but I got the following message: warning NU1603: restore depends on Microsoft.dotnet-try (>= 1.0.20305.1) but Microsoft.dotnet-try 1.0.20305.1 was not found. An approximate best match of Microsoft.dotnet-try 1.0.20474.1 was resolved. You can invoke the tool using the following command: dotnet-try Tool 'microsoft.dotnet-try' (version '1.0.20474.1') was successfully installed.

• I currently have the 1.0.21110.1 preview version installed, but with the same result.

• I've thought about uninstalling the newer dotnet version to use the v3.1.101 what you mentioned above, but on one hand I'm not confident in this topic and I don't know what I could break, and on the other hand it also seems a little counterproductive to rollback to old versions just to be able to use dotnet try, so I'm not comfortable with it.

Does anyone have an idea what else I could try?

---

Here's a list of my software versions: dotnet try version: 1.0.21110.1+c2137652ada27a9795475eee75f8dbc8869f63b1 dotnet sdk: 5.0.301 VS2019 version: 16.10.3 runtimes: Microsoft.NETCore.App 2.1.28 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 3.1.16 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

[colombod]

@borsnoemi11 are you installing using this command

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

[colombod]

Still the issue about the binlog file will be there. We are looking into that

[borsnoemi11]

@borsnoemi11 are you installing using this command

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

Hey colombod, thank you very much for the quick reply. Yes, I used the install command you quoted.

[colombod]

Ok. We will need some more investigation and see how to address it. We are doing some work on the tool right now. Will keep you posted

On 17 Aug 2021, at 07:37, borsnoemi11 @.***> wrote:

 @borsnoemi11 are you installing using this command

dotnet tool install -g --add-source "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-tools/nuget/v3/index.json" Microsoft.dotnet-try Hey colombod, thank you very much for the quick reply. Yes, I used the install command you quoted.

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub, or unsubscribe.

[alexyakunin]

Any updates? Face the same issue, proposed fix doesn't help.

[grcd]

I am experiencing the same issue. Proposed fix does not help.

[colombod]

Hi, are you still having the issue with the log format error? What are the sdk installed?

[chandeepadissanayake]

Still experiencing the same issue. None of the fixes work.

[mertlab]

I'm having the same issue in Windows 11 both in Chrome and Edge browsers. I'm trying to use LINQ example in the doc: (https://docs.microsoft.com/en-us/samples/dotnet/try-samples/101-linq-samples/)

$ dotnet --version
5.0.402

$ dotnet try --version
1.0.21418.2+8296a9a59c5d81b85da47a62eb56369362d93fa2

$ dotnet try verify

D:\dotnet-try\LINQ\docs\lazy-evaluation.md
----------------------------------------------------------------------
  Checking Markdown...
    ✓  Line 7:  D:\dotnet-try\LINQ\src\Program.cs (in project D:\dotnet-try\LINQ\src\LINQ.csproj)
  Checking Markdown...
    ✓  Line 14: D:\dotnet-try\LINQ\src\Program.cs (in project D:\dotnet-try\LINQ\src\LINQ.csproj)

  Compiling samples for session "lazy-evaluation-basic"

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 Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(Stream stream) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 53
   at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(String sourceFilePath) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 37
   at Buildalyzer.AnalyzerManager.Analyze(String binLogPath, IEnumerable`1 buildLoggers)
   at WorkspaceServer.Packaging.Package.LoadDesignTimeBuildFromBuildLogFile(Package package, FileSystemInfo binLog) in D:\workspace\_work\1\s\WorkspaceServer\Packaging\Package.cs:line 138
   --- End of inner exception stack trace ---
   at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
   at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
   at System.Threading.Tasks.Task.Wait()
   at WorkspaceServer.Packaging.Package.TryLoadDesignTimeBuildFromBuildLog() in D:\workspace\_work\1\s\WorkspaceServer\Packaging\Package.cs:line 127
   at WorkspaceServer.Packaging.Package..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) in D:\workspace\_work\1\s\WorkspaceServer\Packaging\Package.cs:line 112
   at WorkspaceServer.Packaging.RebuildablePackage..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) in D:\workspace\_work\1\s\WorkspaceServer\Packaging\RebuildablePackage.cs:line 22
   at WorkspaceServer.Packaging.PackageBuilder.GetPackage(Budget budget) in D:\workspace\_work\1\s\WorkspaceServer\Packaging\PackageBuilder.cs:line 163
   at WorkspaceServer.PackageRegistry.<>c__DisplayClass10_0.<<GetPackageFromPackageBuilder>b__0>d.MoveNext() in D:\workspace\_work\1\s\WorkspaceServer\PackageRegistry.cs:line 139
--- End of stack trace from previous location where exception was thrown ---
   at WorkspaceServer.PackageRegistry.Get[T](String packageName, Budget budget) in D:\workspace\_work\1\s\WorkspaceServer\PackageRegistry.cs:line 92
   at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.CompileWorker(Workspace workspace, BufferId activeBufferId, Budget budget) in D:\workspace\_work\1\s\WorkspaceServer\Servers\Roslyn\RoslynWorkspaceServer.cs:line 412
   at WorkspaceServer.Servers.Roslyn.RoslynWorkspaceServer.Compile(WorkspaceRequest request, Budget budget) in D:\workspace\_work\1\s\WorkspaceServer\Servers\Roslyn\RoslynWorkspaceServer.cs:line 193
   at WorkspaceServer.Servers.WorkspaceServerMultiplexer.Compile(WorkspaceRequest request, Budget budget) in D:\workspace\_work\1\s\WorkspaceServer\Servers\WorkspaceServerMultiplexer.cs:line 26
   at MLS.Agent.CommandLine.VerifyCommand.Compile(Session session, MarkdownProcessingContext context) in D:\workspace\_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 193
   at MLS.Agent.CommandLine.VerifyCommand.Do(VerifyOptions verifyOptions, IConsole console, StartupOptions startupOptions, MarkdownProcessingContext context) in D:\workspace\_work\1\s\MLS.Agent\CommandLine\VerifyCommand.cs:line 84
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.ModelBindingCommandHandler.InvokeAsync(InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass4_0.<<BuildInvocationChain>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseErrorReporting>b__20_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at MLS.Agent.CommandLine.CommandLineParser.<>c__DisplayClass7_0.<<Create>b__2>d.MoveNext() in D:\workspace\_work\1\s\MLS.Agent\CommandLine\CommandLineParser.cs:line 165
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass15_0.<<UseHelp>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass24_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass22_0.<<UseTypoCorrections>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseSuggestDirective>b__21_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseParseDirective>b__19_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<UseDebugDirective>b__11_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c.<<RegisterWithDotnetSuggest>b__10_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass13_0.<<UseExceptionHandler>b__0>d.MoveNext()

[girodg]

any updates on this?

this fails for me on the demo project. I'm using VS 2022, .netcore 3.0, 'microsoft.dotnet-try' (version '1.0.21418.2')

[tonyatmendina]

I'm having a very similar issue, differing only by version numbers. Any code samples (e.g. the 101 LINQ samples) fail with an error:

Unsupported log file format. Latest supported version is 9, the log file has version 14.

My version information is:

dotnet --version
6.0.400

dotnet try --version
1.0.21418.2+8296a9a59c5d81b85da47a62eb56369362d93fa2

[pyrocumulus]

Same problem here, also with slightly different version numbers:

PS C:\Source\username> dotnet --version
7.0.202
PS C:\Source\username> dotnet try --version
1.0.21418.2+8296a9a59c5d81b85da47a62eb56369362d93fa2

Also tried the global.json approach to lower the version down to 3.1.426 SDK but it did not help. I have also re-installed the 3.0.103 SDK and tried that through global.json, still the same error:

Unsupported log file format. Latest supported version is 9, the log file has version 15.

[zebak007]

I spend one day now trying to get this work with 101-linq-samples, still faillling

PS C:\github\try-samples\101-linq-samples> dotnet --info .NET Core SDK (reflecting any global.json): Version: 3.1.426 Commit: e81f6c8565

Runtime Environment: OS Name: Windows OS Version: 10.0.22621 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\3.1.426\

Host: Version: 7.0.10 Architecture: x64 Commit: a6dbb800a4

.NET SDKs installed: 3.1.426 [C:\Program Files\dotnet\sdk] 6.0.413 [C:\Program Files\dotnet\sdk] 7.0.307 [C:\Program Files\dotnet\sdk] 7.0.400 [C:\Program Files\dotnet\sdk]

.NET runtimes installed: Microsoft.AspNetCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.AspNetCore.App 7.0.10 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.NETCore.App 7.0.10 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 3.1.32 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 6.0.21 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] Microsoft.WindowsDesktop.App 7.0.10 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found: x86 [C:\Program Files (x86)\dotnet] registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables: Not set

global.json file: C:\github\try-samples\101-linq-samples\global.json

Learn more: https://aka.ms/dotnet/info

Download .NET: https://aka.ms/dotnet/download

PS C:\github\try-samples\101-linq-samples> dotnet try verify Verifying...

C:\github\try-samples\101-linq-samples\index.md

C:\github\try-samples\101-linq-samples\readme.md

C:\github\try-samples\101-linq-samples\docs\aggregates-1.md

Checking Markdown... ✓ Line 9: C:\github\try-samples\101-linq-samples\src\AggregateOperators.cs (in project C:\github\try-samples\101-linq-samples\src\Try101LinqSamples.csproj)

Compiling samples for region "sum-syntax"

Unhandled exception: System.AggregateException: One or more errors occurred. (Unsupported log file format. Latest supported version is 9, the log file has version 16.) ---> System.NotSupportedException: Unsupported log file format. Latest supported version is 9, the log file has version 16. at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(Stream stream) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 53 at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(String sourceFilePath) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 37 at Buildalyzer.AnalyzerManager.Analyze(String binLogPath, IEnumerable`1 buildLoggers) at WorkspaceServer.Packaging.Package.LoadDesignTimeBuildFromBuildLogFile(Package package, FileSystemInfo binLog) in F:\workspace_work\1\s\WorkspaceServer\Packaging\Package.cs:line 138 --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at System.Threading.Tasks.Task.Wait() at WorkspaceServer.Packaging.Package.TryLoadDesignTimeBuildFromBuildLog() in F:\workspace_work\1\s\WorkspaceServer\Packaging\Package.cs:line 127 at WorkspaceServer.Packaging.Package..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) in F:\workspace_work\1\s\WorkspaceServer\Packaging\Package.cs:line 112 at WorkspaceServer.Packaging.RebuildablePackage..ctor(String name, IPackageInitializer initializer, DirectoryInfo directory, IScheduler buildThrottleScheduler) in F:\workspace_work\1\s\WorkspaceServer\Packaging\RebuildablePackage.cs:line 22 at WorkspaceServer.Packaging.PackageBuilder.GetPackage(Budget budget) in F:\workspace_work\1\s\WorkspaceServer\Packaging\PackageBuilder.cs:line 163 at WorkspaceServer.PackageRegistry.<>c__DisplayClass10_0.<<GetPackageFromPackageBuilder>b__0>d.MoveNext() in F:\workspace_work\1\s\WorkspaceServer\PackageRegistry.cs:line 139 --- End of stack trace from previous location where exception was thrown ---