You can obtain a Source Code License to inspect and debug the MDriven Framework source code when your company needs source-level understanding, investigation, or troubleshooting.
What the Source Code License provides
The Source Code License gives your company access to source code for MDriven for Visual Studio. The delivered source is C# code that can be used to build runtime and design-time parts of the MDriven Framework, including the Visual Studio integration and the MDriven Designer model-editor components.
The source includes the implementation used to build ECO and Modlr. Modlr is itself implemented as an MDriven application and uses a meta-model that describes a UML model. This means that names in the meta-model are reflected in the implementation, which can help you trace how model concepts are represented in the code.
Use the source primarily when you need to:
- Understand what the framework does during a specific operation.
- Investigate a suspected framework defect at source level.
- Debug an issue in your local development environment.
- Review the source as part of your organisation's security and continuity process.
A Source Code License is an optional addition to the license for the MDriven Framework. It does not replace the requirement to maintain a valid, current license for MDriven assemblies during development and production; see NuGet license terms.
Who can hold a license
The license is issued to a corporation and is associated with named developers at that company. It is not issued to private individuals.
If a named developer leaves the company, the license remains with the company. Send MDriven the name of the replacement developer who will be associated with that Source Code License.
Access and delivery
MDriven delivers the source as an encrypted ZIP download. The licensee may request delivery up to four times per year.
To request a Source Code License:
- Prepare a signed purchase order from your corporation.
- Include the names of the developers who require access.
- If you are a European customer, include your VAT ID.
- Scan the signed purchase order.
- Send it to sales@MDriven.net.
Contact sales for current subscription fees, the number of named developers covered, and the current purchase terms.
What you may use the source for
The source files are confidential information. You may use them solely to debug the MDriven product, and you must protect them with at least reasonable care. Do not disclose the source files to third parties.
For example, if a framework operation fails in your application, you may inspect and debug the relevant source locally to identify the cause. You must not provide a source archive, source excerpt, or modified source file to a contractor, customer, or other third party.
Restrictions
Your right to use the source files depends on complying with the license limitations. You must not:
- Modify, adapt, alter, translate, merge, or create derivative works from the source files.
- Disclose, lease, rent, or loan the source files to a third party.
- Sublicense, distribute, or otherwise transfer the source files or any component of them to a third party.
- Remove, alter, or obscure confidentiality, copyright, trademark, or other proprietary notices.
- Reproduce or use the source except where the license expressly authorizes it.
Do not treat access to the source as ownership of the source. MDriven retains ownership.
The full agreement governs if there is any difference between this page and the signed license or non-disclosure agreement.
Building the delivered source
The source delivery includes code from which you can build framework components. The recommended approach is to build only the runtime assemblies you need, then continue to run the MDriven Designer and Visual Studio plugin from the standard installation.
For example, a minimal runtime build may include MDriven.Interfaces, MDriven.Handles, and, where required by your solution, MDriven.Persistence and MDriven.LinqExtensions.
The source build uses Visual Studio 2022. A full build requires a local strong-name key named ecokey.snk; that key is not distributed with the source. Follow the complete solution paths, signing-key placement, build order, and design-time build guidance in MDriven Source code instructions.
Changes and defect fixes
Do not make local changes to the delivered source as a normal development practice. If you identify a defect, report it to MDriven and use the source-level findings to support the investigation. Any local workaround should be treated as temporary and replaced by an official fix when MDriven provides one.
Continuity
The Source Code License is distinct from the continuity commitments described in Trust and Guarantee. In particular, that policy describes the circumstances in which a customer may receive source access needed to continue operations. Read that policy when evaluating operational continuity arrangements.
See also
- [[BestPractices:MDriven Source code instructions|MDriven Source code instructions]]
- NuGet license terms
- Trust and Guarantee
- Calendar-based license