Best approach for this ASP.NET Project

Question

0.00/5 (No votes)

See more:

Hello,
I'm to develop a new ASP.NET project that will use HTML5 + jQuery to provide data...since the visual part (call views for semplicity) will probably be done by a partner and not direcly but us (we'll provide the services) what's the best approach for that kind of solution? Initially I was thinking of ASP.NET MVC4 but in that way we've to give our partner the whole solution that has our core-businness logic.... is there a way I can hide it? or it's best to expose a ASP.NET Project where I give via ApiController the data?

Another question in a MVC pattern can I divide my project into different assemblies?
Thanks

Posted 4-Aug-13 18:02pm

Ponzano Paolo

Add a Solution

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Soren Lorensen · Answer 1 · 2013-08-04T19:07:00

Solution 1

For first question, just write back-end code as web services and then they can be used by JQuery on client without them seeing implementations.

Posted 4-Aug-13 19:07pm

Soren Lorensen

John-ph · Answer 2 · 2013-08-08T02:26:00

Web API is a good choice. You can just expose only what is required for them through the API service. You will have to just give them a sample client application that demonstrates how to use your API and an API overview manual that explain the fundamental concepts and design of your API. And an API reference manual that contains the list of the operations supported by your API. Also, the reference manual should describe the response formats and Lookup values (if any).

You will have to provide a sandbox environment for the developers to use your service to develop and test their application. Your API Service should be able to handle the following.. registering an external application, proper authentication & authorization, error reporting mechanism.

IMO, It is not a good idea to share the whole solution that has core-business logic.

Ponzano Paolo · Answer 3 · 2013-08-04T20:45:00

Hello,
Thanks for your reply.... since I think we'll have to share the project in some way... I was just on my side planning of creating a WebApi service (really more than one)... my question was more like...how can I avoid of sharing the whole solution?It's better I use asp.net classical so they will develop the UI on their side and at the end I'll merge with my project... If I use MVC I'll have to share the whole project...

Best approach for this ASP.NET Project

3 solutions

Solution 1

Solution 3

Solution 2

Add your solution here

Preview 0