Neo-VM migration checklist

[lock9]

Summary or problem description
The initiative to unify our repositories is underway, starting with the Neo-VM. We've encountered a range of unpredicted challenges during this process. This issue was created to facilitate the planning of the migration, since there are multiple tasks to be done, on different stages.

Do you have any solution you want to propose?
We need to break down the migration into smaller issues, so it can be discussed properly.

Step 1: Initial migration (files)

• Migrate the .csproj files and source files (NeoVM integration #2970 )
• Configure the VM project to reuse metadata information from the Directory.Build.props file (NeoVM integration #2970)
  • Update Directory.Build.props to use the TargetFrameworks property (Fix Neo VM target frameworks #2989)
• Update the build workflow to support the Neo-VM project (no changes required)

Step 2: Improvements

• Find an alternative to distribute Neo-VM test files #2971

Removed from scope:

• Migrate the Crypto package into a new standalone project (same repository) #2973

Neo Version

• Neo 3

Where in the software does this update applies to?

• VM

[cschuchardt88]

Update the build workflow to support the Neo-VM project

This maybe already done for us.

Uses solution file in repo

neo/.github/workflows/main.yml

Lines 91 to 93 in 61a0665

	run: |
	dotnet pack -o out -c Release
	dotnet nuget push out/*.nupkg -s https://api.nuget.org/v3/index.json -k ${NUGET_TOKEN}

neo/.github/workflows/main.yml

Line 32 in 61a0665

dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=lcov /p:CoverletOutput=${GITHUB_WORKSPACE}/coverage/lcov

[lock9]

This maybe already done for us.

Yes, I've double-checked and the tests are being run correctly.