Last post Apr 20, 2011 11:36 AM by abhisheks
Apr 15, 2011 02:50 PM|Jordo C|LINK
I have some experience with asp.net and C# with building single purpose applications and such. I do not have any experience building anything large scale and now I need to build an application that houses a bunch of other application. The site will be
sort of an all in one admin tool that members of the helpdesk and other IT departments can use to complete various administrative tasks (creating accounts, creating mailboxes, setting rights, creating shares, etc).
I assume the best way to do this is to have a root website that hosts many other web apps. I would like to make use of a master page, so the various applications will be held nice and neatly in the MainContent placeholder. Each application will have its
own DLL and it will be called by the main site. This way, if a change needs to be made to one of the component apps, only that particular part will need to be recompiled. How does one do this? Is it as easy as having multiple projects inside of one solution
Thanks in advance
EDIT: Cleaned up question
Apr 20, 2011 12:14 AM|atconway|LINK
Your description makes this appear to be a major undertaking based on all of the potential functionality involved. I would be more concerned about getting my arms around all of the required functionality of the system, rather than if I am going to use a
Master page or not. Those are the minute details that will fall into place in the latter stages of design.
It sounds like you might be doing a lot of AD (Active Directory) manipulation (creating accounts, rights, email, etc). Have you considered using any of the native Windows Administrative Tools (from the Windows Server Tools pack) or any other free or purchased
software? If not, and you have to do everything from scratch, I recommend getting your hands around the requirements and then breaking down the project into small pieces.
An architecture like MVC or Domain Model would be a good way to go to account for the vast business rules and scalability needs that may arise. This way you have less of a chance of creating some monster page behind code mess for a large enterprise ASP.NET
Apr 20, 2011 09:03 AM|Jordo C|LINK
Thanks for the reply back.
I am not the best constructor of questions. I wasn't an issue of a master page, I was just trying to explain my needs from the UI down, I can admit not the best way to go about it. As for the other concerns, this tool is going to be an easy to use, one
stop shop for IT staff that isn't exactly accustomed to the MS admin tool kits. Some of the tasks are quite complex and can't be trusted to those below level 3 support. The tool will make these task double clickable thus de-bogging down the exchange admins
and so forth.
The only real question I have is, how do I build an application that is spread out over multiple parts (DLLs)? Therefore, should one of the parts need an upgrade, I would only have to recompile that part and swap out the DLL instead of the whole application,
which would be a much larger undertaking.
Apr 20, 2011 11:03 AM|abhisheks|LINK
have you looked at sharepoint ? If you got windows server, the basic sharepoint install should give you the portal and you can code around it?
Apr 20, 2011 11:23 AM|Jordo C|LINK
We actually have a large SharePoint environment, I never thought of that. I could build SharePoint applications and then attach them to a site of my own? Do you have any resources for this kind of project?
Apr 20, 2011 11:36 AM|abhisheks|LINK
Check out this link for sharepoint development. It's got developer kit as well. If you just walk through Get Started portion, you would get the idea.