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

Can't update to Dapper-2.0.4 with Visual Studio 2015 #1325

Closed
nhathongly opened this issue Sep 9, 2019 · 3 comments
Closed

Can't update to Dapper-2.0.4 with Visual Studio 2015 #1325

nhathongly opened this issue Sep 9, 2019 · 3 comments

Comments

@nhathongly
Copy link

@nhathongly nhathongly commented Sep 9, 2019

We are stuck with Visual Studio 2015 due to the license. Dapper-2.0.4 only targets to .net standard 2.0, so that we can't update it in our projects. Could you please support it to run on .Net Framework 4.6.1?

@mgravell
Copy link
Contributor

@mgravell mgravell commented Sep 9, 2019

Well, the good news is that the old version will continue to work. It isn't realistic to promise eternal support on old platforms, but let me.have some conversations here about minimum versions. Net461 is pretty much the minimum I'd be willing to look at.

I'm morbidly curious, though - but maybe it is an irrelevant tangent - I'm not aware of any major license changes between VS2015 and later. I doubt it is key here, but if you have more details on that I'm curious :)

@mgravell mgravell closed this in aefb284 Sep 12, 2019
@mgravell
Copy link
Contributor

@mgravell mgravell commented Sep 12, 2019

I've reinstated the net461 TFM; whether that works in VS2015 is another question...

@nhathongly
Copy link
Author

@nhathongly nhathongly commented Sep 25, 2019

Well, the good news is that the old version will continue to work. It isn't realistic to promise eternal support on old platforms, but let me.have some conversations here about minimum versions. Net461 is pretty much the minimum I'd be willing to look at.

I'm morbidly curious, though - but maybe it is an irrelevant tangent - I'm not aware of any major license changes between VS2015 and later. I doubt it is key here, but if you have more details on that I'm curious :)

I'm working in a company which has more than 150 developers. We are not allowed to use VS2017 Community, and it costs us a lot to upgrade VS2015 PRO to VS2017 PRO for all developers, as what I'm told

rhubley added a commit to rhubley/Dapper that referenced this issue Jan 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.