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. Web Development
  3. ASP.NET
  4. Problem with Interops

Problem with Interops

Scheduled Pinned Locked Moved ASP.NET
comhelpcsharpasp-netquestion
5 Posts 3 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.
  • A Offline
    A Offline
    Aman Sura
    wrote on last edited by
    #1

    I have deployed an asp.net web application that calls a method from COM Dll, register at my D:\algebra.dll root. The bin folder of my application contains: /bin Interop.algebra.dll .dll Application has only one webform that accepts a number and displays the result by multiplying it by 2. The function that performs the multiplication is called from COM Dll. Now i delete that method and re-register the dll "algebra.dll". I dont replace the Interop in the application's bin directory. The strange thing is that the method still gets called. Should it not give an error?:sigh:

    R J 2 Replies Last reply
    0
    • A Aman Sura

      I have deployed an asp.net web application that calls a method from COM Dll, register at my D:\algebra.dll root. The bin folder of my application contains: /bin Interop.algebra.dll .dll Application has only one webform that accepts a number and displays the result by multiplying it by 2. The function that performs the multiplication is called from COM Dll. Now i delete that method and re-register the dll "algebra.dll". I dont replace the Interop in the application's bin directory. The strange thing is that the method still gets called. Should it not give an error?:sigh:

      R Offline
      R Offline
      Rahul Kshirsagar
      wrote on last edited by
      #2

      As soon as you add a COM reference, the Interop.algebra.dll gets created in the bin folder. After this, whatever you do with the COM component, there will be no effect on Interop.algebra.dll till the time you remove the COM reference from your project and again add it.

      A 1 Reply Last reply
      0
      • A Aman Sura

        I have deployed an asp.net web application that calls a method from COM Dll, register at my D:\algebra.dll root. The bin folder of my application contains: /bin Interop.algebra.dll .dll Application has only one webform that accepts a number and displays the result by multiplying it by 2. The function that performs the multiplication is called from COM Dll. Now i delete that method and re-register the dll "algebra.dll". I dont replace the Interop in the application's bin directory. The strange thing is that the method still gets called. Should it not give an error?:sigh:

        J Offline
        J Offline
        Javier Lozano
        wrote on last edited by
        #3

        What does the registry point to after you re-register the dll? If you can get a codebase path, then you can figure out where the data goes to. ~Javier Lozano

        A 1 Reply Last reply
        0
        • R Rahul Kshirsagar

          As soon as you add a COM reference, the Interop.algebra.dll gets created in the bin folder. After this, whatever you do with the COM component, there will be no effect on Interop.algebra.dll till the time you remove the COM reference from your project and again add it.

          A Offline
          A Offline
          Aman Sura
          wrote on last edited by
          #4

          Thanks Rahul, But one thing i would like to mention that any changes in the method implementation in the dll are reflected. if method body initially multiplied the parameter by 2, and now it is changed so that it multiplies by 3, after re-registering the dll, the webapplication shows updated result with the same interop.(if earlier with a parameter 2, the result was 4, now it is 6). Method implememtation is reflected. A new method in the dll is not detected, then why is it that a deleted method still gets accessed?

          1 Reply Last reply
          0
          • J Javier Lozano

            What does the registry point to after you re-register the dll? If you can get a codebase path, then you can figure out where the data goes to. ~Javier Lozano

            A Offline
            A Offline
            Aman Sura
            wrote on last edited by
            #5

            Thanks, but can you please elaborate yourself. I could not get what you say.

            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