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
Update code/references for final .NET Core 3.1 release #1405
Comments
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2019
…em.Security.Principal.Windows-4.7.0 Bump System.Security.Principal.Windows from 4.6.0 to 4.7.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2019
…osoft.AspNetCore.Components-3.1.0 Bump Microsoft.AspNetCore.Components from 3.0.0 to 3.1.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2019
…em.ComponentModel.Annotations-4.7.0 Bump System.ComponentModel.Annotations from 4.6.0 to 4.7.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2019
…em.Security.AccessControl-4.7.0 Bump System.Security.AccessControl from 4.6.0 to 4.7.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 4, 2019
…em.Data.SqlClient-4.8.0 Bump System.Data.SqlClient from 4.7.0 to 4.8.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 5, 2019
…em.Security.Permissions-4.7.0 Bump System.Security.Permissions from 4.6.0 to 4.7.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 5, 2019
…osoft.AspNetCore.Components.Web-3.1.0 Bump Microsoft.AspNetCore.Components.Web from 3.0.0 to 3.1.0 in /Source #1405
rockfordlhotka
added a commit
that referenced
this issue
Dec 5, 2019
…em.Configuration.ConfigurationManager-4.7.0 Bump System.Configuration.ConfigurationManager from 4.6.0 to 4.7.0 in /Source #1405
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When Microsoft releases the final .NET Core 3.1 we need to run through and make sure all the code/dependencies are correct for that final release. That should be the final step before the CSLA 5.1.0 release.
The text was updated successfully, but these errors were encountered: