Oooh yea ? then where is the mooncheese at 7/11 ?

Yes I do. :-)

Come to think of it to be save should talk about the Encapsulation of Scotland and a creating a Singleton government instead of independent Scotland.

WiganLatics wrote:

Well maybe, but he might make it more of a Lounge question if he asks about whether the independent Scottish banks should upgrade from Fortran and Cobol

Lol lol lol

Now you get me thinking this is another yet to be successful european takeover.

How right can you be. :)

You should see the situation more from an open source point of view. If nobody has the guts you end up with giants producing shitty products. BTW they have Scots Whiskey what else do you need ?

To make the job as easy as possible for narcissistic undereducated employees in a uniform the work instructions are as follow: 1. Everyone is a terrorist 2. Don't smile to people they are on holiday you'r not. 3. Be as rude as possible.

ha ha ha ha ha Don't forget to overload the constructor Sub new if HaveSleptWithGirlAndGotHerpesButCantRememberBecauseDrugsAndAlcoholWereInvolvedAlsoWheresMyWallet= false then HaveSleptWithGirlAndGotHerpesButCantRememberBecauseDrugsAndAlcoholWereInvolvedAlsoWheresMyWallet=true end sub

Maybe you should model a Abstract Class for visits and then extend the properties as you go along

Abstract Class visit() inherits visit
dim long as decimal
ldim at as decimal
end class

Class littleVisit() inherits visit
dim HaveSlept as boolean
end class

Class littleBetterVisit() inherits visit
dim HaveSleptWithGirl as boolean
end class

Take a look at the Levenshtein distance

How do you advertise such a service ? :zzz:

Means that 99.9% of all the servers on the internet have porn ;P

Looks like someone has just read something about Domain Driven Development and was fiddling around a bit. :-D

Code from the time that Sex was safe and flying dangerous ;P

The problem with MSMQ is that the payload size is limited to 4 MB We created a actually a framework that can transport jobs to multiple machines using : 1. MSMQ (only as an event trigger) 2. WCF + MS SQL (for managing the job distribution transaction based ) 3. and a TCP component for async transport of the payload. 4. A base class that you inherit in each (windows service) application you build to process a job. This class gets and returns the payload to the WCF which stores or retrieve the data from the Database. On which server a job has to be processed and what process should handle the job is controlled by a simple xml flowlist. This flowlist can be requested from a WCF service.

I really have fallen in love with the DDD concept. In short this is how we always work out a project. All you need in the beginning is a whiteboard and a marker. 1. Define the domains within the scope of your project 2. Define the components within each domain. 3. VERY IMPORTANT: Give the domains and components GOOD names. 4. AGREE on the CONTRACTS of each component 5. Document your Diagram and Contracts. 6. Split the teams up each dealing with their component(s) and let them create UML diagrams. 7. Let each ULM diagram be coded out by a team that did not create the diagram.

One way to make it generic and easy adaptable is: Extend the .Net FileWatcher class and create a component that listens to certain file changes in a directory. Next Create a windows Service application that will use this component. The settings and number of instances can be made configurable through the app config file of your windows service application. When a Instance notices a file change write a message to the application log file of the windows event Log. Using the Windows Event viewer You then can create custom views that filter for your messages generated by your Windows service application. On each custom view you can attach a task that will be triggered each time a message is written. To this task you can attach a batch file, powershell script or VBScript that will execute and perform your needed functionality each time the task is triggered.

Parent Child ?