-
Notifications
You must be signed in to change notification settings - Fork 80
Update dependency logic #460 #461
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
base: develop
Are you sure you want to change the base?
Update dependency logic #460 #461
Conversation
|
Can you explain why you've added .net6 as a compiling target to four projects (csproj files) but only effectively removed Microsoft.CSharp Version 4.7.0 from one of them? Can you explain why the other four projects required a change. While the above is an information request. we can't accept/approve this PR as it will introduce breaking changes. It appears that your haven't reviewed the class files for compiler declaration and control switches. A quick glance has identified that Please review code in ALL classes, make any required changes to update any relevant compile time control switches. Create unit tests to test the control flows are correct (usually this is introducing async methods so a unit test to make sure the method exists and a lambda expression compiles will suffice as the compiler will throw a method missing exception). |
|
Apologies for that. I have reviewed the compilation switches and nearly everyone I could find was already ok except for that one class you mentioned. Have also added the missing conditions on the dependencies. There should be no breaking changes as net 6 behaves the same as net standard. In relation to testing I have increased the test frameworks on the respective test frameworks. |
|
We're seeing compiler errors. Please address these. Seems to be that Package imports aren't being picked up Restore complete (1.6s) Also can you base this off the develop branch. We don't accept external PRs directly to master. |
|
Have changed the branch looked into the issues. It ended up being easier to target net standard 2.1 rather than net 6 due to wcf issues. |
|
Can you review all files you've modified. You've said you decided to target standard 2.1 rather than .net 6, however at least one csproj file still has a new target of .net6 it sounds like it shouldn't have. Cqrs.Azure.Storage.csproj comes to mind, but there appears to be several. |
|
WCF is only utilised in the base CQRS package hence adding net 6 was a big/risky undertaking for that project and the same time the high level outcome could be achieved by adding net standard 2.1 for that library. The other projects I remained with net 6 which was the preference. |
Closes #460