Design and Architecture

Not sure what the question is but Active Directory propagates data between servers. You can google for Active Directory Replication. Active Directory impacts login so if someone can't login then a replication timeliness issue would certainly be possible.

Doubt not found exception. What I have found instead is piece of work that is supposed to be done by you and you only. There is not doubt about that. Sorry!:thumbsdown: "With sufficient thrust, pigs fly just fine." Ross Callon, The Twelve Networking Truths, RFC1925

The view would ow the buttons. The document is, effectively, your model, so it will contain any data that you need. *pre-emptive celebratory nipple tassle jiggle* - Sean Ewington "Mind bleach! Send me mind bleach!" - Nagy Vilmos CodeStash - Online Snippet Management | My blog | MoXAML PowerToys | Mole 2010 - debugging made easier

SSEAR wrote: Hope you understand my situation. I certainly don't. Some problem involving X occured some time ago. What X is is irrelevant. How long ago is irrelevant. From that some less than ideal situation occurred. The causes for that are one or more of the following. 1. You failed to implement all of the known functionality. 2. You failed to design for known future uses. 3. Other uses failed to use your design (and thus implementation) correctly. 4. New features were needed. Obviously 1/2 are your fault. 3 is not something that you fix with code, but instead fix it with process (humans interacting with other humans in a defined way with the goal of reducing future problems.) 4 is a benefit of software development since it insures that there will always be jobs.

In 1971 (yes, 40+ years back), a book came out on Flowcharting. The book contained the usual blurbs on the dust jacket, including one about how the book even covered sharpening the pencil. But the most telling one was: Flowcharting is for the mentally retarded. Honest.

You could make your life a HELL of a lot simpler by not attempting to reinvent the wheel - there are loads of DI containers around (Castle Windsor, Unity et al) - take a look and you will probably find it easier (and will definately find it quicker) to use... C# has already designed away most of the tedium of C++.

If the user starts the print-action from, say, his browser, then the local computer will display a list of all available printers. If the printer is in the network, and the local computer has the correct drivers, it'll be able to print to there. Permissions are granted over the Active Directory. Printing is not an action that "raises an event". You could add code that instructs the server to print something on behalf of the user. Bastard Programmer from Hell :suss:

That is common practice with devices like TV set top boxes. Many use the Linux kernel and some required OS specific programs (often BusyBox) from the open source side and implement the main function in closed source applications. The source of the kernel and all code based on open source must be published according to their licenses. Each program written from scratch by you must not be published. A special case is linking open source libraries. These must have a GPL linking exception or are published under a license allowing such linkage like LGPL. Assuming you want to use the Linux kernel but implement nearly all other code yourself, I think it is possible. But it would be a lot of work and requires checking the licenses of the used open source components.

This article may help you... http://www.hanselman.com/blog/HanselminutesPodcast116DistributedCachingWithMicrosoftsVelocity.aspx[^] Distributed Caching with Microsoft's Velocity

you can use MOQ for mocking and IOC for running the test cases.

Now that's another problem that I'm gonna post in this website, because I can't make any WPF projects :(

The System.Threading.Timer can help you: its callback function does not run in the thread the timer was created.

The only way I know of is to use two windows. An invisible main window (the icon of which is shown in the taskbar) and your second window becomes the main window for the user.

Put some code on the first line of the event to log the time that it's fired. You'll find that it fires around the time it's supposed to, unless the app is in a loop without yielding processortime for the messagepump. Have a read of this[^] CP article :) Bastard Programmer from Hell :suss:

The most common route is to map the OO-objects to a relational model. Your database will need to have it's own design thought out, and preferably, normalized. OTOH, if you're using it merely as a datastore for said objects, then it might be more beneficial to dive into serialization. Bastard Programmer from Hell :suss:

A Decorator is used when the original class cannot be "extended" (because it is sealed or final, or written by someone else and you don't have source, etc.). In your example, the skills associated with a person can easily be maintained as an array of skills on the Person class. So this does not qualify as an apt example for a decorator pattern.

No problem[^]. First link seems very hot. :) Luc Pattyn [My Articles] Nil Volentibus Arduum