|
Home > Archive > BizTalk Server > March 2006 > WCF (WinFX Jan CTP) and BizTalk (2006 B2) problem
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
WCF (WinFX Jan CTP) and BizTalk (2006 B2) problem
|
|
| Paul Hester 2006-03-17, 5:52 pm |
| We have a WCF web service with BasicProfileBinding. We can Add-Web-Reference
to it from a C# project for example, but when attempting the same from a
BizTalk 2006 project, a dialog pops up and says "Failed to add a web
reference", and there's nothing that explains why it failed. Searched the web
and found someone with a simular problem who resolved it by removing some
stuff from devenv.exe.config, but that fix did not work in our environment.
Does anyone have info on this? Thanks. Note: we can still add a web reference
in the BT project if the web service is implemented with ASP.NET Web Services.
Thanks for any help,
-Paul
| |
| Jon Flanders 2006-03-17, 8:52 pm |
| Paul - I'm in favor of having a seperate .net assembly with the webservice
client. You can now configure this in the Send Port itself in 2006.
Jon Flanders [MVP]
http://www.masteringbiztalk.com
http://www.quicklearn.com/workflow.htm
> We have a WCF web service with BasicProfileBinding. We can
> Add-Web-Reference
> to it from a C# project for example, but when attempting the same from
> a
> BizTalk 2006 project, a dialog pops up and says "Failed to add a web
> reference", and there's nothing that explains why it failed. Searched
> the web
> and found someone with a simular problem who resolved it by removing
> some
> stuff from devenv.exe.config, but that fix did not work in our
> environment.
> Does anyone have info on this? Thanks. Note: we can still add a web
> reference
> in the BT project if the web service is implemented with ASP.NET Web
> Services.
> Thanks for any help,
> -Paul
| |
| Paul Hester 2006-03-17, 8:52 pm |
| Jon
We just recently moved from BT2004 to BT2006, and in response to your reply
here I went back and added a send port and can see it's now possible to
create a SOAP SendPort and specify an assembly containing the client proxy.
Yeah! I never liked in BT2004 that adding a web-reference created a "web"
port type; seemed odd to me and made dealing with schemas shared within the
orchestration and the web-service difficult, but I'm glad its been "fixed" in
2006. So, is it your recommendation that the easiest way to make the
clientproxy is to create an empty VS project, add a web-reference, and
reference its DLL when creating a SOAP send port?
Thx for your post!
"Jon Flanders" wrote:
> Paul - I'm in favor of having a seperate .net assembly with the webservice
> client. You can now configure this in the Send Port itself in 2006.
>
> Jon Flanders [MVP]
> http://www.masteringbiztalk.com
> http://www.quicklearn.com/workflow.htm
>
>
>
>
|
|
|
|
|