Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. C#
  4. Web service question

Web service question

Scheduled Pinned Locked Moved C#
questionhelptutorial
3 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S Offline
    S Offline
    Steve Messer
    wrote on last edited by
    #1

    I am using WSE 3.0 to create a TCP web service. Everything was working fine until I referenced some classes from a separate dll. The proxy class generates fine and includes the classes from the separate dll. The problem is when the client calls the webservice with a calls that results in using classes from the separate dll the client throws an exception saying that I am using an object from an unreferenced dll. How to you reference this dll to make the client happy?

    D 1 Reply Last reply
    0
    • S Steve Messer

      I am using WSE 3.0 to create a TCP web service. Everything was working fine until I referenced some classes from a separate dll. The proxy class generates fine and includes the classes from the separate dll. The problem is when the client calls the webservice with a calls that results in using classes from the separate dll the client throws an exception saying that I am using an object from an unreferenced dll. How to you reference this dll to make the client happy?

      D Offline
      D Offline
      Drehmer
      wrote on last edited by
      #2

      Your client is probably receiving the message error from the server. So, I believe the solution is not in changing the client. Try to copy the DLL to the BIN folder in your WebService and see if it works. Charles.

      S 1 Reply Last reply
      0
      • D Drehmer

        Your client is probably receiving the message error from the server. So, I believe the solution is not in changing the client. Try to copy the DLL to the BIN folder in your WebService and see if it works. Charles.

        S Offline
        S Offline
        Steve Messer
        wrote on last edited by
        #3

        Thanks for your reply. It turns out that the problem was related to two different sets of similar classes. The code was using some objects from one set of classes and some from the other. The generated proxy code was all messed up thus confusing the client. Once we removed the duplicate (proof of concept) set of classes everything worked as expected.

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups