ASP.NET 解决方案的结构
我正处于创建 3 个截然不同的领域的 ASP.NET 解决方案的开始阶段。我将有一个客户区、一个客户管理区和一个内部管理区。这些领域中的每一个领域都显着不同，并且功能上不会重叠。我正在考虑按如下方式构建解决方案：
- 客户端（项目）
- 客户端管理（项目）
- 内部（项目）
- 通用库（项目）来保存共享任务。
这是构建解决方案的准确方法吗？我可能会遇到这样的陷阱吗？如果我想访问项目之间的一些用户数据，会话状态 (sql) 将如何跨项目工作？
感谢您的帮助。
I am in the beginning stages of creating an asp.net solution with 3 very different areas. I will have a client area, a client admin area, and an internal admin area. Each one of these areas is significantly different and there would be not be overlap in functionality. I was thinking of structuring the solution as follows:
- Client (Project)
- Client Admin (Project)
- Internal (Project)
- Generic Library (Project) to hold shared tasks.
Is this an accurate way to structure the solution? Are there pitfalls that I might run into with this? How would the session state (sql) work across the projects if I wanted to access some user data between projects?
Thank you for your help.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
您的项目结构看起来不错。
就会话状态而言，您可以将三个 Web 项目部署在一个应用程序下。
Your project structure looks fine.
As far as session state goes, you can deploy your three web projects under the umbrella of one application.
为什么不将这些项目作为一个整体进行整合呢？我在几个项目中看到，在困难的重构过程中，“内部”项目将被忽略或排除在构建之外。
Why not keep the projects together as one? I have seen on several projects where the "Internal" project will get neglected or excluded from the build during a difficult refactoring.