Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 18:49
    dennisdoomen assigned #1363
  • 18:49
    dennisdoomen unlabeled #1363
  • 18:46
    dennisdoomen synchronize #1631
  • 12:38
    dennisdoomen review_requested #1631
  • 12:38
    dennisdoomen ready_for_review #1631
  • 12:38
    dennisdoomen edited #1631
  • 12:36
    dennisdoomen synchronize #1631
  • 12:35
    dennisdoomen synchronize #1631
  • 12:34
    dennisdoomen edited #1631
  • 12:32
    dennisdoomen synchronize #1631
  • Jul 30 05:36
    dennisdoomen opened #1631
  • Jul 27 19:55
    Fed03 closed #1402
  • Jul 27 19:54
    Fed03 commented #1498
  • Jul 26 06:44

    jnyrup on release-6.0

    Fake timing for unstable test o… Merge pull request #1630 from j… (compare)

  • Jul 26 06:44
    jnyrup closed #1630
  • Jul 26 06:27
    jnyrup opened #1630
  • Jul 26 05:27
    dennisdoomen commented #1085
  • Jul 26 02:32
    lonix1 closed #1629
  • Jul 26 02:32
    lonix1 commented #1629
  • Jul 25 19:24
    jnyrup commented #1085
Dennis Doomen
@dennisdoomen
The ProbingAdapterResolver is no longer needed. It was used to find by the PCL to find the platform-specific implementation of FA (e.g. NET 4.5, Silverlight, etc)

If NetStandard doesn't support Assembly, then we can just wrap it in #ifdef NET45

Scratch that. NetStandard does support Assembly. But getting the dependencies has to happen through DependencyContext.Default.CompileLibraries
and DependencyContext.Default.RuntimeLibraries. See https://stackoverflow.com/questions/30007264/get-available-types-in-coreclr

Stuart Blackler
@Im5tu
Cool - will alter the PR later :)
Stuart Blackler
@Im5tu
Not given up btw, just adjusting some free time :D
So I removed the unnecessary file, and got to the point of putting in the dependency context, but couldn't seem to find DependencyContext.Default so think i've done something wrong. That's where I am at
Stuart Blackler
@Im5tu
blob
That's what I am getting, any ideas greatly appreciated
Dennis Doomen
@dennisdoomen
Is it possible that it requires a higher version of NetStandard?
Stuart Blackler
@Im5tu
nuget.org says net standard 1.3
(and 1.6 & net451)
Dennis Doomen
@dennisdoomen
According to nuget. org, that 1.1.2 has some weird dependencies on some preview stuff. Try 1.1.1.
Raghav S
@raghav710
I would like to know on how to get a setup ready for the fluentassertions repo. I cloned the master branch and when I run psake.cmd or psake.ps1 I get
Exception: Exec: Er
ror executing command msbuild /v:m /p:Platform="Any CPU" $SlnFile /p:Configurat
ion=Release /p:SourceAnalysisTreatErrorsAsWarnings=false /t:Rebuild $logger.
I am a newbie to this repo, so please excuse any questions that seem obvious
Dennis Doomen
@ddoomen_twitter
The master branch needs Visual Studio 2015. The develop branch is WIP and requires Visual Studio 2017.
@Im5tu anything I can continue with? I'll probably have a bit more time the coming weeks.
Raghav S
@raghav710
@ddoomen_twitter I have VS 2015 and am on the master branch. Is running the VS build enough or do I need to run ./psake too?
Raghav S
@raghav710
hi, I am working on an implementation for fluentassertions/fluentassertions#557 and I am stuck at a point
Raghav S
@raghav710
In the GenericDictionaryEquivalencyStep class I want to check if one dictionary contains the other's keys. But since the key types are different (TExpectKey, TSubjectKey) I am not able to do a 2-way comparison i.e. I can do the .Contains() check one way by saying TSubjectKey:TExpectKey but then I wouldnt be able to do the comparison the other way
can someone give me some pointers to move forward?
Raghav S
@raghav710
@dennisdoomen any comments?
Dennis Doomen
@dennisdoomen
Sorry, missed your question. Eventually the comparison will use the TSubjectKey to compare the items in the dictionary, so that's the only thing you can make assumptions on.
Raghav S
@raghav710
@dennisdoomen thanks :smile:
Dennis Doomen
@dennisdoomen
If anybody wants to help with v5.0, the ground work to support .NET 4.5.1, .NET Standard 1.4 and .NET Standard 1.6 using a single cross-compiled project has been completed. See https://github.com/fluentassertions/fluentassertions/milestone/10 for the work that still needs to be done.
Dennis Doomen
@dennisdoomen
@/all this Gitter channel is going to be closed. Please join the official Slack channel at https://fluentassertions.slack.com