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

Application Architecture #2

Open
andymaster01 opened this issue Apr 8, 2014 · 6 comments
Open

Application Architecture #2

andymaster01 opened this issue Apr 8, 2014 · 6 comments

Comments

@andymaster01
Copy link

Hi Mark.

I have been reading your blog a lot lately, I see a lot of interesting reasoning in your posts.

I have question about this project, there is any document explaining the overall architecture for this demo?

@ploeh
Copy link
Owner

ploeh commented Apr 9, 2014

Thank you for writing.

This particular code base is one I've used for various presentations, so there's no document covering exactly this code base. However, this code base is an evolution of a simpler sample code base described in my MSDN Magazine article CQRS on Windows Azure.

For a further evolution on the thoughts presented here, see also my Pluralsight course A Functional Architecture with F#.

@scpeterson
Copy link

Hello Mark:

I am in the process of rebuilding an application from the ground up, and am advocating using AutoFixture, xUnit and AutoFixture Idioms. I remembered that there were good idiom examples in this project, and so I cloned it, opened it in VS 2013 and upgraded a few packages. I was able to work out many things that failed as a par of the upgrades, but I'm not sure how to deal with one test in DateViewModelTests. You have one test:
[Fact] public void SutHasDefaultConstructor() { Assert.DoesNotThrow(() => new DateViewModel()); }
xUnit no longer has DoesNotThrow as part of its API (xunit/xunit#188). The goal of the test is to verify that the DateViewModel class has a default constructor, but I'm not sure how to do that now. Any help would be much appreciated.

@ploeh
Copy link
Owner

ploeh commented Feb 3, 2015

Well, I don't agree with the decision to remove Assert.DoesNotThrow, but I do understand the arguments being made.

You could always do something like this:

[Fact]
public void SutHasDefaultConstructor()
{
    new DateViewModel(); // Assert that it doesn't throw.
}

@scpeterson
Copy link

Oh, I see, well that's simple enough, but not very descriptive; having Assert.DoesNotThrow, while possibly redundant, made it very clear what you were asserting. Thank you for your help.

@ploeh
Copy link
Owner

ploeh commented Feb 3, 2015

Yes, I agree with you, but I don't control xUnit.net.

@ploeh
Copy link
Owner

ploeh commented Feb 3, 2015

FWIW, I've now added a comment to xunit/xunit#188

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

No branches or pull requests

3 participants