You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Change unit testing project to be .net framework instead of a .net core. Apparently there are issues when trying to use new features of 4.7 dotnetframework (e.g. named tuples) within a project and then referencing that project in one built upon dotnetcore. Manually changing the dependency bindings doesn't seem to work.
Would have to find a different way of storing user secrets as .netframework doesn't have a built in way like .netcore does.
This is just a request.
The text was updated successfully, but these errors were encountered:
Change unit testing project to be .net framework instead of a .net core. Apparently there are issues when trying to use new features of 4.7 dotnetframework (e.g. named tuples) within a project and then referencing that project in one built upon dotnetcore. Manually changing the dependency bindings doesn't seem to work.
Would have to find a different way of storing user secrets as .netframework doesn't have a built in way like .netcore does.
This is just a request.
The text was updated successfully, but these errors were encountered: