https://github.com/Solution-Management/CtrlVAF

An extensive framework, made to make your life as an M-Files VAF engineer much more simple, powerful and S.O.L.I.D
https://github.com/Solution-Management/CtrlVAF

m-files reflection vault-application-framework

Last synced: 3 months ago
JSON representation

An extensive framework, made to make your life as an M-Files VAF engineer much more simple, powerful and S.O.L.I.D

• Host: GitHub
• URL: https://github.com/Solution-Management/CtrlVAF
• Owner: Solution-Management
• Created: 2020-07-24T11:39:48.000Z (over 4 years ago)
• Default Branch: main
• Last Pushed: 2022-12-07T20:40:41.000Z (about 2 years ago)
• Last Synced: 2024-10-07T20:16:01.950Z (4 months ago)
• Topics: m-files, reflection, vault-application-framework
• Language: C#
• Homepage:
• Size: 276 KB
• Stars: 5
• Watchers: 1
• Forks: 5
• Open Issues: 6
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

• awesome-m-files - CtrlVAF by Solution Management - Move logic out of the standard VaultApplication class into separate classes that can handle these tasks for the VaultApplication class. The design is based on the dispatcher/command pattern. (Development / Libraries and open source)

README

        
# CtrVAF

This package was created in order to move logic out of the standard VaultApplication class into seperate classes that can handle these tasks for the VaultApplication class.

The design is based on the dispatcher/command pattern. 

At this time there are three different dispatchers:

1. **Event** dispatcher that seeks out classes that react to M-Files events. These classes would replace the event handler functions on the VaultApplication class.

2. **Validation** dispatcher which seeks out classes that do custom validation on the configuration set in the admin tools. These classes would replace the logic happening inside the overrideable `CustomValidation()` method of the VaultApplication class

3. **Background** dispatcher which seeks out classes with a method that can be called as a background operation

Furthermore, every dispatcher can be decorated with a **Licensed** dispatcher to enable easy marking of license requirements on the handler classes.

All this minimizes the times the VaultApplication class needs to be reopened and edited. Perfect open/close on the VaultApplication class is not (yet) possible we think, but this is a step in that direction. 

For more information on how each dispatcher works and how to implement the handler classes, please take a look at the information in the relevant folder.