Update FwLinks for RTM
Update FwLinks for RTM
Merging with release-6.1.0 and then putting FwLinks back to correct values for master
Added public Create methods to EnumType and EnumMember similar to other metadata item types.
Added unit tests.
Added public Create methods to EnumType and EnumMember similar to other metadata item types.
Added unit tests.
FirstAndLastName - updating the connection we crate for Empty Model CodeFirst to contain the namespace (fixes workitem #2063)
Merge branch 'release-6.1.0'
FuncionallyImportedToStoreProcedurally - changes enabling native support for TVFs and sprocs (implicit result mapping only) with Code First
FuncionallyImportedToStoreProcedurally - changes enabling native support for TVFs and sprocs (implicit result mapping only) with Code First
Changed internal call to target public surface and added more coverage on negative case tests
TooAssertive - the designer would show a bunch of asserts when "Save connection string" checkbox was unchecked (issue: #2064). There wer two root causes:
- one of the Asserts was not valid - TranslateConnectionString used to accept an empty string and would return the same value so I just removed the assert shorcircuit the logic for string.IsNullOrEmpty
- when the "Save connection string" checkbox is unchecked we clear the config name in the settings since it is not used in the database first approach but we tried to pass the value (which was empty) to the CodeFirstCodeGenerator which needed it for writing the DbContext derived class ctor. Now we are just using DbContext derived class name if "Save connection string" checkbox is unchecked.

Bonus: a fix for issue #2079 - Default constructor for OneEFWizard.cs is missing documentation header
Merge branch 'release-6.1.0'
Take a screenshot if the test fails
Merge branch 'release-6.1.0'
If NotNullableVariable is of type int, in the expression NullableColumn == NotNullableVariable there is an implicit cast of the variable to Nullable<int> that we did not handle and thus the expression produced for equality comparison had unnecessary terms.
string.Concat(string.Concat(new [] { "2073", "2075" }), string.Concat(null)) - fix for work items #2073 and #2075
- 2073 - String concantenate works for object[] but not string[] - enabled recognizing string.Concat overload that takes string[]
- 2075 - String.Concat(null) in queries throws - we were throwing ArgumentNullException which is actually the expected behavior (inline with what .NET Fx does) however the exception came from Linq parameter validation and contained an invalid argument name. Adding argument validation in the EF code made it possible to set the correct argument name.
Merge branch 'release-6.1.0'
Modified the logic for converting boolean expressions to case statements
so that ANY and ALL no longer produce poor-performing queries of the
form "CASE WHEN EXISTS (X) THEN 1 WHEN NOT EXISTS (X) THEN 0 END".

The relevant issue is: https://entityframework.codeplex.com/workitem/192.
If NotNullableVariable is of type int, in the expression NullableColumn == NotNullableVariable there is an implicit cast of the variable to Nullable<int> that we did not handle and thus the expression produced for equality comparison had unnecessary terms.
PaneFullOfErrors - displaying errors from ModelGeneration in the VS error pane.