<rsd version="1.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns="http://archipelago.phrasewise.com/rsd">
  <service>
    <engineName>MyGet</engineName>
    <engineLink>http://www.myget.org/</engineLink>
    <dc:identifier>https://www.myget.org/F/aggregatesource-ci/</dc:identifier>
    <dc:owner>yreynhout</dc:owner>
    <dc:creator>yreynhout</dc:creator>
    <dc:title>AggregateSource - Continuous Integration Package Source</dc:title>
    <dc:description>AggregateSource
===============

This library/code provides lightweight infrastructure for doing eventsourcing using aggregates. It's not a framework, and it never will be. Period.

The preferred way of using it, is copying it into your project and getting rid of all the cruft you don't need. That said, there are NuGet packages available for those of you that are pressed for time and don't mind following the prescribed recipe.

It's well suited for those scenarios where multiple aggregates need to collaborate and is lenient to saving multiple aggregates in one go should your underlying store allow you to do so or your problem domain require you to do so. Of course, nothing is holding you back from throwing when multiple aggregates have been changed. I just think this shouldn't interfere with the programming model you use.

## License

Licensed using a BSD 3-Clause License.

## Discussion

Have questions? Head on over to the discussion group: https://groups.google.com/forum/#!forum/aggregatesource</dc:description>
    <homePageLink>https://www.myget.org/Feed/Details/aggregatesource-ci/</homePageLink>
    <apis>
      <api name="nuget-v3-packages" blogID="" preferred="false" apiLink="https://www.myget.org/F/aggregatesource-ci/api/v3/index.json" />
      <api name="nuget-v2-packages" blogID="" preferred="true" apiLink="https://www.myget.org/F/aggregatesource-ci/api/v2/" />
      <api name="nuget-v1-packages" blogID="" preferred="false" apiLink="https://www.myget.org/F/aggregatesource-ci/api/v1/" />
    </apis>
  </service>
</rsd>