You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 7x branch of OData is still leveraging the old C# project system to build .NET Framework projects. This process leads to numerous issues when releasing OData libraries, including compiled versions being out of sync with packaged versions.
This set of changes that will follow in a PR will update the process to build .NET Framework & .NET Core out of the same solution, and will require the CI/CD process to be upgraded as well.
When finished, OData 7x will match the structure of the Restier project, which has demonstrated the benefits of using this system for several releases now.
Questions to be answered:
Should we drop StyleCop (YES!!!)
Should we drop skipping strong names (YES!!!)
Should we drop the extra .targets files (YES!!!)
Should we be pointing to the MIT license instead of using our own license file? (YES!!!)
The text was updated successfully, but these errors were encountered:
Visual Studio 2022 has many if not most of StyleCop's features built into .editorConfig files. It does not need to be enforced in the build process as it is not currently directly improving release quality.
The 7x branch of OData is still leveraging the old C# project system to build .NET Framework projects. This process leads to numerous issues when releasing OData libraries, including compiled versions being out of sync with packaged versions.
This set of changes that will follow in a PR will update the process to build .NET Framework & .NET Core out of the same solution, and will require the CI/CD process to be upgraded as well.
When finished, OData 7x will match the structure of the Restier project, which has demonstrated the benefits of using this system for several releases now.
Questions to be answered:
The text was updated successfully, but these errors were encountered: