Skip to content
/ lab Public
forked from OData/lab

This repository is for exploring new ideas and developing early prototypes of various OData stacks.

License

Notifications You must be signed in to change notification settings

EMMWIS/lab

 
 

Repository files navigation

lab

Component Build Status
Connected Service Rolling
RESTier Scaffolding Rolling
WebApi Scaffolding Rolling

Introduction

This repository is for exploring new ideas and developing early prototypes of various OData stacks.

OData Connected Service Provider

  • Source

  • Visual Studio Extension

  • FAQ Question: The extension module is not loaded when debugging in the Visual Studio experimental instance, or it is not listed as part of the "Add Connected Service" options Workaround: Disable signing by going to the Project Properties > Signing and disabling both "Sign the assembly" and "Delay sign only" options.

    Question: In Visual Studio 2017, upon configuring the service endpoint in the OData Connected Services extension and clicking "Finish", I get an error message that says "Value cannot be null.\r\nParameter name: path1".
    Workaround: Download the Microsoft WCF ToolKit and install it. Then go to the registry and find the following key: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft WCF Data Services]. Create a duplicate of "VS 2010 Tooling" (if this doesn't exist, use "5.6" instead) named "VS 2014 Tooling". Then try again. (Special thanks to mohsenno1 for pointing this out.)

    Question: In Visual Studio 2017, upon configuring the service endpoint in the OData Connected Services extension and clicking "Finish", I get an error message that says "Cannot access".
    Workaround: Most reported issues for this error are related to authentication-based endpoints. This extension does not currently support authentication. To work around, download the metadata as a text file from the endpoint and then point the OData Connected Services URI to the downloaded file.

Unit Tests

The ODataConnectedService.Tests.sln contains the unit tests for the OData connected service. The folder structure of the tests mirrors the folder structre of the ODataConnectedService project. The base namespace for tests is Microsoft.OData.ConnectedService.Tests. Furthermore each test class has the same name as the class it is testing, followed by the suffix Test.

Example: for some class Microsoft.OData.ConnectedService.X.Y located in src\X\Y.cs, the test class would be Microsoft.OData.Tests.ConnectedService.Tests.X.YTest located in test\X\YTest.cs

OData v4 Web API Scaffolding

RESTier Scaffolding

The scaffolder simplifies the process of building an OData v4 service with EF.

About

This repository is for exploring new ideas and developing early prototypes of various OData stacks.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • C# 99.7%
  • Batchfile 0.3%