Object-Role Modeling Code

* Fix build issues on standalone VS2015 machine
* Remove extra predefinedDataType line from DCIL generator

Remove office icon dependencies
* Allows clean build on 2013 and 2015 without earlier VS versions
* Set version to September 2015. refs #193

Use VSIX installation with devenv /udateconfiguration for VS2012/2013/2015 Setup.sln
* Shows NORMA as an installed extension in VS
* /updateconfiguration will cause next VS launch to slow down and potentially file/new and opening the first .orm file. However, this is still much faster than devenv /setup, which has gotten significantly slower for each new VS version.
* Adjust vsix manifest editions for VS2013 and VS2015

VS2015 setup not installing ORMCustomTool or ORMGeneratorSettings for C# project
* Also added missing .pdb for DatabaseImport tool

Initial VS2015 port
* Early build: core is lightly tested, setup and extensions are not.
* VS2013 and VS2015 both have issues with the office icons, which were removed in VS2013 and later. This will be addressed in a later build, which will remove this dependency for all versions.

Fix some verbalization crushes with difficult subquery scenarios by checking for null returns on all uses of GetRolePlayerVariableUse. Most of this is defensive: I don't have scenarios for all of these cases, but triggered one of these cases with a partial binding to an incomplete subquery definition.

* Make attaching a subset constraint to a subtype line more consistent with other editing actions by allowing a double-click commit on the constrained subtype line.
* Updated constraint editing instructions to include directions for subtype lines.
* Updated version and readme files pending January 2015 CTP refs #193

Changes in [1556] incorrectly removed required variable quantification for uncorrelated path roots introduced in the middle of a derivation rule.

* Enhance verbalization support for subqueries by removing redundant 'exists' clauses whenever possible. Extra 'exists' would appear as part of the verbalized subquery expansion if a subquery result role or parameter was used in a function or value constraint but not in a fact type within the subquery.
* Block the context window from attempting to render subqueries. These would render poorly in most case, but actually crashed in the case of a subquery with a single result role.

Redo deletion of diagram with a repeated shape triggers a delete closure with no current transaction, which isn't handled by the multi shape code.
This is a hard crash. I have no idea why it wasn't caught years ago.