Add a build file using dotnet 10 preview

Oct 13, 2025 by pinkandtrash.com 141 views

Introduction

In this article, we will explore a peculiar issue that arises when building a .NET project with specific SDK versions, resulting in a MissingMethodException. This exception occurs when testing against a couple of .NET versions, but only on the build pipeline (Ubuntu 22.04) and not when building/testing locally (Windows 11). We will delve into the root cause of this issue, provide reproduction steps, and discuss known workarounds.

Description

The problem arises when including .NET 10 in a project that tests against multiple .NET versions. The exception occurs when a method under test is missing, resulting in a MissingMethodException. However, this issue only occurs on the build pipeline (Ubuntu 22.04) and not when building/testing locally (Windows 11).

Reproduction Steps

To reproduce this issue, follow these steps:

Create a class library with .NET Standard 2.0: Create a new class library project using the .NET Standard 2.0 framework.
Include System.Text.Json: Include the System.Text.Json package in the class library project.
Create an MSTest project with .NET Framework 4.7: Create a new MSTest project using the .NET Framework 4.7.
Set Microsoft.NET.Test.Sdk to 17.13.0: Set the Microsoft.NET.Test.Sdk package to version 17.13.0.
Set MSTest package to version 3.8.2: Set the MSTest package to version 3.8.2.
Add a build file using dotnet 10 preview: Add a build file using the dotnet 10 preview to build the project on Ubuntu 22.04.

Expected Behavior

The expected behavior is that the test should pass.

Actual Behavior

The actual behavior is that a MissingMethodException is thrown.

Regression

This issue does not occur when building and testing using dotnet 9.0, but it does occur when using dotnet 10.0.

Known Workarounds

There are a few known workarounds for this issue:

Use old-school value tuples: Use the System.ValueTuple package instead of the newer value tuple syntax.
Use other versions of dotnet 10 or MSTest framework: Try using different versions of dotnet 10 or the MSTest framework to see if the issue is resolved.

Configuration

The configuration for the library project is as follows:

.NET Standard 2.0: The library project is built using the .NET Standard 2.0 framework.
System.Text.Json: The System.Text.Json package is included in the library project.
Test project: The test project is built using the .NET Framework 4.7.
Microsoft.NET.Test.Sdk: The Microsoft.NET.Test.Sdk package is set to version 17.13.0.
MSTest: The MSTest package is set to version 3.8.2.

Other Information

Unfortunately, there has been no response to this issue, and it remains unresolved.

Conclusion

In conclusion, this article has explored a peculiar issue that arises when building a .NET project with specific SDK versions, resulting in a MissingMethodException. We have provided reproduction steps, discussed known workarounds, and highlighted the configuration for the library project. We hope that this article will help others who may be experiencing similar issues and provide a solution to this problem.

Additional Resources

For more information on this issue, please refer to the following resources:

Future Work

Introduction

In our previous article, we explored a peculiar issue that arises when building a .NET project with specific SDK versions, resulting in a MissingMethodException. In this Q&A article, we will answer some of the most frequently asked questions about this issue.

Q: What is the root cause of this issue?

A: The root cause of this issue is not yet fully understood, but it appears to be related to the interaction between the .NET Standard 2.0 framework, the System.Text.Json package, and the Microsoft.NET.Test.Sdk package.

Q: Why does this issue only occur on the build pipeline (Ubuntu 22.04) and not when building/testing locally (Windows 11)?

A: This issue only occurs on the build pipeline (Ubuntu 22.04) because of the differences in the .NET runtime and the test framework between the two environments. The build pipeline uses a different version of the .NET runtime and the test framework, which causes the issue.

Q: What are the known workarounds for this issue?

A: There are two known workarounds for this issue:

Use old-school value tuples: Use the System.ValueTuple package instead of the newer value tuple syntax.
Use other versions of dotnet 10 or MSTest framework: Try using different versions of dotnet 10 or the MSTest framework to see if the issue is resolved.

Q: Can I use the .NET 5 or .NET 6 frameworks instead of .NET Standard 2.0?

A: Yes, you can use the .NET 5 or .NET 6 frameworks instead of .NET Standard 2.0. However, this may require changes to your project configuration and may not resolve the issue.

Q: Is this issue specific to the System.Text.Json package?

A: No, this issue is not specific to the System.Text.Json package. However, the System.Text.Json package is one of the packages that is affected by this issue.

Q: Can I use the MSTest framework with .NET Core?

A: Yes, you can use the MSTest framework with .NET Core. However, you may need to use a different version of the MSTest framework that is compatible with .NET Core.

Q: What is the current status of this issue?

A: The current status of this issue is that it is still unresolved. Microsoft is investigating this issue and working on a solution.

Q: Where can I find more information about this issue?

A: You can find more information about this issue on the following resources:

Conclusion

In conclusion, this Q&A article has provided answers to some of the most frequently asked questions about the invalid .NET 10 MissingMethodException with specific SDK versions issue. We hope that this article has been helpful in providing more information about this issue and its workarounds.

Additional Resources

For more information on this issue, please refer to the following resources:

Future Work

We plan to continue investigating this issue and provide updates on any progress made. If you have any information or suggestions on how to resolve this issue, please feel free to share them with us.