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.

Sign up for GitHub

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

Jump to bottom

What ".net frameworks/versions" should be targeted? #7

Open
rskopecek opened this issue Jan 20, 2019 · 1 comment
Open

What ".net frameworks/versions" should be targeted? #7

rskopecek opened this issue Jan 20, 2019 · 1 comment
Assignees
@rskopecek
Labels
collaboration
Milestone
0.3.x

Comments

@rskopecek
Copy link
Owner

Currently the project is targeted at netstandard2.0. However, the mountain of tech debt that affects developers and their system users may range back to early versions of .Net. Version 3.5 seems like an obvious one to include.

What .net versions should be added on as a target so you can utilize in all your .net codebases.
@rskopecek rskopecek added this to the 0.3.x milestone Jan 20, 2019
@rskopecek rskopecek self-assigned this Jan 20, 2019
@rskopecek
Copy link
Owner Author

Well, "day one" trying to use the nuget on an old .net app ran into an issue. Netstandard 2 littered all sorts of stuff and basically disabled .Net, and thus the app. Just uninstalled to fix. So, added multi-targeting in to cover 3.5, 4.62, and 4.72 for now and dropped all the extras for netstandard 2 to prevent package littering. Not entirely sure if I did it right. Used the built in functionality, but ran into some issues. Shallow tested every .net version 3.5 - 4.72, so looked okay.

Short story: .Net projects 3.5+ should all work now.

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

@rskopecek rskopecek

Labels
collaboration
Projects
None yet
Milestone
0.3.x
Development

No branches or pull requests
1 participant
@rskopecek