Skip to content
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

Ground work for Fluent Assertions 5.0 #463

Closed
8 tasks done
dennisdoomen opened this issue Aug 18, 2016 · 8 comments
Closed
8 tasks done

Ground work for Fluent Assertions 5.0 #463

dennisdoomen opened this issue Aug 18, 2016 · 8 comments
Assignees
Labels
Milestone

Comments

@dennisdoomen
Copy link
Member

dennisdoomen commented Aug 18, 2016

Ground Work

  • Switch to XUnit (for Devices)?
  • Switch to Cake
  • Move JSON support to a separate repo to support different release cycles
  • Drops support for .NET 4.0, Silverlight, Windows 8.0/8.1, WPA and Windows Phone for Silverlight.
  • Redirect contributors to the master branch for bug-fixes.
  • Move to dedicated organization
  • Start logo contest
  • Cross-compiles .NET Standard 1.4 (so we can support XmlDocument and UWP), .NET Standard 1.6 (to support .NET Core) and .NET Framework 4.5 (Merge the framework-specific versions into a single cross-compiled project #558)
@dennisdoomen
Copy link
Member Author

@onovotny any thoughts on this?

@clairernovotny
Copy link

LGTM :)

@dennisdoomen
Copy link
Member Author

@onovotny will this allow you to get rid of FA.Xamarin?

@dennisdoomen dennisdoomen changed the title Fluent Assertions 5.0.0 Plan Fluent Assertions 5.0.0 Aug 25, 2016
@dennisdoomen dennisdoomen added this to the v5.0 milestone Aug 25, 2016
@deRightDirection
Copy link

maybe also support for UWP?

@dennisdoomen
Copy link
Member Author

maybe also support for UWP?

Hmm, that would mean I have to target 1.4. @onovotny can you confirm?

@clairernovotny
Copy link

clairernovotny commented Oct 31, 2016

If you target 1.4, then that includes UWP. The differences between 1.4 and 1.6 aren't huge, and there's generally no reason to target a higher version than what you need. That enables broader platform support.

@dennisdoomen dennisdoomen self-assigned this Feb 4, 2017
@dennisdoomen dennisdoomen changed the title Plan Fluent Assertions 5.0.0 Fluent Assertions 5.0.0 Feb 11, 2017
@dennisdoomen dennisdoomen changed the title Fluent Assertions 5.0.0 Fluent Assertions 5.0 Jun 2, 2017
@adamvoss adamvoss mentioned this issue Jun 2, 2017
@SaroTasciyan
Copy link
Contributor

@dennisdoomen Regarding #257 planning to remove ShouldBeEquivalentTo() in v5 to prevent confusion?

@dennisdoomen
Copy link
Member Author

I was planning to give them the same behavior.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants