Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / July 2007

Tip: Looking for answers? Try searching our database.

TCP Webservice trying to use classes from a separate dll

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
smesser - 27 Jul 2007 17:04 GMT
I have a TCP webservice which ran fine until I added a dll containing some
common objects to webservice.

The proxy code generates fine but when I run the client requesting data that
results in using objects from the dll I added the client throws an exception
saying that I am using objects from an unreferenced dll.

The dll is referenced, any ideas what the problem might be here?
John Saunders [MVP] - 27 Jul 2007 18:53 GMT
>I have a TCP webservice which ran fine until I added a dll containing some
> common objects to webservice.
[quoted text clipped - 6 lines]
>
> The dll is referenced, any ideas what the problem might be here?

The client and service can NEVER, EVER, share types. They are two unrelated
entities.

Consider: how would you solve this problem if the client was written in Java
and the service in .NET? You would bt unable to share the DLL. That's how
you should solve this problem, right after you remove from the client that
reference to types shared by the service.
Signature

John Saunders [MVP]

smesser - 27 Jul 2007 19:06 GMT
Yes, you are correct and my problem wasn't what I thought it was.

A developer that is working on this code after me added a new set of objects
to the
server and was mix/matching between to two sets. Therefore the generated
proxy code was giving the client problems.

I had initially thought that the client needed to reference the common dll
but in reality it just needed good proxy code to work with.

Thanks for your comment.

> >I have a TCP webservice which ran fine until I added a dll containing some
> > common objects to webservice.
[quoted text clipped - 14 lines]
> you should solve this problem, right after you remove from the client that
> reference to types shared by the service.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.