Vetuviem.WPF.SourceGenerator
0.10.18
dotnet add package Vetuviem.WPF.SourceGenerator --version 0.10.18
NuGet\Install-Package Vetuviem.WPF.SourceGenerator -Version 0.10.18
<PackageReference Include="Vetuviem.WPF.SourceGenerator" Version="0.10.18"> <PrivateAssets>all</PrivateAssets> <IncludeAssets>runtime; build; native; contentfiles; analyzers</IncludeAssets> </PackageReference>
paket add Vetuviem.WPF.SourceGenerator --version 0.10.18
#r "nuget: Vetuviem.WPF.SourceGenerator, 0.10.18"
// Install Vetuviem.WPF.SourceGenerator as a Cake Addin #addin nuget:?package=Vetuviem.WPF.SourceGenerator&version=0.10.18 // Install Vetuviem.WPF.SourceGenerator as a Cake Tool #tool nuget:?package=Vetuviem.WPF.SourceGenerator&version=0.10.18
Vetuviem
Vetuvium is a toolkit to support View to View Model binding (MVVM → V2VM → Ve-Tu-Viem) aimed at offering a structure to get more re-usability out of ReactiveUI.
Mission Statement
- To give a mechanism to reduce the amount of boiler plate code being produced, by allowing some of the ReactiveUI specific logic to be hidden away
- Allow the developer to think along the lines of standard behaviours for controls by offering a way to produce re-usable behaviours through a class and\or function design pattern
- Allow the developer to focus on what matters on the ViewModel
- Reduce the cognitive load by
- Removing the risk of misusing 1 way or 2 way binding
- Remove the need for the user to think about having to cater for Bind vs BindCommand
- Offer a structure that allows for more work to be done potentially with Source Generators to reduce reflection and improve the build time developer experience.
Current Status
This is currently a proof of concept alpha. For understanding of the design reasoning please see https://www.dpvreony.com/articles/designing-vetuviem/
Nuget Packages
Purpose | Package | NuGet |
---|---|---|
Command Line Generation | Coming soon | Coming Soon |
Visual Studio Integration | Vetuviem.SourceGenerator | |
Core Functionality | Vetuviem.Core |
An example
Currently to write binding logic in the codebehind you have to write something similar to this for a single control
TODO
But what if you have a way to simplify logic and offer a way to even make it reusable without all the boilerplate leg work?
TODO
Sponsorship
TODO
Support
TODO
Contribute
TODO
Learn more about Target Frameworks and .NET Standard.
-
.NETStandard 2.0
- No dependencies.
NuGet packages
This package is not used by any NuGet packages.
GitHub repositories
This package is not used by any popular GitHub repositories.