Skip to content

Conversation

pjlorenzo
Copy link

FluentAssertions, Ninject and .Net Framework updated

@kevinkuszyk
Copy link
Member

kevinkuszyk commented Feb 11, 2019

Hi @pjlorenzo thanks for your contribution.

Apart from the Fluent Assertions changes from the likes of act.ShouldNotThrow() to act.Should().NotThrow() are there any other breaking changes in consuming libs that are driving this update?

I usually like to keep the nuget dependencies as low as possible to avoid forcing consumers to have to upgrade and to maximise compatiblity. Bearing that in mind, a couple of questions:

  1. Is net461 the lowest TFM we can target? I'd like to be as low as possible to maximise compatablity for consumers.
  2. Is there anything driving the Ninject update which prevents a binding redirect for consumers?
  3. Likewise, can we downgrade Fluent Assertions to 5.0.0?

@kevinkuszyk
Copy link
Member

Closing as it's been superseded by #10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants