Create separate projects for separate concerns about webapicontrib HOT 6 CLOSED

Would there still be a way to bring them all into a project? I would think knowing about and using MessageHandlers would be nice, but somebody might "accidentally" discover the benefits of using MessageFormatters because they have everything.

from webapicontrib.

I think part of this depends on how you plan on publishing to OpenRasta and Nuget. Just one package or fine grained packages. Users might not want everything under the sun just to get a protobuf-net MediaTypeFormatter.

from webapicontrib.

@motowilliams that's what I was thinking when I wrote the issue.
Maybe we can create 1 big package with everything and fine grained ones as well?

from webapicontrib.

As @ChrisMissal noted, nothing stops us from having separate, tiny projects and another project that includes everything. I'd argue for one "master" project with everything and then separate copies for each fine-grained assembly we want. Most people will probably try the "master" project first to get a feel for it, and more than project packaging, documentation will win people to using the different contrib features. We need to start writing!

from webapicontrib.

I think this can now be closed. The only remaining item is to create unique packages for WebApiContrib, Testing, SelfHost, and WebHost.

from webapicontrib.

Agreed.

from webapicontrib.