-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Timeline on next release #859
Comments
Extra info, if I try
Could this be related to the fact that the projects I am compiling have dependent project assemblies? FYI, projects seem to compile OK and run fine from command line. Seems related to this: #781 |
Interesting. I haven't seen that but it's definitely not necessary to budget execution time for |
My problem(setup version: dotnet-hosting-3.1.6-win.exe): Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware|An unhandled exception has occurred while executing the request. System.InvalidOperationException: No design time or full build available. |
@pccai This looks like a separate problem. Would you mind opening a separate issue for it and including the results of Thanks. |
@ritchiecarroll Does it work for you without the project-to-project dependencies? For example, can you run |
C:\Users\Administrator>dotnet-try --version C:\Users\Administrator>dotnet --info 运行时环境: Host (useful for support): .NET Core SDKs installed: .NET Core runtimes installed: To install additional .NET Core runtimes or SDKs: tks. |
Other errors: {"message":"An unhandled exception occurred.","exception":"System.InvalidOperationException: No design time or full build available\r\n at WorkspaceServer.Packaging.Package.CreateRoslynWorkspace()\r\n at WorkspaceServer.Packaging.Package.ProcessFullBuildRequest(Budget budget)\r\n at WorkspaceServer.Packaging.Package.b__54_0(Budget budget)\r\n at WorkspaceServer.Servers.Roslyn.PackageExtensions.GetCompilation(IPackage package, IReadOnlyCollection |
@pccai You're using an older version that doesn't work with the latest SDKs. Can you run the following and try again? > dotnet tool uninstall -g dotnet-try
> dotnet tool install -g Microsoft.dotnet-try |
yes,that my way,but not running: D:\try>dotnet try --version D:\try>dotnet try demo {"message":"An unhandled exception occurred.","exception":"System.AggregateException: One or more errors occurred. (Unsupported log file format. Latest supported version is 7, the log file has version 9.)\r\n ---> System.NotSupportedException: Unsupported log file format. Latest supported version is 7, the log file has version 9.\r\n at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(Stream stream) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 53\r\n at Microsoft.Build.Logging.StructuredLogger.BinLogReader.Replay(String sourceFilePath) in C:\MSBuildStructuredLog\src\StructuredLogger\BinaryLogger\BinLogReader.cs:line 37\r\n at Buildalyzer.AnalyzerManager.Analyze(String binLogPath, IEnumerable |
It does not |
@pccai You might also try cleaning out out the build outputs. The |
@ritchiecarroll If you do a |
Just moments... 8 seconds? Ran test on a sample:
|
If useful, here's the full unhandled exception:
|
Here you go!!This works:
This does not:
Only difference is an underscore in main project file name??!! Doesn't like underscores I guess... |
FYI - more complex examples that reference other project-level assemblies still fail with:
However... These project assemblies also contain underscores in their names... If the issue is related. |
Wow, great find! Thanks for your persistence on this. I opened #869 to track this. |
Right now code built with C# 8.0 / .NET Core 3.1 always gives the following error for code I've tried (tried all versions and a manual compile from source):
FYI, I am in the process of developing a tool that will take Go code and convert it to C#: go2cs
dotnet-try
would be perfect for this by doing head-to-head comparisons of original Go code and converted C# code:The text was updated successfully, but these errors were encountered: