Merge branch 'master' into dev

Author: ismcagdas

doc/Development-Guide-Angular.md

@@ -117,28 +117,46 @@ In addition to those fundamental modules, there are some share modules:
 
 ### Configuration
 
-Angular solution contains src/assets/**appconfig.json** file which
-contains some configuration for the client side:
+The Angular solution file src/assets/**appconfig.json** contains some 
+configuration for the client side. At runtime, the client scripts will 
+download this file, and use it to calculate the address of the server-side
+API:
 
--   **remoteServiceBaseUrl**: Used to configure base address of the
+-   **remoteServiceBaseUrl**: Used to configure the base address of the
     server side APIs. Default value: http://localhost:22742
--   **appBaseUrl**: Used to configure base address of the client
+-   **appBaseUrl**: Used to configure the base address of the client
     application. Default value: http://localhost:4200
 
-**appBaseUrl** is configured since we use it to define format of our
-URL. If we want to use tenancy name as subdomain for a multi-tenant
+The purpose of **appBaseUrl** is to enable the Angular client to decompose
+the browser address into tenant-name + base-url. 
+
+#### Subdomain Multi-Tenancy
+
+If we want to use the tenancy name as a subdomain for a multi-tenant
 application then we can define **appBaseUrl** as
 
 http://**{TENANCY\_NAME}**.mydomain.com
 
 {TENANCY\_NAME} is the place holder here for tenant names. Tenancy name
-can also be configured for **remoteServiceBaseUrl** as similar. To make
-tenancy name subdomains properly work, we should also make two
-configurations beside the application:
+must be similarly configured for **remoteServiceBaseUrl**. 
+
+It's important to understand that subdomain multi-tenancy is a function
+of the `DomainTenantResolveContributor` server-side class.
+This means that the server API **must** be accessed via a sub-domain that
+conforms to the format you have defined during your configuration of 
+AspNetBoilerplate (see 
+[Multi-Tenancy](https://github.com/aspnetboilerplate/aspnetboilerplate/blob/dev/doc/WebSite/Multi-Tenancy.md#determining-current-tenant) regarding preinitialization).
+
+<img src="images/angular2-core-subdomain-tenant-resolution-sequence.png" alt="Angular ASP.NET Core Sub-Domain Tenancy Overview" class="img-thumbnail" width="540" height="379" />
+
+To complete the setup of subdomain tenancy, we should also make two
+infrastructural configurations:
 
 1.  We should configure DNS to redirect all subdomains to a static IP
     address. To declare 'all subdomains', we can use wildcard like
-    **\*.mydomain.com**.
+    **\*.mydomain.com**. Note that if you have a split Angular/API
+    setup, then you will need 2 subdomain formats, such as
+    **\*.app.mydomain.com** and **\*.api.mydomain.com**.
 2.  We should configure IIS to bind this static IP to our application.
 
 There may be other ways of doing it but this is the most simple way.

doc/Step-by-step-publish-to-azure-angular.md

@@ -83,14 +83,14 @@ Select "**azure-publish-demo-server**" and click "**OK**", then click "**Publish
 The details will be explained in the next lines. Here are the quick steps to publish the **AngularUI** to the Azure
 
 - Run the `yarn` command to restore packages
-- Run the `ng build -prod`
+- Run the `ng build --prod`
 - Copy the web.config file that is placed in **angular** folder root to dist folder
 - Configure the **angular/dist/assets/appconfig.json**
 - Send the required files to the Azure
 
 ### Prepare The Publish Folder
 
-Run the `yarn` command to restore packages and run the `ng build -prod` to create publish folder that named **dist**.
+Run the `yarn` command to restore packages and run the `ng build --prod` to create publish folder that named **dist**.
 
 <img src="images/azure-publish-angular-publish-angular.png">
 

doc/images/angular2-core-subdomain-tenant-resolution-sequence.png

@@ -6,7 +6,20 @@ jQuery and ASP.NET Core + Angular versions beginning from v4.1. See
 
 The change logs in this page are just a summary of major changes. Detailed release notes are shared on the Github repository (only available to the customers).
 
-### v6.5 (2019-01-11)
+## v6.6.1 (2019-02-11)
+
+* Upgraded Xamarin package dependencies.
+* Bug fixes.
+
+## v6.6 (2019-02-08)
+
+* Implemented Metronic [demo6](https://keenthemes.com/metronic/preview/?demo=demo6) and [demo10](https://keenthemes.com/metronic/preview/?demo=demo10) layouts.
+* Implemented refresh token for the Xamarin app.
+* Switched to Google OAuth2 from Google+ API.
+* Upgraded to ABP v4.2.
+* Minor features, enhancements and bug fixes.
+
+## v6.5 (2019-01-11)
 
 - Implemented recurring payments for subscriptions (using [Stripe](https://stripe.com/))
 - Upgraded to PrimeNG v7.0.