Have you looked at the ibuyspy.com portal site? It has a great layout of writing modules to do what I think you are looking for. Toolbars are controlled by user controls, redirection to mobile environments done in the default.aspx, content driven from the sql db, etc. Really pretty cool scripting and a great way to explore layouting content. All mdules and display is controlled by a web based admin area too.
----- Original Message ----- From: Canalini Andrea <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, May 27, 2002 11:09 AM Subject: Re: [DOTNET] Input on the most commonly used design patterns > I'm novice in design pattern. I'm developing a generic framework to build > plugins-based applications. Each plugin implements a particular aspect of > the main program (sometimes are linked and sometimes they are very > different) . Every plug-in is hosted by the main app (the container). When > the plug is "hooked", change the "container" interface (toolbar, shortcut > bar and so on). I'm searching the best way to implement the "hook" > procedure. Has the pluggable factory something to do wich this kind of > application?. > > > -----Original Message----- > From: Alex Henderson [mailto:[EMAIL PROTECTED]] > Sent: Thursday, January 31, 2002 12:18 PM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Input on the most commonly used design patterns > > > My favourite design pattern is the pluggable factory, and I use it quite a > bit (of course it's certainly not the most common... that being > observer/subscriber, singleton and enumerator of course). > > The pattern I've used the least in C# is the MVC, as it's application to web > development doesn't really exist within the ASP.Net paradigm. > > I'm going to release my basic example of a pluggable factory soon because > it's not as easy to implement in C# as C++ - it's a little horrible in > fact - about 100+ lines of code, mostly reflection related, but for large > pluggably factory suites it has a much lower overhead - the only thing it > really needs now is a strongly typed custom collection to increase > performance and perhaps an IDE macro for creating a strongly typed version > of the classes to save on human error in implementation [my C++ version was > done using templates back in the day]) > > Cheers, > > - Alex > > -----Original Message----- > From: dotnet discussion [mailto:[EMAIL PROTECTED]]On Behalf Of > Manolito B San Jose > Sent: Thursday, 31 January 2002 5:44 p.m. > To: [EMAIL PROTECTED] > Subject: [DOTNET] Input on the most commonly used design patterns > > > Hi, all! > > just waiting for my Design Patterns book from Amazon. just wanted to > know from you guys what you think are the most useful and commonly used > design patterns in light of the capabilities of C#. > > Noli > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or > subscribe to other DevelopMentor lists at http://discuss.develop.com. > You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
