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. .NET (Core and Framework)
  4. Web Service + Interop gives stale data

Web Service + Interop gives stale data

Scheduled Pinned Locked Moved .NET (Core and Framework)
csharpcomc++asp-netquestion
2 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.
  • _ Offline
    _ Offline
    _Superman_
    wrote on last edited by
    #1

    I have a web service in ASP.Net (C#) doing COM interop with a C++ COM component. After adding and removing the reference to COM many times, the data I get is old data. I believe the data is being cached somewhere. Any way to get over this?

    «_Superman_» I love work. It gives me something to do between weekends.

    J 1 Reply Last reply
    0
    • _ _Superman_

      I have a web service in ASP.Net (C#) doing COM interop with a C++ COM component. After adding and removing the reference to COM many times, the data I get is old data. I believe the data is being cached somewhere. Any way to get over this?

      «_Superman_» I love work. It gives me something to do between weekends.

      J Offline
      J Offline
      Jack Vanderhorst
      wrote on last edited by
      #2

      What sort of "data" do you mean? I assume since you're talking about a COM object that it just looks like an incorrect version in some way. Is it possible that you're actually picking up a different version of the DLL at runtime? Perhaps it's picking up the old one left in the application directory instead of the new one you're actually trying to reference? Try checking the locations in the PATH variable that contain incorrect versions of the DLL and get rid of them. Is it a Serviced component? Are you maybe picking up an older object from an object pool? I'm not even sure if this is possible, just an idea...

      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