Great news ! Jim Gray is going to speak @ TechEd Europe ! I'm really looking forward!

For everybody interested in attending my live MSDN Webcast tomorrow, here is the agenda: CodeDOM Introduction Assembly compilation Source code generation Source code parsing Advanced concepts Template based source code generation...

The answer to Issue 6 is maybe a bit surprising. One of the keys for successfully answering the quiz lies in the understanding of XML schema types . In the given example, xsd:integer has been applied to the message’s elements. It’s important...

Given the following schema, how will your corresponding CLR types look like? As always, answer and explanation will follow… < xsd:schema targetNamespace ="http://beatsch/issue6/types" xmlns : tns ="http://beatsch/issue6/types" ...

This post is part of Issue 5’s answer The previous post demonstrated that we have to care about the messages we pass around. At the end, it’s always about the process of defining contracts. Let’s think about the way we’re...

This post is part of Issue 5’s answer Messaging means that you really care about messages. But looking at our example, do we really care about them? You might say yes, because we define a CLR message that acts as the argument type for our...

This post is part of Issue 5’s answer As a result of step 1 (How to define a <MessagePredicate>) we go the following template for our <MessagePredicate> < wsp:MessagePredicate wsp : Usage ="wsp:Required"> wsp:GetBody...

This post is part of Issue 5’s answer I’ve highlighted the relevant artifacts in the following excerpt of the WS-PolicyAssertions spec: The contents of the <MessagePredicate> element is an XPath 1.0 expression...

The answer to Issue 5 is the following: < wsp:MessagePredicate wsp : Usage ="wsp:Required" xmlns : it ="uri:isssue5/types" xmlns : iw ="uri:isssue5/wsdl"> wsp:GetBody(.)/ iw:reqMsg/it:something > 4 </ wsp:MessagePredicate...

Together with Mario , I’m going to deliver the following content throughout Austria : Writing Secure Code: Essential Security Technologies (part 1) Writing Secure Code: Essential Security Technologies (part 2) Secure Application Architecture...

The information in this weblog is provided "AS IS" with no warranties, and confers no rights. This weblog does not represent the thoughts, intentions, plans or strategies of my employer. It is solely my opinion. Inappropriate comments will be deleted...

I’ve attended several session about WS-* specs in the past. One of the biggest problems is XML’s human readability. Instead of explaining the concepts many presenters just deal with the underlying XML representation. As a result, the session...

I’ve found the following thoughts quite interesting… Prolog: The WS-Policy framework allows you to make statements about your Web Services such as their preferences, requirements or capabilities. Since policies are part of the messaging...

CBDi explicitly states that this is NOT an April Fool! Check out their article how EU ensures chaos in media components. They question the EU government’s understanding of the following definitions: A component is a set of functionality...