QuickModules provides you with a basic, modular framework for hanging API endpoints from. Internally using the Managed Extensibility Framework (MEF) to load modules, QuickModules gives you the ability to build encapsulated CRUD services without needing to write, or understand, the usual plumbing.
In order to ease any concerns you may have I will run through all the steps required (there are very few) to get QuickModules into your MVC application.
Step 0: Open Visual Studio (Duh!)
Step 1: Create a new MVC project
Step 2: Choose an Empty, Basic, Internet, Intranet or SPA template (actually, any will do, but these make the most sense)
Step 3: Notice how barren your project is without QuickModules. 🙁 (I’ve chosen a Basic template here)
Step 4: Install QuickModules using NuGet: Right-click on the References node in your Solution Explorer tree and click on “Manage NuGet Packages”:
Step 5: Search for “QuickModules” and choose “Install”. (Don’t worry if the details and version numbers look a little different on your PC, this is a screenshot of an early work-in-progress package).
That’s it! Hit F5 to run your application. If you’ve chosen an Empty or Basic template you’ll probably get a 404 Not Found error. Try navigating to the sample “Nearby Restaurants” module by adding /QM/Get?ActivityType=NearbyRestaurants to your URL (QM being shorthand for QuickModules of course!).
But Wait There’s More!
Built into the framework (and optionally supported by your modules) is paging, and filtering. All for the low, low price of $9.95. (Just kidding, it’s free). Use the LINQ-style Skip and Take arguments to control paging:
And use the Filter argument to narrow the result set down: