Accessing WCF server without using the generated code from svcutil

[Andrew Falanga]

Hi,

As you all may recall I've been working on a WCF client/server system
for some time. I have need of one of my clients to be able to access
the server and I'm hoping there's a way to configure the client to
access the server programmatically instead of having to use the stuff
generated by svcutil?

Basically, what this comes down to is the client has to be integrated
into another solution. To do so, the other solution needs to have a
reference to System.ServiceModel. This isn't a big deal, however,
other solutions reference the solution that I need to add my stuff
to. This is where Pandora's Box opens. These other solutions now
need a reference to System.ServiceModel and we'd like to avoid this.

Is it possible to do this?

Andy

 

[sloan]

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry
WCF with Interface Development

My article (above url) may be of assistance.

Code sample is downloadable.

I would check out idesign.net (downloads) as well. Juval is the master of
WCF.
I would buy his book as well.

a.. ISBN-10: 0596526997
a.. ISBN-13: 978-0596526993

 

[Andrew Falanga]

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry
WCF with Interface Development

My article (above url) may be of assistance.

Code sample is downloadable.

I would check out idesign.net (downloads) as well.  Juval is the masterof
WCF.
I would buy his book as well.

a.. ISBN-10: 0596526997
a.. ISBN-13: 978-0596526993

I guess I have a more fundamental question because the whole reason of
knowing if I can configure the client without using the App.config
file generated by svcutil is to find out if I can use the client
without referencing the System.ServiceModel library in the assembly/
project. I don't think so because it would seem as though that is
what is making this whole thing possible is the Service Model
library. Even if I can divorce myself from the App.config file and
instantiate a client object, I've still got to have the Service Model
library in order to "marshal" data from the client to the server and
vice versa, correct?

Andy

 

[sloan]

You could "publish" (expose) your WCF app as a webservice.
Then have your client subscribe to the webservice.

http://silverlight.net/learn/learnvideo.aspx?video=47174

While you are not using Silverlight (that I know of), some of the issues
will be the same.
You have to add some information to your config to publish your WCF as a
webservice (and allow the meta data to be published).

..............

Youre basically be creating a wcf app, but it is exposed as a webservice.
Then your client cares about the webservice, not anything "WCF"'ish.

Make sense?

...........

http://sholliday.spaces.live.com/Blog/cns!A68482B9628A842A!158.entry
WCF with Interface Development

My article (above url) may be of assistance.

Code sample is downloadable.

I would check out idesign.net (downloads) as well. Juval is the master of
WCF.
I would buy his book as well.

a.. ISBN-10: 0596526997
a.. ISBN-13: 978-0596526993

I guess I have a more fundamental question because the whole reason of
knowing if I can configure the client without using the App.config
file generated by svcutil is to find out if I can use the client
without referencing the System.ServiceModel library in the assembly/
project. I don't think so because it would seem as though that is
what is making this whole thing possible is the Service Model
library. Even if I can divorce myself from the App.config file and
instantiate a client object, I've still got to have the Service Model
library in order to "marshal" data from the client to the server and
vice versa, correct?

Andy