Skip to content

Update net45 to net462 - #233

Open
jon-armen wants to merge 2 commits into
aws:3.xfrom
jon-armen:net462
Open

Update net45 to net462#233
jon-armen wants to merge 2 commits into
aws:3.xfrom
jon-armen:net462

Conversation

@jon-armen

Copy link
Copy Markdown
Contributor

Description of changes:

  • Remove support for net45 (obsolete)
  • Add support for net462

Extracted work from #223 to reduce the amount of change in a single PR. Will update #223 for netcoreapp3.1 and net6.0 changes separately.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@jon-armen
jon-armen requested a review from a team as a code owner March 8, 2022 01:54
@jon-armen
jon-armen changed the base branch from master to 3.x March 18, 2022 11:08
@jon-armen

Copy link
Copy Markdown
Contributor Author

@srprash , I've updated this pr to go into the 3.x line if we want to move this work to that branch.

@srprash

srprash commented Mar 28, 2022

Copy link
Copy Markdown
Collaborator

Hi @jon-armen
Yes, we would like to trace the breaking changes in the 3.x branch. Thanks for doing this. :)

@jon-armen

Copy link
Copy Markdown
Contributor Author

@srprash , handled the merge issues. Once we start moving these pr's thru, I'll work towards updating to support dotnet6.

@jon-armen
jon-armen force-pushed the net462 branch 2 times, most recently from d124bfd to a29ffe7 Compare April 4, 2022 16:57
@jon-armen

Copy link
Copy Markdown
Contributor Author

@srprash - I've fixed the commits squashing this change to a single commit.

@jon-armen

Copy link
Copy Markdown
Contributor Author

This obsoletes #101

@jon-armen

Copy link
Copy Markdown
Contributor Author

@srprash - I've merged this down to a single commit. Are we in a position where we can merge into 3.x?

@jon-armen

jon-armen commented Jul 28, 2025

Copy link
Copy Markdown
Contributor Author

@srprash , in order to update to the latest aws sdk (#315), we'll need to drop 4.5 support. Can we start a aws-sdk 4.0 branch for several breaking changes?

[Edit] - Just getting my bearings back around here. I see we're still on version 2.x, and 3.x was tracking the breaking changes. Can we continue using 3.x to track breaking changes?

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.

2 participants