ILSpy

89 Tags

61 MiB

Tree: aad16c66e9

Author	SHA1	Message	Date
Christoph Wille	6f1c2b6cc9	.NET 11 for Tests (#3695 ) * .NET 11 RC2 minimal changes * Heuristic for transport feed Roslyn selection * Microsoft.CodeAnalysis.NetAnalyzers from main NuGet feed * Use the VS2026 image * Switch all test projects to net11 * Extract constants * Include vsix with plain nuget.config files	2 weeks ago
Siegfried Pammer	77d9ee73e9	Fix IDE2000 globally	4 months ago
Peter Crabtree	e1e16b64f5	dev: Strip BOM mark from text files	8 months ago
Siegfried Pammer	e4ebe20602	Upgrade dotnet target framework to net10	10 months ago
Siegfried Pammer	a94d66561a	Move to .NET 8.0 (#3119 ) * Basics of net8.0. Breaking unit tests expected. * Missed that TestRunner project was already upgraded to net7.0 (search and replace fail) * Use Preview 6 locally * Use .NET 8.0 RTM * Final fixups --------- Co-authored-by: Christoph Wille <christoph.wille@gmail.com>	2 years ago
Daniel Grunwald	8cc186d599	Use .NET 7.0 as target framework for the tests. This will be necessary for testing newer language features such as `ref` fields.	3 years ago
Siegfried Pammer	e24b901cd1	Build self-contained test runners before running tests.	4 years ago
Siegfried Pammer	e4b63f7a35	- Make all tests async. - Use custom test runner for correctness tests. - Use .NET 6.0 framework for all Roslyn compiler tests. - Disabled tests involving new string interpolation patterns.	4 years ago