Today I participated and lectured at an open source event. It was great to meet enthusiastic people that believe in something bigger then themselves. These events are always a mixture of young people full of vigor and need for rebellion as well as more balanced older people that have believed in open source for a long time.

I have been intrigued with open source and open source business models for a long time now, so I might belong to the second group.

In my last post I provided an example of PHP calling a .NET windows communication foundation web service. The PHP invoked the .NET service with no parameters, getting the time on server.

Sometime (well, most of the times) you need to pass parameters to the .NET web service. for example you might want to pass a client ID and get back its account balance.

Here is what you do:

I am done doing my first PHP to .NET interoperability example. In this example a PHP page calls a windows communication foundation (WCF) service in .NET

Here is what we want to create:

First create a "out of the box" windows communication foundation (WCF) WCF service library project.

Language syntax's, performance, PHP, Ruby, Java and who's better? Ahhhh! -

I was reading on The Server Side and came across this post:

http://www.theserverside.com/news/thread.tss?thread_id=43020#221954

which is part of this overall discussion:

When trying to debug a WCF ( windows communication foundation) .NET 3.5 framework library, you might encounter a problem where Visual Studio (VS 2008) refuses to run or debug the WCF web service.

the problem:

The error you get from the WCF test client when trying to debug the WCF service is this - "WCF Test Client: Unrecognized option 'targetclientversion' specified"

If this was a comics style blog it would start like this:

They both stood there, the clean and virtues super-hero MVC and his arch-enemy the dirty and corrupt spaghetti-design-pattern... they were both aware that only one of them will prevail.

When designing enterprise application architecture, talking to clients and doing interviews for my group, I sometimes tackle the “scale up vs. scale out” software architectural dilemma.

To set the stage lets define what scale means as well as what scale-up and scale-out mean.