The Turnkey WebApplication uses MVC for index and login pages - it defaults to angularjs for all other pages. To get MVC on other pages you must set tagged value MVC=true on ViewModel.

MVC works differently from Angular in a number of ways - the main differences are these:

• Grid-row-clicks, in MVC select of row is done if there are zero or many actions, but if there is 1 action (defined in ViewModel) this action is executed on row click
• MVC never shows a popup menu of multiple actions as angular does

How to build MVC apps with MDrivenFramework

MVC_Generated_ViewModel_UI_in_MDrivenFramework

Comboboxes_in_MVC_from_model_driven_ViewModel

MVC_View_Model_handling

Getting_started_template_for_MDriven_MVC

MVC_White_paper_in_4_parts

New MVC Notes Autumn 2021

New nuget packages for .net5 and .netStandard are published on nuget and named MDriven.*

To get a package into a EcoSpace by code add an attribute to EcoSpace like [EcoSpacePackage(typeof(Package1Package))]

To get binding a codegen ViewModel to work go like this:

public IActionResult View([ModelBinder(typeof(VMClassBinder))] SampleViewModel value)
{
  return View("View");
}

To supress the bogus validation done on VMClass go like this:

var mvc = services.AddMvc(options =>
{
  options.ModelMetadataDetailsProviders.Add(new SuppressChildValidationMetadataProvider(typeof(VMClass)));
}); // to avoid validation of the complete world by following VMClass refs

To enable your page to roundtrip truly stateless we need to know the ViewModel name and Root object id on postback. Add these hidden fields in your form:

<input asp-for="ThisAsExternalId" hidden />
<input asp-for="ViewModelClass.ViewModel.Name" hidden/>

To use Runtime generated Razor files from ViewModel do like this - see comments on what each row is added and choose wisely: