Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Codegen fails for ValueTask<T> with Build but not MSBuild #5300
When trying to build a project containing a grain interface whose method returns a
This behavior happens whether the project targets .NET Core 2.2 or .NET Standard 2.0. (one of the lines changes to
This behavior does not happen if
Repository below reproduces these results with both
Documentation and release notes (as far as I have seen?) does not appear to suggest that the code generation package should determine whether
In the repro I linked above, there are 4 projects and compilation statuses are as below:
So the issue appears to be independent of target and is isolated to
While on this topic, I do have two questions:
If the plan is to retire, maybe "won't fix" is the appropriate action since
Yes, we plan to retire it at some point. The fundamental problem with it is that is uses Reflection for loading application type information, and that is very sensitive to assembly versioning, etc.
It generates more type identity 'noise' because it does not load dependencies. That has no impact on performance, just longer generated code file.