7

After searching the entire day about what I should use, I'm not sure what option would be best for my needs so I hope someone with more experience could help me out.

I have a winforms application (c#) and a ASP.NET MVC 4 web application (c#). I wish to connect these, the goal is to send and receive data from the database which I use in the MVC 4 project, but from within the windows forms application. The data I send from the windows forms application to the database, is then used by the MVC 4 web application.

I am entirely new to web services / Web Api's so I can't really decide what option would be best. Any help would be much appreciated..

Renaissance
  • 798
  • 5
  • 15
Bram van den Besselaar
  • 89
  • 1
  • 5
  • 1
    @hawbsl: why did you put a bounty on this question? If anything is unclear, I think you'd better start your own question, where you explain what you're missing in the current answer(s). – CodeCaster Sep 26 '13 at 12:06
  • 1
    @CodeCaster question is clear enough (and it's more or less the question i wanted to ask) adding a dupe question wouldn't make sense. i am hoping for more & better answers and more scrutiny of the answers (even the single existing answer might be OK but i'm not perhaps knowleadgeable to judge. it didnt have any upvotes) – hawbsl Sep 26 '13 at 14:30

6 Answers6

3

If you already created MVC4 project then you can add actions to any controller and return JSON data like below :

public JsonResult GetCategoryList()
{
    var list = //return list
    return Json(list, JsonRequestBehavior.AllowGet);
}

or you can create new project of MVC4 and select WEBAPI template . It will create webapi project for you .It will create with example .so it will easy for to create webapi.In webapi it return data automatically convert to xml and json as per request

The WCF Web API abstractions map to ASP.NET Web API roughly as follows

WCF Web AP -> ASP.NET Web API
Service -> Web API controller
Operation -> Action
Service contract -> Not applicable
Endpoint -> Not applicable
URI templates -> ASP.NET Routing
Message handlers -> Same
Formatters -> Same
Operation handlers -> Filters, model binders

Other Links

Nirmal
  • 924
  • 4
  • 9
  • _"so it will easy for to create webapi."_ - now try to strongly-typed consume that service, for example a Windows application, because that is what this question is about. I'd say: skip WebAPI and go with WCF. – CodeCaster Sep 26 '13 at 12:05
  • How would you secure the Json GetCategoryList so that _only_ the Winforms app can consume it? and no one else – hawbsl Sep 26 '13 at 14:38
  • get username and password as parameter and then you can authenticate and authorise users.like paypal webapi – Nirmal Sep 26 '13 at 17:52
  • https://www.sandbox.paypal.com/webapps/auth/protocol/openidconnect/v1/authorize?" + "client_id=key&response_type=code&scope=openid profile email – Nirmal Sep 27 '13 at 11:44
2

If you have an MVC 4 App already, it would be better to use Web API (RESTful service) I assume you have some knowledge in building REST API (understanding of POST, PUT, UPDATE stuff)

It is simple in configuration and usage. All what you need actually is to create a new controller like:

class MyApiController: ApiController {

   public Post(SomeClass item) {
      ....connect to db and do whatever you need with the data
   }
}

You'll also should configure routing for Api.

And then in your winForms app you can simply use HttpClient class to perform api call.

HttpClient aClient = new HttpClient();

// Uri is where we are posting to: 
Uri theUri = new Uri("https://mysite.com/api/MyApi");

// use the Http client to POST some content ( ‘theContent’ not yet defined). 
aClient.PostAsync(theUri, new SomeClass());

Take a look at some implementation details right here: Web Api Getting Started

Get started with WCF is not so easy as with Web API.

SkSirius
  • 156
  • 1
  • 9
1

Given the tags you've used, my guess is that you're deciding between SOAP Web Services and WCF. Given these two, I say to go WCF. SOAP web services (as implemented in Visual Studio) are the older technology; still serviceable, but WCF can do everything an older SOAP service can do (including look exactly like a SOAP service) and more.

If you have a web service that connects your web server to your database server (these two things should be on different machines; your web server is exposed to the world by necessity, while your DB server should be locked down like Fort Knox), I see no reason why you shouldn't use that same service as-is for an internal WinForms application (using a LAN/VPN to access the service layer on the DB server). For a WinForms application that must access the data over the Internet, I would recommend reimplementing the service as a WCF service supporting secure encrypted data transfer. You can also set up the service endpoint to only accept HTTPS connections, and thus simply run your existing service through SSL/TLS.

What you choose will primarily depend on how much time-resources you can commit to resolving the problem; moving to HTTPS is a fast fix requiring little if any code changes, while reimplementing in WCF will take more time but will allow additional security measures beyond a simple secure tunnel.

KeithS
  • 70,210
  • 21
  • 112
  • 164
  • Thank you for the fast answer. The windows forms application will be sold as a product so there will be lots of different users who will need access to the database, over the internet. Furthermore, I am not choosing between SOAP or WCF, I am choosing between all possible solutions since I have no experience in this matter. I guess I will add a WCF service to my MVC project, as you recommended. Once again thanks for the answer. – Bram van den Besselaar Dec 10 '12 at 16:49
1

Or something lightweight like Nancy: http://nancyfx.org/

cja
  • 9,512
  • 21
  • 75
  • 129
  • do you wanna say anything more about what it is and why use it? the home page doesn't exactly contain an elevator pitch – hawbsl Sep 26 '13 at 14:31
1

We had some issues with MVC4 WebApi stuff and ended up using ServiceStack on the server side JavaScript/AJAX for web clients and RestSharp for thick clients.

One of our specific issues was the inability to auto generate documentation, significant performance differences, and better support for unit/integration testing.

Yaur
  • 7,333
  • 1
  • 25
  • 36
0

Rather than advocate specifically WCF, I'd recommend WCF Data Services or OData, with the stipulation that you'll need to secure it. If you go for pure WCF, you'll see that you'll end up creating a lot of code to handle retrieving the info from a database, and then sending that information right back out to your clients. It doesn't sound that bad, at first, but after about 30 entities in a database, you'll quickly grow tired of a pure WCF solution.

OData is great, it uses Entity Framework, and it quickly opens data manipulation for an existing database or one you are going to make. It will save you a ton of development time, if you can make your service secure. The format of the data response is flexible. There are plenty of client libraries ported for other programming languages as well.

The steps for securing a service are pretty simple. Always deploy to https. Any login or registration methods , need to be post methods, that return a token (Encrypted value), or a unique secret that can be encrypted and sent back for any subsequent requests. It's better to use the token, and have an expiration on the token.. because otherwise both your service and your app whether mobile or desktop, need to have a shared encryption / decryption method.

Renaissance
  • 798
  • 5
  • 15
Slack Shot
  • 1,090
  • 6
  • 10