Documentation:Visual Studio: Difference between revisions

Visual Studio

Revision as of 17:47, 22 January 2017

When running MDriven in Visual Studio you have access to code generation.

If you open the model from within visual studio and it loads as xml and not as a model surface there is probably one of possible two 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 ecomdl file:

<None Include="yourmodel.ecomdl">

<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

This page was edited 25 days ago on 04/04/2024. What links here

@@ Line 3: / Line 3: @@
 If you open the model from within visual studio and it loads as xml and not as a model surface there is probably one of possible two 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 ecomdl file:  <code><None Include="yourmodel.ecomdl"></code>     <code><SubType>Designer</SubType></code>  <code></None></code>  when in fact it should look like this:  <code><None Include="yourmodel.ecomdl" /></code>  You can load the project file to manually fix this
+# 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 ecomdl file:
+<code><None Include="yourmodel.ecomdl"></code>
+<code><SubType>Designer</SubType></code>
+<code></None></code>
+when in fact it should look like this:
+<code><None Include="yourmodel.ecomdl" /></code>
+You can load the project file to manually fix this