Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread ASP.NET WebAPI/REST/ODATA support
Sun, Jun 28 2015 10:09 PMPermanent Link

Boris B

While I do go back to Turbo Pascal days, I've worked exclusively in C# since .NET 1.0 came out.

So, I'm more used to C# server back ends.

I take it given the strong JSON support, etc., that tying an EWB 2 app to an C# WebAPI/REST/ODATA backend is straightforward?

Is there a Help/technical article on best practices on this, or sample code?

I'm almost tempted to invest in a copy of Embarcadero RAD Studio, but my Object Pascal coding skills are rusty, and I'd rather leverage C# in the backend.
Mon, Jun 29 2015 3:59 AMPermanent Link

Matthew Jones

Boris B wrote:

> While I do go back to Turbo Pascal days, I've worked exclusively in
> C# since .NET 1.0 came out.
>
> So, I'm more used to C# server back ends.
>
> I take it given the strong JSON support, etc., that tying an EWB 2
> app to an C# WebAPI/REST/ODATA backend is straightforward?
>
> Is there a Help/technical article on best practices on this, or
> sample code?
>
> I'm almost tempted to invest in a copy of Embarcadero RAD Studio, but
> my Object Pascal coding skills are rusty, and I'd rather leverage C#
> in the backend.

Stick with C#. EWB is "just" a normal SPA tool, so you can access data
in whatever way you want just like any other AJAX system. I did an
application that used the TServerRequest object to talk to a normal C#
REST service. You can access the data however you want, XML, JSON or
custom. Version 2 has JSON enhancements, but it was possible before.

--

Matthew Jones
Mon, Jun 29 2015 8:34 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Boris,

<< I take it given the strong JSON support, etc., that tying an EWB 2 app to
an C# WebAPI/REST/ODATA backend is straightforward? >>

It's really just a matter of handling the dataset requests and being able to
respond with the correct JSON, as well as consuming transaction operations.

You can find a complete reference here:

http://www.elevatesoft.com/manual?action=viewtopic&id=ewb2&topic=DataSet_JSON_Reference

A good way to see what's going on is to simply load up this example
application in the browser of your choice, and turn on the network sniffing
functionality in the browser's developer tools:

http://www.elevatesoft.com:8081/transactions/transactions.html

Then just refresh the application and try performing a transaction.

And, if you have any questions while implementing the interface, you can
always ask here.

Tim Young
Elevate Software
www.elevatesoft.com
Mon, Jun 29 2015 11:45 AMPermanent Link

Boris B

Thanks for both replies.

The data set functionality is well documented and clear enough.

It was more WebAPI calls I guess that I wondered about, things like (in C#)

public UserPermissions GetUserPermissions();

public DateTime GetRevisedDesireByDate( GetReviseDesireByDateRequest request );

etc.
Image