I have client specific overrides for business rules. We run the industry standard & compliance related rules first and then the client specific rules. We are currently having main biz class having the standard rules and client specific rules as a decorator over that. Then we detect the client id passed and load the appropriate decorator. Assets are loaded through a CMS due to different branding elements.

While designing a MTA based system, how should we structure the application deployment such that we can build tenant specific functionality as well and restrict that to the requesting tenant. We need to design asset management so we can build on core and specific components and then load them at runtime based on the tenant who's requesting. Our environment is web+mobile client with thin server

When you are passing something to another function, it can get modified within that. The importance comes into picture if you want to know what happens after the function returns. If you do not care about the post-return stage, then you can pass by value/reference, it doesn't affects your application logic in anyway. However, if you are concerned with the after value, you need to pass by reference. Apart, given the framework implementation, an object is a heavyweight construct. So if we keep on passing such a huge object by creating a copy, it will hog up memory causing hung application and GC trigger. Hence the framework will auto (most i believe) will pass an object by reference and cause any changes to that be available outside the function as well. You can also pass a value type (structure) as reference, in which case it will be boxed into a reference type and then passed. C# allows you to explicitly specify "ref" and "out" decorators on parameters. If applied either, the changes are visible after the function return, else by default it gets passed as value.

What u mean by "bat country" ?

stop defamation...

This is the reason if u register explicit events handlers at start , you should release them at end.

Even if technically possible, what's the logical need of accomplishing it? Generics do allow specific types to be used, but this need is more like having a tree with each branch capable of bearing a different fruit :doh:

Code can solve a problem identified; but first identify the problem itself

Currently I am trying to incorporate the person user control as collapsible to show hide children. Also to show person's detail on mouse hover.

If your connection string is same, not integrated authentication, then you have 25 connections possible in your pool, unless u increase them manually. Otherwise, look for an open SqlDataReader which has caused exception and hence not got the connection close (you would have also missed the closing of connection in the finally block, for this to happen). Anyway, within a little time, the connection will timeout and return to your pool. So the issue cannot be continuous; if it is, then you need to look into the machine's event log to figure out the actual root cause.

It can be that you have encoded your connection string and while the user account has sufficient permissions to decode it on your own servers, it doesn't has so on the production servers.

Yes, the framework provides the libraries and runtime environment for the dll to run. When you create the setup project in visual studio, you can add a condition to check on the target machine. In this, add a condition mentioning that the required version of .net framework is installed; providing a location on MS site to get it if its not already installed. However, in most cases, you can expect it to be installed either by default or as part of some service packs Windows XP SP3 will have .net 3.0 installed Windows Vista comes with 2.0 pre-installed; SP will install further Windows 7 comes with 3.5 pre-installed

Its a simple design pattern named as "Facade" There are low level functions available in an API, but you might need to expose simpler interfaces to your "common" users; those who need very generic functionality. For specific cases, the users may take the pain of going deeper, but 95% of time, its not required. Hence wrapping an intricate functionality into a simple API (the target of Facade design pattern) provides both common as well as specific users the level of functionality desired by them. OOPS has lots to learn, and the more experience you get, the deeper you can think. Its good you want to get into design in 6 months and you would sure grow up to a happy professional :) Cheers (BTW: include design patterns in your quest, they would tell u a lot how things are designed)

A class with a single private default constructor cannot be inherited. It will always need some way to instantiate the parent...

Thanks Rob, it seems that your control can provide some guidance for the full family tree control. Would keep you posted if i get to design it further :)

Does anyone know about having a family tree control in silverlight. There's a WPF application on codeplex, but that is too extensive to show the already built tree on a website. Their's API is also too big to port back. In case anyone wants to do this with me, let me know.