Development tech.....

I want to break a project I'm working on up into smaller projects/applications/dll's. I need it to still live under the same folder struct though.

For instance I have root/User which has about 8 directors under it. Each directory is basicly a group of pages related to a certian set of data.

I'm starting to think I structered this badly because I have security setup in a fashion simular to a windows account. Meaning You get a name and password, and you can then be granted or denied access to things. Right now I have there main types of accounts that have there own groups of permissions. These can all be mixxed and match by an admin user but the system generally doesn't go for this and it is pretty point less to give a user permissions from several groups. Anyway, one dir/data set is source. In it I have a pages for each permission that would be involved with source: agent, reviewer, manufacturer and so on.

So what I have is a directory for a group of data and inside it pages that are accessed based on how you can use the data.

I have about 400+ files in this project. Not counting the data project and the business project. They each have around 200+ files.

This monster is getting hard to manage and update. My business and data projects are at a point where I rarely make changes to them so they are fairly easy to manage and I already have a plan to break them up some what to make changes to them go easier.

What I'm looking for is an idea or tried and tested way to build serveral web application that work together and will publish to the same root directory.

Anyone know what I mean or have any ideas?

So let me understand this...

you have 200+ pages, and they're all different depending on what type of user permission you have? Shouldn't the page dynamically address that? Or a menu on the left side of a page address it?

The menu removes or adds buttons based on a user's group or user permission...

Or the content area changes depending on the group or user permission?

"What I'm looking for is an idea or tried and tested way to build serveral web application that work together and will publish to the same root directory."

Web applications can make http requests to one another (webservices model).

But if you want to have 4 projects, and have them all publish to the same directory... and operate as one... I don't think maintaining that would be wished upon your worst enemy. They would have to exist in seperate directories under a parent directory.. and already I would be at a loss to figure out errors..

I know exactly what you mean about not wishing it on your worst enemy. It's a bad idea. I actually can do it though I tried it out. the trick is setting the projects default namespace to be the same on all projects and then you just create the folder structure so it will publish properly and move the rem the web config. It works but it is pointless.


As to the menu yes i have that. and yes I wanted to just have one page for each section of data and have it load UserControls but I had some problems and the boss was pushing so I did the quick thing to get up and running. I have a rebuild planned in two weeks though(I'm not telling the damn bankers) that's what brought this question on.

I plan to take my UserControls and my data and business dll and restruct the the project. to trim it down and fully implement my original design, but first I have to resolve this e-mail issue I am having.

See right now I have human resources and financ on me and this e-mail problem and I want to fix the application because it would run a lot better the way I designed instead of the way they forced me to wip out. Of cource they don't care about it working they only care about $$$ I spend most of my day in meetings and trying to keep them happy.

I have no techs, no programmers to work with and bunch of money men...... I'm stressed :afrog:

The crazy part is this is a small company but it's like corp. espianage around here