Discuss "Best practice for project setup" in the .Net Development forum.

Hi

I got a project from an interior design and architectural company.
this application will be the same for both, infact they will both log
onto the same application, the only difference will be when entering
specifications for projects, the data entered will differ between the
architects and the interior designers.

With that said, some parts of the application will remain global, ie
Projects that they work on, and suppliers they use.

What would be the practice in set-up for this type of project?

Shem

I know nothing about architecture and interior design, so I don't know how the data would be handled.

However here is my advice:

• Use a single table for user data and includes a field that determines each users role
• Have a table that holds project data
• Ensure that the data the architects and interior designers enter reference the project ID.

I would need more information to give you more advice. What type of data are they entering? Depending on this, you may be able to use the same tables to store the data if setup correctly.

As far as .Net is concerned, I don't see how it would be different from any other project.

__________________
jmurrayhead
Did I help you out? Make me popular by clicking the icon!

If you found a post helpful, please click the button in the lower right-hand corner of the post.

Powered by ASP.Net

What i was really looking for was if there's a Set-up for a project that is broken up into smaller projects.

But then I'll just go and do it the way I've planned to do it, all i will do to break
it up is to create 3 folders in App_Code: Global, Interior, Architecture

Thanks
Shem

and my DA, BO, BL folders will be in each of those main folders

Shem

Yes there's a way. You can create separete projects and then reference those projects in another project.

For example, let's say you created a blog project, a forum project and a news article project. Now you want to build a web site that would use these projects. You would simply create a new project and add reference to the other three projects.

Of course, you would have to design the database and web site code to all work together. But that should be simple using the layered approach.

Do you recommend i go that way, or should i just do it my way?
considering this is my first .Net project, I don't want to have issues
when referencing other projects, and like i said, it's only the specs data
that differs between the 2?

Shem

I'd say the advantage of doing it that way is that you have a level of separation. In my example, you have 3 separate applications that eventually make a big application. Creating the 4 different projects gives that separation that makes it easier to work with. Especially if you have multiple developers working on the project.

In your case, I wouldn't say it is needed nor very beneficial.

Ok so i'll do it my way, thanks

Hi Shem, and what exactly would you want to separate the projects?
You can use them all in the same application, just create different folders for each.
I am sure you can manage the project this way.
Now if somewhere along the way, your company decides to invest in a few other developers
you can always use Visual Studio Team edition and share the same project.

Seeing how you are starting out, I'd have to agree with you and just do it your way.

If you get stuck somewhere along the way, you know where we're at

__________________
................... ASCII and ye shall receive ..................
Knowledge is the only resource on earth that multiplies when shared

If you found a post helpful, please click the 'Thanks' button in the lower right-hand corner of the post.