此ASP.NET项目的最佳方法 [英] Best approach for this ASP.NET Project

问题描述

你好，

我要开发一个新的ASP.NET项目，它将使用HTML5 + jQuery来提供数据...因为可视部分（简化的调用视图）可能会完成由合作伙伴而不是直接但我们（我们将提供服务）这种解决方案的最佳方法是什么？最初我在考虑使用ASP.NET MVC4，但是这样我们就可以给我们的合作伙伴提供具有核心业务逻辑的整个解决方案....有没有办法可以隐藏它？或者最好公开我通过ApiController提供数据的ASP.NET项目？



MVC模式中的另一个问题是我可以将项目划分为不同的程序集吗？ br />
谢谢

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

推荐答案

对于第一个问题，只需将后端代码编写为Web服务，然后JQuery可以在没有它们的客户端上使用它们看到实现。

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.

Web API是一个不错的选择。您只需通过API服务公开它们所需的内容即可。您必须为他们提供一个示例客户端应用程序，演示如何使用您的API和API概述手册，以解释API的基本概念和设计。以及API参考手册，其中包含API支持的操作列表。此外，参考手册应描述响应格式和查找值（如果有）。



您必须为开发人员提供沙箱环境，以便使用您的服务来开发和测试他们的应用程序。您的API服务应该能够处理以下事项..注册外部应用程序，正确的身份验证和授权，错误报告机制。



IMO，这不是一个好主意分享具有核心业务逻辑的整个解决方案。

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.

您好，

感谢您的回复....因为我认为我们必须分享项目在某种程度上...我只是在计划创建一个WebApi服务（真的不止一个）......我的问题更像是......我怎么能避免分享整个解决方案？我更好使用asp.net经典，所以他们将在他们的一边开发UI，最后我将与我的项目合并......如果我使用MVC，我将不得不分享整个项目...

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...

这篇关于此ASP.NET项目的最佳方法的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！