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. ASP and COM

ASP and COM

Scheduled Pinned Locked Moved ASP.NET
comquestioncsharpasp-netwcf
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.
  • F Offline
    F Offline
    fume
    wrote on last edited by
    #1

    Im developing a web application using ASP.net, my client have this COM, actually a TLB file. How can i use that COM in my application? I have 2 options, 1) is to add it as reference and 2) as a Web Service using SOAP... Which is better in these 2 options? or if there's any other option please introduce it to me.... tnx

    F 1 Reply Last reply
    0
    • F fume

      Im developing a web application using ASP.net, my client have this COM, actually a TLB file. How can i use that COM in my application? I have 2 options, 1) is to add it as reference and 2) as a Web Service using SOAP... Which is better in these 2 options? or if there's any other option please introduce it to me.... tnx

      F Offline
      F Offline
      fadee
      wrote on last edited by
      #2

      Hi The choice depends upon the context and future extensions and scalability options. If you want to re-write the component all over again in .NET, then I would recomend to write wrapper arround it in .NET and use it. This way in future you can change the implementation without disturbing the whole system. Now about webservices, if you are writing wrapper, then it is extremely easy to convert a .NET class into webservice. If you require load balancing or things like that then go for webservices. But do consider, webservices have slow response time as compared to component level communication. mE! ------------------- Therez No Place like ... 127.0.0.1

      F 1 Reply Last reply
      0
      • F fadee

        Hi The choice depends upon the context and future extensions and scalability options. If you want to re-write the component all over again in .NET, then I would recomend to write wrapper arround it in .NET and use it. This way in future you can change the implementation without disturbing the whole system. Now about webservices, if you are writing wrapper, then it is extremely easy to convert a .NET class into webservice. If you require load balancing or things like that then go for webservices. But do consider, webservices have slow response time as compared to component level communication. mE! ------------------- Therez No Place like ... 127.0.0.1

        F Offline
        F Offline
        fume
        wrote on last edited by
        #3

        i guess that's clear enough, thanks.. by the way, this COM that im working on is a TLB file written, i think in Java if not in VB6. Im not sure cause I don't have the info. but then how can i re-write or wrap this again in VB.Net? Im not experienced yet in "wrappers".

        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