Skip to content

chore: move AntlrGrammars project to .NET Standard, sdk-style#1105

Open
tlecomte wants to merge 4 commits into
TabularEditor:masterfrom
tlecomte:AntlrGrammarsNetStandard
Open

chore: move AntlrGrammars project to .NET Standard, sdk-style#1105
tlecomte wants to merge 4 commits into
TabularEditor:masterfrom
tlecomte:AntlrGrammarsNetStandard

Conversation

@tlecomte
Copy link
Copy Markdown

@tlecomte tlecomte commented May 8, 2023

This moves the AntlrGrammars project to .NET Standard, together with migrating the project file to the newer "sdk-style" format.

The benefits are:

  • .NET Standard means that the dlls built for this project are cross-platform and are both compatible with .NET Framework 4.8, and with .NET Core.
  • the "sdk-style" format is simpler, as source files are automatically included based on their path. Also, several assembly properties are directly defined in the project file instead of requiring a separate AssemblyInfo.cs file.

Tested by building locally on a fresh repo and starting TabularEditor.

tlecomte-jw and others added 4 commits April 30, 2023 13:39
For a couple of years .NET projects can use `PackageReference` instead of `packages.config` to list dependencies.

This has several immediate benefits. The main advantage is that it simplifies the project files and removes redundancy, since packages only have to be listed in one place, and transitive dependencies no longer need to be listed.

Reference: https://learn.microsoft.com/en-us/nuget/consume-packages/migrate-packages-config-to-package-reference

This is also a step towards migrating the project files to the newer "sdk-style" format.
chore: move from packages.config to PackageReference
This moves the `AntlrGrammars` project to .NET Standard, together with migrating the project file to the newer "sdk-style" format.

The benefits are:
- .NET Standard means that the dlls built for this project are cross-platform and are both compatible with .NET Framework 4.8, and with .NET Core.
- the "sdk-style" format is simpler, as source files are automatically included based on their path. Also, several assembly properties are directly defined in the project file instead of requiring a separate AssemblyInfo.cs file.

Tested by building locally on a fresh repo and starting TabularEditor.
@tlecomte
Copy link
Copy Markdown
Author

tlecomte commented May 8, 2023

Dear @otykier here is another small contribution.

If you like it, I'm happy with continuing such migrations progressively for the other projects.

@otykier
Copy link
Copy Markdown
Collaborator

otykier commented May 8, 2023

Hi @tlecomte - thanks a lot for this contribution.
Unfortunately, I've had to revert the last PR you submitted (migration to PackageReference), because that project format does not work well with our installer/setup project. So at least for now, I'll leave this open.

@tlecomte
Copy link
Copy Markdown
Author

tlecomte commented May 9, 2023

Oh sorry about that @otykier. I'll try to find some time to look at the installer project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants