Using custom namespaces when wrapping workflows in a web service

By default the web service wrapper generated around a workflow use the “tempuri.org” namespace. Not very pretty and certainly not something you want to use in a deployed application. So people started complaining and Microsoft listens (sort of).

 

Paul Andrew published the solution on this blog at http://blogs.msdn.com/pandrew/archive/2006/10/25/extending-the-wf-publish-as-web-service-or-get-rid-of-tempura-org.aspx. Now I don’t like it as it means searching for temp files with vague names, copying them and changing the generated code and ASMX page. Not exactly a pretty solution by any standards.

 

Unfortunately this is all we are going to get for now. Lets just hope a service pack to address this behavior doesn’t take too long (yea right).

 

And while I am going on about it, how come there is only an ASMX web servide wrapper and no WCF wrapper? Really sounds like that is what we are supposed to have in the first place.

 


One thought on “Using custom namespaces when wrapping workflows in a web service

Leave a Reply

Your email address will not be published. Required fields are marked *


*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>