Updated references #43
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Updated references to Unity (my primary concern) and all other nuget packages. Also added the nunit test adapter package to AutoMoq.Tests. I wasn't able to get tests running using the nunit test adapter extension, and the test console said this was the recommended way to add the test adapter.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here's a pull with updates for nuget packages.
I needed to fork specifically because it currently references Unity 4, whereas my project references the latest version. We apparently hacked this before by just dumping Microsoft.Practices.Unity.dll into the bin folder, but now we've moved to 4.7.2 and it's triggering some weird errors (binding errors for System.Runtime, specifically. 4.7.1 and 4.7.2 have been nightmares about binding problems).
If you want it, feel free. If not, nuke it and no worries. I'm going to throw my fork in a nuget package and throw it into our company's private nuget feed and roll.
Updated references to Unity (my primary concern) and all other nuget packages. Also added the nunit test adapter package to AutoMoq.Tests. I wasn't able to get tests running using the nunit test adapter extension, and the test console said this was the recommended way to add the test adapter.