Nested classes for MVU

[libin85]

I have been lately spending a lot of time exploring MVU architecture and Comet. Its pretty cool and fun to work with. One thing that really bothers me in almost all MVU style coding is how much code that goes into a single class file.

Can we have nested classes where in one we draw the UI, and in the other we write the logic. More like Xaml and code-behind. Infact also blazor has a better approach
Reference: https://www.telerik.com/blogs/using-a-code-behind-approach-to-blazor-components

[Happypig375]

Can we have nested classes where in one we draw the UI, and in the other we write the logic.

It's called partial classes and you can already use them today.

[libin85]

Can we have nested classes where in one we draw the UI, and in the other we write the logic.

It's called partial classes and you can already use them today.

I totally get that, but I was asking if we could create like a nested class. Like how xaml and the code behind creates together

[Happypig375]

Like how xaml and the code behind creates together

It's also called "partial classes".

[libin85]

okay. did not know that.

[DingpingZhang]

If the "nested" you mentioned is the file structure shown below:

It is related to the configuration in the *.csproj file, not a C# syntax.

    <Compile Include="MainWindow.xaml.cs">
      <DependentUpon>MainWindow.xaml</DependentUpon>
      <SubType>Code</SubType>
    </Compile>

[charlesroddie]

You can also use a folder with two files.