OData Model Builder
Component | Build | Status |
---|---|---|
Model Builder | Rolling | |
Model Builder | Nightly |
1. Introduction
This is the official OData Model Builder repository.
2. Project structure
3. Building, Testing, Debugging and Release
3.1 Building and Testing in Visual Studio
Simply open the shortcut OData.ModelBuilder.sln at sln
folder to launch a solution that contains the product source and relevant unit tests.
The solution contains the corresponding test project. Please open it, build it and run all the tests in the test explorer.
3.2 One-click build and test script in command line
N/A
3.3 Debug
Please refer to the How to debug.
3.4 Nightly Builds
The nightly build process will upload a NuGet packages for Model builder to the MyGet.org odatanightly feed.
To connect to odatanightly feed, use the following feed URLs:
-
https://www.myget.org/F/odatanightly/api/v3/index.json (Visual Studio 2015+)
-
https://www.myget.org/F/odatanightly/api/v2 (Visual Studio 2012+)
You can query the latest nightly NuGet packages using this query: MAGIC OData query
3.5 Official Release
The release of the component binaries is carried out regularly through Nuget.
4. Documentation
Please visit the OData docs pages. It has detailed descriptions on each feature provided by OData model builderetc.
5. Community
5.1 Contribution
There are many ways for you to contribute to OData model builder. The easiest way is to participate in discussion of features and issues. You can also contribute by sending pull requests of features or bug fixes to us. Contribution to the documentations is also highly welcomed. Please refer to the CONTRIBUTING.md for more details.
5.2 Support
- Issues: Report issues on Model Builder issues.
- Questions: Ask questions on Stack Overflow.
- Feedback: Please send mails to [email protected].
- Team blog: Please visit https://devblogs.microsoft.com/odata/ and http://www.odata.org/blog/.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.