Added NuGet packages

Author: LennardF1989

Lib/ClientDependency.Core.Mvc.dll

@@ -5,6 +5,11 @@ This example shows how that works in most cases.
 
 Please keep in mind our company has no access to Sitecore, so it's not tested on that platform. In theory it should however work just fine given all the dependencies below are there. Pull requests fixing this issue would be welcome!
 
+#NuGet
+You can get MvcApp from NuGet, it depends on uCommerce.Binaries.
+
+    PM> Install-Package uCommerce.MvcApp
+
 #Usage
 In order to use MvcApp, the only real required step would be registering a Mvc Route. 
 
@@ -36,16 +41,12 @@ From then on, you have multiple ways of utilizing Mvc in your App, please browse
 #Notes
 - Be sure to adjust the `deploypath` in the App.config before rebuilding.
 - The post-build event currently only works for Umbraco. 
-- The following libraries are required, we use an internal NuGet server for these. However, most can also be retrieved from an Umbraco + uCommerce installation, simply drop them in the Lib-folder and you should be ready to go:
+- The required uCommerce Binaries (uCommerce.Binaries) and the MvcApp (uCommerce.MvcApp) itself are retrieved from NuGet.
+- The following libraries are required and could be retrieved from NuGet, but we don't really need all the other stuff that comes with it. We got these DLL's straight from an Umbraco and uCommerce installation and include them for convenience:
  - ClientDependency.Core.dll
  - ClientDependency.Core.Mvc.dll
- - MvcApp.dll (Install MvcApp from the uCommerce App Store for this one)
  - System.Web.Mvc.dll
  - System.Web.WebPages.dll
- - UCommerce.dll
- - UCommerce.Infrastructure.dll
- - UCommerce.Pipelines.dll
- - UCommerce.Presentation.dll
 
 #Recommendations
 Even though we provide quite a few ways to build apps and extensions with MvcApp, we recommend to do as much as possible client-side (using something like Angular.js). This prevents unnecessary page refreshes giving a smooth experience to the user, while still leveraging the power of Controllers through Ajax calls. A great starting point for this is the `ExampleController`-method, which is a blank page which has all uCommerce dependencies injected (including Angular.js).

Lib/ClientDependency.Core.dll

@@ -1,3 +1,11 @@
 <?xml version="1.0" encoding="utf-8"?>
 <configuration>
+  <runtime>
+    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
+      <dependentAssembly>
+        <assemblyIdentity name="System.Web.Mvc" publicKeyToken="31bf3856ad364e35" culture="neutral" />
+        <bindingRedirect oldVersion="0.0.0.0-5.2.3.0" newVersion="5.2.3.0" />
+      </dependentAssembly>
+    </assemblyBinding>
+  </runtime>
 </configuration>

Lib/System.Web.Mvc.dll

@@ -49,8 +49,9 @@
     <Compile Include="uCommerce\RegisterMvcRouteTask.cs" />
   </ItemGroup>
   <ItemGroup>
-    <Reference Include="MvcApp">
-      <HintPath>..\..\Lib\MvcApp.dll</HintPath>
+    <Reference Include="MvcApp, Version=1.0.0.0, Culture=neutral, processorArchitecture=MSIL">
+      <HintPath>..\..\packages\uCommerce.MvcApp.1.0.0\lib\MvcApp.dll</HintPath>
+      <Private>True</Private>
     </Reference>
     <Reference Include="System" />
     <Reference Include="System.Web" />
@@ -59,22 +60,29 @@
       <HintPath>..\..\Lib\System.Web.Mvc.dll</HintPath>
     </Reference>
     <Reference Include="UCommerce, Version=6.9.0.15323, Culture=neutral, processorArchitecture=MSIL">
-      <HintPath>..\..\Lib\UCommerce.dll</HintPath>
+      <HintPath>..\..\packages\uCommerce.Binaries.7.0.0.0\lib\UCommerce.dll</HintPath>
+      <Private>True</Private>
+    </Reference>
+    <Reference Include="UCommerce.Infrastructure, Version=7.0.0.16029, Culture=neutral, processorArchitecture=MSIL">
+      <HintPath>..\..\packages\uCommerce.Binaries.7.0.0.0\lib\UCommerce.Infrastructure.dll</HintPath>
       <Private>True</Private>
     </Reference>
-    <Reference Include="UCommerce.Infrastructure, Version=6.9.0.15323, Culture=neutral, processorArchitecture=MSIL">
-      <HintPath>..\..\Lib\UCommerce.Infrastructure.dll</HintPath>
+    <Reference Include="UCommerce.Pipelines, Version=7.0.0.16029, Culture=neutral, processorArchitecture=MSIL">
+      <HintPath>..\..\packages\uCommerce.Binaries.7.0.0.0\lib\UCommerce.Pipelines.dll</HintPath>
       <Private>True</Private>
     </Reference>
-    <Reference Include="UCommerce.Pipelines, Version=6.9.0.15323, Culture=neutral, processorArchitecture=MSIL">
-      <HintPath>..\..\Lib\UCommerce.Pipelines.dll</HintPath>
+    <Reference Include="UCommerce.Presentation, Version=7.0.0.16029, Culture=neutral, processorArchitecture=MSIL">
+      <HintPath>..\..\packages\uCommerce.Binaries.7.0.0.0\lib\UCommerce.Presentation.dll</HintPath>
       <Private>True</Private>
     </Reference>
-    <Reference Include="UCommerce.Presentation, Version=6.9.0.15323, Culture=neutral, processorArchitecture=MSIL">
-      <HintPath>..\..\Lib\UCommerce.Presentation.dll</HintPath>
+    <Reference Include="UCommerce.Web.Api, Version=7.0.0.16029, Culture=neutral, processorArchitecture=MSIL">
+      <HintPath>..\..\packages\uCommerce.Binaries.7.0.0.0\lib\UCommerce.Web.Api.dll</HintPath>
       <Private>True</Private>
     </Reference>
   </ItemGroup>
+  <ItemGroup>
+    <None Include="packages.config" />
+  </ItemGroup>
   <Import Project="$(MSBuildToolsPath)\Microsoft.CSharp.targets" />
   <!-- To modify your build process, add your task inside one of the targets below and uncomment it. 
        Other similar extension points exist, see Microsoft.Common.targets.

Lib/System.Web.WebPages.dll

@@ -0,0 +1,5 @@
+<?xml version="1.0" encoding="utf-8"?>
+<packages>
+  <package id="uCommerce.Binaries" version="7.0.0.0" targetFramework="net452" developmentDependency="true" />
+  <package id="uCommerce.MvcApp" version="1.0.0.1" targetFramework="net452" developmentDependency="true" />
+</packages>