I have big plans for the CASK application.  I first want to get SharePoint under my belt so that I can understand it's interfaces and class structures.  CASK and SharePoint have quite a bit in common, i.e., they both can create Web Sites with sections; each site can have a Downloads, Calendar, Articles, Discussion and other types of sections.  

I'll use my http://www.CodePlex.com/SDMS application as the foundation for the next version of CASK - it will have a WinForm and Web (Silverlight) Interface utilizing the CompositeWPF/Prism and MEF packages.  My early goals are to design the Administrative functions that will permit the user to select a provider (SharePoint or CaskDotNet) and add sites, sections, users and roles as applicable.

WHY THIS INTRO for the Google verification topic?

I don't want to change the database structure of the CASK application.  I continue to maintain and update the CASK application but the focus of my work will be in the newer SDMS system (when released it will split in two with the web component being the new CASK application).   The inability to change the database structure can be problematic especially when I get a valuable upgrade request from a user that I want to implement into the existing CASK system.

I am not a big fan of reusing tables/fields for other than what they were intended for because it will make a confusing application more confusing - I want to move CASK in a user-friendly direction.   In this case I'll have to make an exception to the rule because I need to ensure those that rely on CASK (i.e., my business and it's clients) can easily upgrade to the new version when it releases - I need to leave the database intact.

For this Google verfication meta tag requirement (which I will now go into) I will reuse the CASK Transformation feature (blogged about HERE).

If you register for Google and go to WebMaster tools you will have the opportunity to register your website(s) with Google.  One of the options is to have Google generate a "Verification meta tag" that you can place on your main page.   In the example below I am using the fake tag "OI812NItWasGr8" for Google's meta tag name "verify-v1".  CASK will use the internal ID of GoogleVerify.

Since CASK is a Data-Driven system, which can support mulitple sites, this Content will change per website configuration.  We have to have a way to let CASK know which content to serve up for each applicable Community (website).

To configure the Google provided meta tag for your system using CASK you'll first have to know your community name.  To obtain this go to the Communities link and locate the "Name" for the applicable Community / Site.

Now that you know your community name you can configure the site by following the directions for Transformations (blogged HERE) and add the following configuration to the Transformations section - IT IS IMPORTANT THAT YOU FOLLOW THE STEPS IN THE METIONED BLOG FROM IT'S HOMEPAGE!! 

from: gv.Localhost=OI812NItWasGr8
to: --

Where "gv." tells the CASK system that this is a Google Verification meta tag and the value is 0812NItWasGr8 - you will plug in the value provided by Google (without quotes) and you are done. Example follows:

SOURCE AVAILABLE HERE  ChangeSet 45115

MORE ON THE CODE CHANGES HERE 

 

Tags: cask documentation
Categories: