Incorrect ~site token resolution for CSOM for the subwebs

[SubPointSupport]

Issue

The following model would resolve the ~site token incorrectly, as the curretn sitecollection URL. In fact, all sub-webs' navigation would resolve ~site token as the web URL in the current, giving ClientContext.

var model = SPMeta2Model.NewWebModel(rootWeb =>
            {
                rootWeb.AddWeb(_web, web =>
                {
                    web
                        .AddQuickLaunchNavigationNode(CompanyPortalQuickNavigationNodes.General)

Token resolution for CSOM uses the current ClientContext instead of the "host web", so that all ~site token would always be resolved to the ClientContext's web even for the sub-webs.

Workaround

As a workaround, create a separate model for the subweb, create a new ClientContext and deploy the sub-web with the new ClientContex. In that case, ClientContext would have correct web and the token would be resolved to that web.

Will be fixed in the further SPMeta2 releases.

[SubPointSupport]

Added the following tests to ensure correct ~site token replacement.

• Can_Replace_Site_Token_On_RootWeb
• Can_Replace_Site_Token_On_SubWeb
• Can_Replace_Site_Token_On_SubSubWeb

SSOM passes.
CSOM fails on Can_Replace_Site_Token_On_SubWeb and Can_Replace_Site_Token_On_SubSubWeb

[SubPointSupport]

Added the following tests, all passed. CSOM re-engineering for all CSOM based model handler, full CSOM regression testing.

• CSOMTokenReplacementService_Should_Support_ClientContext
• CSOMTokenReplacementService_Should_Support_SiteModelHost
• CSOMTokenReplacementService_Should_Support_WebModelHost