Documentation:Visual Studio: Difference between revisions

Visual Studio

Latest revision as of 08:53, 4 April 2024

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:

<None Include="yourmodel.ecomdl">    

<SubType>Designer</SubType> 

</None>

When in fact, it should look like this:

<None Include="yourmodel.ecomdl" />

Load the project file to manually fix this.

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

@@ Line 1: / Line 1: @@
-When running MDriven in Visual Studio you have access to [[code generation]].
+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 and not 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 ecomdl file:
+# 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">
+ <SubType>Designer</SubType>
+ </None>
-<code><SubType>Designer</SubType></code>
+When in fact, it should look like this:
+ <None Include="yourmodel.ecomdl" />
+Load the project file to manually fix this.
-<code></None></code>
+Read more on the [[MDriven Framework Visual Studio installation|MDriven Framework Visual Studio installation here.]]
-when in fact it should look like this:
+Read more on [[Switching to VS to access codedress from MDrivenDesigner]]
-<code><None Include="yourmodel.ecomdl" /></code>
-You can load the project file to manually fix this
-Read on the [[MDriven Framework Visual Studio installation]]
 [[Category:Visual Studio]]
+{{Edited|July|12|2024}}