Troubleshoot MDriven Framework installation in Visual Studio 2022
This guide helps Visual Studio 2022 users diagnose local MDriven Framework installation and model-editor problems.
Confirm the VS2022 extension installation
Visual Studio 2022 uses a VSIX extension. Install the MDriven Framework build intended for Visual Studio 2022.
- Download the VSIX installer file from MDriven.net downloads.
- Run the VSIX file on the local computer to install or update the MDriven Framework.
- Open Visual Studio 2022 and confirm that the MDriven extension appears among the installed extensions.
For example, if you upgraded from Visual Studio 2019 and the MDriven model editor is unavailable in Visual Studio 2022, install the VS2022 VSIX rather than relying on the Visual Studio 2019 installation.
The .ecomdl file opens as XML
An .ecomdl file is an MDriven model file. If it opens as XML rather than as a model surface, check both the MDriven Framework installation and the project-file entry for the model.
- Confirm that the MDriven Framework for Visual Studio 2022 is installed.
- Open the project file and locate the entry for the
.ecomdlfile. - Remove the
<SubType>Designer</SubType>element if it is present.
For example, change this entry:
<None Include="yourmodel.ecomdl">
<SubType>Designer</SubType>
</None>
to this entry:
<None Include="yourmodel.ecomdl" />
Code generation fails or changes do not save
If Visual Studio reports that a model file belongs to the Misc Files project, add the model file to a real project, then close and reopen the editor tab.
For example, if Visual Studio reports Model file "C:\_path_to_your_project\YourProject.ecomdl" belongs to the "Misc Files" project, first ensure that YourProject.ecomdl is included in the project.
Resolve package references in your project
Use MDriven NuGet packages when your code references MDriven packages. Do not reference assemblies from the Visual Studio extension installation in your application build.
Some MDriven packages use SqlServerCe. If a SqlServerCe reference cannot be resolved, add the System.Data.SqlServerCe_unofficial NuGet package.
For example, when a project builds after adding MDriven NuGet packages but reports an unresolved SqlServerCe reference, add System.Data.SqlServerCe_unofficial to that project.
Avoid mixing Visual Studio extension assemblies with NuGet assemblies
The VSIX contains assemblies for the Visual Studio integration. Your project uses assemblies from NuGet. Do not use assemblies from the VSIX installation folder in your own builds.
Mixing these assembly sources can cause reflection failures, designer crashes, code-generation errors, and behavior that varies with assembly load order.