structure of an asp.net solution

Question

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.

Answer 1

Your project structure looks fine.

As far as session state goes, you can deploy your three web projects under the umbrella of one application.

Answer 2

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.