VsSolution returns an E_FAIL COM error if the project cannot be found.
If the project was in a subfolder inside the solution then VsSolution was failing to find the project
using its unique name (e.g. 'MyProject\MyProject.csproj').
Project template containing ${SolutionName} in the ProjectReference/@Include attribute will have the project name expanded.
<ProjectItems>
<ProjectReference Include="..\${SolutionName}.Base.csproj" />
Project template containing ${ProjectName} in the ProjectReference/@Include attribute will have the project name expanded.
<ProjectItems>
<ProjectReference Include="..\${ProjectName}.Base.csproj" />
Project template containing ${ProjectName} in the Project/@directory attribute will have the project name expanded.
<Project name="${ProjectName}.Interface" directory="Base\${ProjectName}.Interface" language="C#">
Changed the Add New Database Connection dialog so when a driver is selected the
data source control is shown. This allows the user to enter connection details,
such as the username and password, without having to use the auto-discover button.
Change EnvDTE.ProjectItems.AddFileFromCopy to add .resx and .Designer.cs files to the
project with DependentUpon set to the parent file if a parent file is found in the project.
Fixes 'No migrations configuration type was found in the assembly' error when enabling migrations.
EntityFramework's Enable-Migrations cmdlet builds the project and then checks the generated
assembly for the configurations class that it added.
Enable-Migrations now works.
Workaround is to have the DTE class implement the System.IServiceProvider interface which is not
actually implemented by Visual Studio's EnvDTE.DTE class.