diff options
Diffstat (limited to 'src/ILVerify/README.md')
| -rw-r--r-- | src/ILVerify/README.md | 14 |
1 files changed, 1 insertions, 13 deletions
diff --git a/src/ILVerify/README.md b/src/ILVerify/README.md index ef4d0d81f..286c70d50 100644 --- a/src/ILVerify/README.md +++ b/src/ILVerify/README.md @@ -17,7 +17,7 @@ Historically on Full Framework IL generators used PEVerify to make sure that the - Fast spin up/tear down. ## The codebase -The project targets netcoreapp2.0 and uses the new .csproj based project format. If you want to open and compile it with Visual Studio then you need a version, which supports .NET Core 2.0 tooling. This is supported in Visual Studio 2017 Update 3 (Version 15.3) or later. The other option is to use command (with .NET Core 2.0 tooling). +The project targets netcoreapp2.1 and uses the new .csproj based project format. If you want to open and compile it with Visual Studio then you need a version, which supports .NET Core 2.1 tooling. This is supported in Visual Studio 2017 Version 15.8 or later. The other option is to use command (with .NET Core 2.1 tooling). The code is split into three projects: - ILVerification is the library with the core verification logic, - ILVerification.Tests contains the tests for ILVerification, @@ -27,18 +27,6 @@ The code is split into three projects: To test the ILVerification library we have small methods checked in as .il files testing specific verification scenarios. These tests live under [src/ILVerification/tests/ILTests](../ILVerification/tests/ILTests). Tests are grouped into .il files based on functionalities they test. There is no strict policy here, the goal is to have a few dozen .il files instead of thousands containing each only a single method. -Currently the IL files are NOT compiled automatically. You have to compile manually (We want to automate this step later): - -``` -ilasm [filename.il] /dll /ERROR -``` - -Note: if you run the tests and get an error similar to this then it means that the .il files were not compiled, or none of them contained methods that follow the naming convention described below: - -``` -Result Message: System.InvalidOperationException : No data found for ILVerify.Tests.ILMethodTester.TestMethodsWithInvalidIL -``` - The test project itself is under [src/ILVerification/tests](../ILVerification/tests) Method names in the .il files must follow the following naming convention: |