Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add strong naming, public properties, and support for .NET 8 #56

Open
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

ilCosmico
Copy link

@ilCosmico ilCosmico commented Sep 25, 2024

This pull request includes the following updates:

  1. Strong Naming:

    • Added strong naming to the assembly to ensure it's signed and meets security requirements for strong-named assemblies.
  2. Public Properties:

    • Exposed the Diameter property in the DstvHole class, allowing access to the hole diameter.
    • Exposed the PointList and Type properties in the Contour class with improved immutability by returning IReadOnlyList<DstvContourPoint> for safer access to the points.
  3. .NET 8 Target:

    • Added .NET 8 as a target framework to ensure compatibility with the latest .NET version and to take advantage of its new features and improvements.

These changes aim to improve security, accessibility, and future compatibility with .NET 8. Please review the updates and merge if everything looks good. Thank you!

…r classes

- Added strong naming to ensure the assembly is signed.
- Exposed the 'Diameter' property in DstvHole.
- Exposed 'PointList' and 'Type' properties in Contour
Added .NET 8 as a target framework to support the latest .NET version.
@ilCosmico ilCosmico changed the title Add strong naming and public properties in DstvHole and Contour Add strong naming, public properties, and support for .NET 8 Sep 25, 2024
@ilCosmico
Copy link
Author

Hi, I was wondering if there are any updates regarding this pull request or any chance these changes might be merged soon? Thanks in advance!

@ilCosmico
Copy link
Author

@martijn00, any chance these changes might be merged? Thanks in advance!

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.

1 participant