Documentation:Visual Studio: Difference between revisions

Visual Studio

Revision as of 05:49, 18 July 2023

This page was created by Hans.karlsen@mdriven.net on 2017-01-22. Last edited by Stephanie@mdriven.net on 2025-01-30.

You have access to code generation when running MDriven in Visual Studio.

If you open the model from within Visual Studio and it loads as XML instead of as a model surface, this is probably one of two possible problems:

You have not installed the MDriven Framework for the correct version of Visual Studio
Your ecomdl file has been tagged by VS to open in the XML designer - if this is the case, the project file looks like this on the node for the ecomdl file:

<SubType>Designer</SubType>

</None>

when in fact it should look like this:

<None Include="yourmodel.ecomdl" />

You can load the project file to manually fix this.

@@ Line 1: / Line 1: @@
 You have access to [[code generation]] when running MDriven in Visual Studio.
-If you open the model from within Visual Studio and it loads as XML instead of as a model surface, there is probably one of possible two problems:
+If you open the model from within Visual Studio and it loads as XML instead of as a model surface, this is probably one of two possible problems:
 # You have not installed the MDriven Framework for the correct version of Visual Studio
 # Your ecomdl file has been tagged by VS to open in the XML designer - if this is the case, the project file looks like this on the node for the ecomdl file:
-<code><None Include="yourmodel.ecomdl"></code>
+<None Include="yourmodel.ecomdl">
-<code><SubType>Designer</SubType></code>
+<SubType>Designer</SubType>
-<code></None></code>
+</None>
 when in fact it should look like this:
+ <None Include="yourmodel.ecomdl" />
-<code><None Include="yourmodel.ecomdl" /></code>
 You can load the project file to manually fix this.
 Read more on the [[MDriven Framework Visual Studio installation|MDriven Framework Visual Studio installation here.]]
 [[Category:Visual Studio]]