Getting this damned HTTP-based WCF service running as non-admin

[Release] WSCF 0.7 - with support for XSD-based code generation

• Generate data transfer object/data contract code from schema descriptions in XSD or WSDL files - via the VS 2005 add-in and the command line tool.

• SOAP validation extension crashed when applied as an attribute.
• Could not remove multiple items at once from the operations list in step three of WSDL wizard.
• Byte arrays were not properly serialized when the code is generated with “Change casing” option.
• Code generation crashed when the configuration file contains the XML namespace information in the <configuration> element.
• Edit WSDL wizard crashed when the WSDL contains relative paths referring to a location outside the current directory (e.g. ../contracts/restaurantdata.xsd).
• When "Data binding" code generation was enabled the PropertyChanged event raising statements were not added to the property setters of types that inherit a parent type who implements the INotifyPropertyChanged interface.
• Importing multiple schemas with the same target namespace is now allowed.
• Visual Studio hogged the CPU when WSCF was installed together with certain other add-ins, like GhostDoc or the Windows Workflow Foundation Extensions.

Demo application from TechEd Developers 2006

It's Indigo baby!!!

After the tremendous effort (more than 4 years I assume) by building 42 people, WCF is finally released. Get it here and it’s time make enough room for “using System.ServiceModel” line in your code (y).

I really enjoyed playing around this product since it was not even publicly available (as far as I remember)… Congratulations to everyone in the Indigo team (I know this is how all you guys like to name it ;)).

thinktecture @ TechEd Europe Developers

dotnetpro - LINQ Video

In der aktuellen Ausgabe der dotnetpro gibt es ein dotnetpro.tv Video zu LINQ!

In dem Video zeige ich wie LINQ funktioniert und was dahinter steckt.

Christian

Straight-forward WCF duplex communication over MSMQ?

My friend Mike Taulty has recently posted a cool post about his attempt to create a WCF extension to leverage the duplex programming model over MSMQ.

This is a really interesting area (and of course has a huge potential) and at thinktecture labs I and Buddhike spent a great deal of time for research on this very topic.
On our way to a solution we came across exactly the same issues that Mike points out in his post. And it's kind of funny that the solution he's giving was the one came to our heads at the first place too.

Although it's a very decent attempt, this has a major architectural flaw because of MSMQ's inherent asynchronous and decoupled model and the handshaking nature of the RM protocol. Essentially the issue comes up because of using the reliable sessions channel for adding the ReplyTo addressing header to the messages. The Reliable Messaging protocol is a kind of a handshaking protocol which enforces the exchange of some protocol level messages (CreateSequence, ACK etc.) before the actual message exchange takes place.

On the other side, one of the biggest advantages of using MSMQ for messaging in your application is you can make sure that your application will work regardless of the availability of the services and clients (clients can send messages without the services being online and vice versa).
This nature of MSMQ stands in our way if we try to use RM/RS channel for adding ReplyTo headers. For example, if you start Mike's client without starting the service and try to send a message the client will end up with a timeout exception because when the client sends the message, the RS channel first tries to exchange the protocol level messages required to establish the reliable session. Since the service is not running and thus there is no RS channel up on the service