Object-Role Modeling Code

Cross-model constraint merging matched constraints that restricted the same roles irrespective of the join paths. However, separate join paths can lead to much different constraints, so this should be a primary requirement for matching, not a secondary consideration.

Fixed bug with cross model merge of shapes with multiple readings with same order.
Repro steps:
1) Drag a fact type with two readings on same reading order into another model.
2) Undo the drop
3) Reapply the drag/drop operation
Result: The second drop fails.

Internally, the named element dictionary for the reading signatures is holding a reference to the previous (now deleted) reading item keyed by the signature of the second item.

The dictionary event tracking code made a bad assumption about one-or-many-ness of a given relationship and overwrote the tracking information for the second reading. It is highly likely that this could also cause other bugs outside this scenario.

Bug fixes:
* Fix sample population editor VS crash with recursive identifiers.
* Allow test framework to run on 64-bit machines.

Bug fixes:
* Dragging fact types shapes from the model browser with attached role names and constraint shapes was creating multiple instances of each shape. This was a bad side effect of changes introduced and [1508] and [1527]. The MultiShapeUtility.ForceMultipleShapes directive is now removed and replaced with MultiShapeUtility.AllowMultipleShapes between creation and fixup of a new child shape resulting from an object browser drag operation.
* Added modality checks to the intersection of simple mandatory and single column subset constraints. There was no handling for this. This was a targeted fix and does not fix mandatory modality issues with other set comparison constraints.
* Don't serialized references to roles in the orm:PlayedRoles element if those roles are defined in an alternate partition. Continuation of work on [1519].

Minor miss from [1548].

* Require all extensions to use a load key that is a hash of the signed type name for the extension domain model.
* Modified data type verbalization (show length and scale at the end, show the data type for an entity type with a reference mode, replace 'Portable data type' with 'Data Type' (portable is not used anywhere else in NORMA).
* Fixed verbalization type (greater replaces greather)

* Additional work on build files. The build helpers were not referencing the correct dll versions, so some of the utility files used in the build were not being found on some builds. Specifically, VS2008 build failed on machines without a simultaneous VS2005 development build. Devtools will need to be rebuilt before a normal build.
* Fixed bug in relational view, which did not like other kinds of table shapes during a database refresh.

The recent changes from 4.0 to 12.0 as the default ToolsVersion for all project files (as part of the VS2013 work in [1533]) stopped the project files from loading in Visual Studio 2008. The ToolsVersion for all project files is now set to a fake tools version (12.34), and this version needs to match the corresponding tool requirements for each VS version.

To facilitate this, I've added a VSVer.bat to update the registry keys and set the TargetVisualStudioVersion for each VS release. The added version-specific batch files simply call VSVer (VS2008.bat runs VSVer 2008). These batch files need to be run from the corresponding 'Visual Studio 20xx Command Prompt' (opened as an Administrator) before launching a solutions in Visual Studio.

Note that the toolsversion setting was usually provided for a command-line build, effectively overriding the value in the .csproj file. Build batch files have been updated so that this is always the case. However, VS cannot be persuaded to pay attention to any similar tools version setting, and the placement of this attribute on the root element of .csproj file means that it cannot be macroized, so some creativity was required to allow a single project file to open in all versions of VS.

Fix a couple of diagram tab issues.
* Pressing the delete key while renaming a diagram tab would delete the selection on the current diagram instead of the selection in the text box.
* If the page reorder dialog is opened from a specific diagram tab then initially select that diagram.

Added initial database import for Oracle. Code provided by ORMFoundation user Jose Carlus for use with the Oracle-provided ODAC drivers.