Last post Jan 31, 2012 01:55 AM by karthikeyanar
May 02, 2008 11:18 AM|prady|LINK
May 02, 2008 03:52 PM|littlefool|LINK
Not really sure what you mean, but I guess you want some kind of a portal structure with modules that perform independent functionalities...
Seems you need to look into asp.net Web Parts ;)
Web Parts are the building blocks of a (dynamic) portal in asp.net. you can do much more with it, but basically it allows you to write user controls (ascx files) that perform 1 specific functionality and add them to a page where it appears as a "module"
together with others. Your modules can work individually but can also be connected with each other.
Heres the overview of web parts from msdn
Just google for Web Parts and you'll find much more information.
May 03, 2008 01:01 AM|prady|LINK
thanks for the reply. I am more interested in the concept of plugin architecture where in each component can be independent of each other and can be added in or removed from the application without affecting the other components in the application. sorry
for the usage of phrase "Plug and Play". I think plugin architecture could be the more apt word.
For instance i have portal for a company. It has various modules like finance, project management, bug tracking etc. I would like have an architecture which will allow me to add in new components like sales, HR added into it at a later stage. Or if i remove
any component existing in application it shd not affect the existing components.
Hope i am able explain my needs.
I am just trying to evaluate such a architecture is feasible in a web application. I know that this kind of architecture is used in desktop applications. Just wondering if this can be done in web applications also.
May 03, 2008 06:06 AM|littlefool|LINK
Still seems to me Web Parts is the way to go. After all, what you describe is the basics of a web portal. A page can hold multiple Web Parts (= Modules), each module is independend developed and added to the portal framework. You can add or remove web parts
dynamic in a later stage at runtime or static during design time on your pages.
It's pretty much the project I'm working on right now. We are also developing now a web portal framework. The portal will be used by different departments, each with access to their own modules and pages. Web Parts are the building blocks for this. The main
challenge of these kind of frameworks is not how to add or develop the modules, but how to secure them so that everybody sees or performs only what he is allowed to.
May 04, 2008 05:54 AM|prady|LINK
interesting.... I am just wondering how can we incorporate the usage of multiple pages in webpages in webparts... Would each each part link you up to new set of pages.. I am not very aware of webparts. Mayb i will do some research on that. Thanks for the
May 04, 2008 02:11 PM|littlefool|LINK
The pages are just aspx pages like any other web application. The Web Parts are just controls you drap and drop on your page. You can have 1 web part instance on multiple pages too. Just read up a little and if there are any other questions you can always
post them on the "web parts and personalization" forum.
Here's a "how do I" video on this site:
If you're looking for a good book about it, I can only recommend "asp.net 2.0 web parts in action" from Darren Neimke http://manning.com/neimke/. It has been an excellent resource in creating my portal framework.
May 04, 2008 02:21 PM|gunteman|LINK
May 04, 2008 07:42 PM|Imco|LINK
Seems to me like you're looking for more of a composite application than just the interface.
Check out the
Web Client software factory from MS's P&P team, it's designed to address this type of scenario. Even if you don't use the actual software factory you should be able to get some good ideas by looking at the reference implementation.
If it's too "heavy" (requires entlib and friends) you should also be able to (easily) get a clean separation of components (and consequently modularity) with the new
asp.net mvc bits, assuming you're familiar with the concepts behind MVC.
It's also possible with 'regular' webforms and/or web parts (that's all the software factory really is; just helped along by some base classes and code generation) but you'll likely find yourself solving a lot of the same problems and you'll have to come
up with your own application architecture (which isn't always a bad thing).
I hope that helps.
May 04, 2008 08:40 PM|SergeyS|LINK
I am looking to develop an application with various independent modules in asp.net. Can anyone provide with some links on good resources on this plug and play type architecture.
for example i have components like project management system, document management system which can work independently as well can be attatched into a common application...
You may wish to examine DotNetNuke http://www.dotnetnuke.com/
May 05, 2008 01:44 PM|prady|LINK
I think dotnetnuke is something which iam looking... In the meantime i also looking into WCSF which also i find very interesting...
I will update you guys on which framework i will use after i finish reading about both WCSF an dotnetnuke...
Since i dont have much knowledge of webparts i think i will stay away from it...Thanks for your pointer littlefool...
You guys rock out here.....
Jan 31, 2012 01:55 AM|karthikeyanar|LINK
See this url : http://www.fidelitydesign.net/?p=159
asp.net mvc create "project management" , "document management" plug and play architecture