COM issue under .NET

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • Bryan Gan
    #1

    COM issue under .NET

    Dear all,

    Can I know is there any improvement if develop COM
    under .NET comparing to develop COM using VC6?

    thanks.
    Tags: None
    • Scott M.
      #2
      Re: COM issue under .NET

      You can't develop COM applications in the .NET Framework.

      You can CALL a COM component and use it within a .NET application, but this
      usually creates a performance hit, since the .NET Framework will have to
      create a runtime callable wrapper class around your COM object.


      "Bryan Gan" <gcy80@yahoo.co m> wrote in message
      news:084e01c36c 6e$46d8edd0$a50 1280a@phx.gbl.. .[color=blue]
      > Dear all,
      >
      > Can I know is there any improvement if develop COM
      > under .NET comparing to develop COM using VC6?
      >
      > thanks.[/color]


        Comment

        • Rob Windsor
          #3
          Re: COM issue under .NET

          Actually you can create COM components using .NET, or at least using VB.NET
          and C#, I'm not sure about other languages. COM Interop works both ways, you
          can use TLBIMP to create a runtime callable (RCW) so that .NET can use a COM
          component or you can use TLBEXP to create a COM callable wrapper (CCW) so
          that COM enabled applications can use you .NET component.

          One resource that describes this in detail is "Profession al Visual Basic
          Interoperabilit y" by Lhotka and Hollis (WROX).

          ---
          Rob Windsor
          G6 Consulting
          Toronto, Canada



          "Scott M." <s-mar@badspamsnet .net> wrote in message
          news:%235dB2Nzb DHA.1872@TK2MSF TNGP12.phx.gbl. ..[color=blue]
          > You can't develop COM applications in the .NET Framework.
          >
          > You can CALL a COM component and use it within a .NET application, but[/color]
          this[color=blue]
          > usually creates a performance hit, since the .NET Framework will have to
          > create a runtime callable wrapper class around your COM object.
          >
          >
          > "Bryan Gan" <gcy80@yahoo.co m> wrote in message
          > news:084e01c36c 6e$46d8edd0$a50 1280a@phx.gbl.. .[color=green]
          > > Dear all,
          > >
          > > Can I know is there any improvement if develop COM
          > > under .NET comparing to develop COM using VC6?
          > >
          > > thanks.[/color]
          >
          >[/color]


            Comment

            • Rob Windsor
              #4
              Re: COM issue under .NET

              Hi Scott,

              OK, I see what you're saying now. You're right, you can't do it natively in
              ..NET.

              Rob

              "Scott M." <s-mar@badspamsnet .net> wrote in message
              news:uD0ei$2bDH A.616@TK2MSFTNG P11.phx.gbl...[color=blue]
              > That's true, but you can't create the COM component using .NET. You can
              > only call it from within a .NET app or you can wrap a .NET assembly in a[/color]
              CCW[color=blue]
              > to use in a COM app. But, you can't actually create a COM app in .NET.
              >
              >
              > "Rob Windsor" <rwindsor@NO.MO RE.SPAM.bigfoot .com> wrote in message
              > news:%23NrY731b DHA.3748@TK2MSF TNGP11.phx.gbl. ..[color=green]
              > > Actually you can create COM components using .NET, or at least using[/color]
              > VB.NET[color=green]
              > > and C#, I'm not sure about other languages. COM Interop works both ways,[/color]
              > you[color=green]
              > > can use TLBIMP to create a runtime callable (RCW) so that .NET can use a[/color]
              > COM[color=green]
              > > component or you can use TLBEXP to create a COM callable wrapper (CCW)[/color][/color]
              so[color=blue][color=green]
              > > that COM enabled applications can use you .NET component.
              > >
              > > One resource that describes this in detail is "Profession al Visual Basic
              > > Interoperabilit y" by Lhotka and Hollis (WROX).
              > >
              > > ---
              > > Rob Windsor
              > > G6 Consulting
              > > Toronto, Canada
              > >
              > >
              > >
              > > "Scott M." <s-mar@badspamsnet .net> wrote in message
              > > news:%235dB2Nzb DHA.1872@TK2MSF TNGP12.phx.gbl. ..[color=darkred]
              > > > You can't develop COM applications in the .NET Framework.
              > > >
              > > > You can CALL a COM component and use it within a .NET application, but[/color]
              > > this[color=darkred]
              > > > usually creates a performance hit, since the .NET Framework will have[/color][/color][/color]
              to[color=blue][color=green][color=darkred]
              > > > create a runtime callable wrapper class around your COM object.
              > > >
              > > >
              > > > "Bryan Gan" <gcy80@yahoo.co m> wrote in message
              > > > news:084e01c36c 6e$46d8edd0$a50 1280a@phx.gbl.. .
              > > > > Dear all,
              > > > >
              > > > > Can I know is there any improvement if develop COM
              > > > > under .NET comparing to develop COM using VC6?
              > > > >
              > > > > thanks.
              > > >
              > > >[/color]
              > >
              > >[/color]
              >
              >[/color]


                Comment

                • Mr.Tickle
                  #5
                  Re: COM issue under .NET

                  Is it possible to call CORBA stuff from .NET as standard or must I use some
                  other 3rd party libraries.


                  "Rob Windsor" <rwindsor@NO.MO RE.SPAM.bigfoot .com> wrote in message
                  news:#4Vghy5bDH A.748@TK2MSFTNG P10.phx.gbl...[color=blue]
                  > Hi Scott,
                  >
                  > OK, I see what you're saying now. You're right, you can't do it natively[/color]
                  in[color=blue]
                  > .NET.
                  >
                  > Rob
                  >
                  > "Scott M." <s-mar@badspamsnet .net> wrote in message
                  > news:uD0ei$2bDH A.616@TK2MSFTNG P11.phx.gbl...[color=green]
                  > > That's true, but you can't create the COM component using .NET. You can
                  > > only call it from within a .NET app or you can wrap a .NET assembly in a[/color]
                  > CCW[color=green]
                  > > to use in a COM app. But, you can't actually create a COM app in .NET.
                  > >
                  > >
                  > > "Rob Windsor" <rwindsor@NO.MO RE.SPAM.bigfoot .com> wrote in message
                  > > news:%23NrY731b DHA.3748@TK2MSF TNGP11.phx.gbl. ..[color=darkred]
                  > > > Actually you can create COM components using .NET, or at least using[/color]
                  > > VB.NET[color=darkred]
                  > > > and C#, I'm not sure about other languages. COM Interop works both[/color][/color][/color]
                  ways,[color=blue][color=green]
                  > > you[color=darkred]
                  > > > can use TLBIMP to create a runtime callable (RCW) so that .NET can use[/color][/color][/color]
                  a[color=blue][color=green]
                  > > COM[color=darkred]
                  > > > component or you can use TLBEXP to create a COM callable wrapper (CCW)[/color][/color]
                  > so[color=green][color=darkred]
                  > > > that COM enabled applications can use you .NET component.
                  > > >
                  > > > One resource that describes this in detail is "Profession al Visual[/color][/color][/color]
                  Basic[color=blue][color=green][color=darkred]
                  > > > Interoperabilit y" by Lhotka and Hollis (WROX).
                  > > >
                  > > > ---
                  > > > Rob Windsor
                  > > > G6 Consulting
                  > > > Toronto, Canada
                  > > >
                  > > >
                  > > >
                  > > > "Scott M." <s-mar@badspamsnet .net> wrote in message
                  > > > news:%235dB2Nzb DHA.1872@TK2MSF TNGP12.phx.gbl. ..
                  > > > > You can't develop COM applications in the .NET Framework.
                  > > > >
                  > > > > You can CALL a COM component and use it within a .NET application,[/color][/color][/color]
                  but[color=blue][color=green][color=darkred]
                  > > > this
                  > > > > usually creates a performance hit, since the .NET Framework will[/color][/color][/color]
                  have[color=blue]
                  > to[color=green][color=darkred]
                  > > > > create a runtime callable wrapper class around your COM object.
                  > > > >
                  > > > >
                  > > > > "Bryan Gan" <gcy80@yahoo.co m> wrote in message
                  > > > > news:084e01c36c 6e$46d8edd0$a50 1280a@phx.gbl.. .
                  > > > > > Dear all,
                  > > > > >
                  > > > > > Can I know is there any improvement if develop COM
                  > > > > > under .NET comparing to develop COM using VC6?
                  > > > > >
                  > > > > > thanks.
                  > > > >
                  > > > >
                  > > >
                  > > >[/color]
                  > >
                  > >[/color]
                  >
                  >[/color]


                    Comment

                    • Daniel O'Connell
                      #6
                      Re: COM issue under .NET

                      "Mr.Tickle" <MrTickle@mrmen .com> wrote in message
                      news:u0oE245bDH A.724@tk2msftng p13.phx.gbl...[color=blue]
                      > Is it possible to call CORBA stuff from .NET as standard or must I use[/color]
                      some[color=blue]
                      > other 3rd party libraries.
                      >
                      >[/color]
                      I think it can currently only be done via third party libraries.
                      From what I've read borlands C# builder provides a CORBA library, Mono
                      provides a CORBA library, and there is an open source library[1](that I
                      believe mono either uses or based their CORBA support off of, but i'm not
                      sure and i'm too tired to look).
                      As i recall, the CORBA support in all cases is done using remoting.(i could
                      be wrong about borland's library)
                      I don't know if MS will ever support CORBA in the standard BCL, its
                      something i'd like to see, but...who knows.
                      COM is much more of an issue on the windows platform with application
                      integration, it had to be there v1.

                      1. that project can be located at http://remoting-corba.sourceforge.net/
                      [color=blue]
                      > "Rob Windsor" <rwindsor@NO.MO RE.SPAM.bigfoot .com> wrote in message
                      > news:#4Vghy5bDH A.748@TK2MSFTNG P10.phx.gbl...[color=green]
                      > > Hi Scott,
                      > >
                      > > OK, I see what you're saying now. You're right, you can't do it natively[/color]
                      > in[color=green]
                      > > .NET.
                      > >
                      > > Rob
                      > >
                      > > "Scott M." <s-mar@badspamsnet .net> wrote in message
                      > > news:uD0ei$2bDH A.616@TK2MSFTNG P11.phx.gbl...[color=darkred]
                      > > > That's true, but you can't create the COM component using .NET. You[/color][/color][/color]
                      can[color=blue][color=green][color=darkred]
                      > > > only call it from within a .NET app or you can wrap a .NET assembly in[/color][/color][/color]
                      a[color=blue][color=green]
                      > > CCW[color=darkred]
                      > > > to use in a COM app. But, you can't actually create a COM app in[/color][/color][/color]
                      ..NET.[color=blue][color=green][color=darkred]
                      > > >
                      > > >
                      > > > "Rob Windsor" <rwindsor@NO.MO RE.SPAM.bigfoot .com> wrote in message
                      > > > news:%23NrY731b DHA.3748@TK2MSF TNGP11.phx.gbl. ..
                      > > > > Actually you can create COM components using .NET, or at least using
                      > > > VB.NET
                      > > > > and C#, I'm not sure about other languages. COM Interop works both[/color][/color]
                      > ways,[color=green][color=darkred]
                      > > > you
                      > > > > can use TLBIMP to create a runtime callable (RCW) so that .NET can[/color][/color][/color]
                      use[color=blue]
                      > a[color=green][color=darkred]
                      > > > COM
                      > > > > component or you can use TLBEXP to create a COM callable wrapper[/color][/color][/color]
                      (CCW)[color=blue][color=green]
                      > > so[color=darkred]
                      > > > > that COM enabled applications can use you .NET component.
                      > > > >
                      > > > > One resource that describes this in detail is "Profession al Visual[/color][/color]
                      > Basic[color=green][color=darkred]
                      > > > > Interoperabilit y" by Lhotka and Hollis (WROX).
                      > > > >
                      > > > > ---
                      > > > > Rob Windsor
                      > > > > G6 Consulting
                      > > > > Toronto, Canada
                      > > > >
                      > > > >
                      > > > >
                      > > > > "Scott M." <s-mar@badspamsnet .net> wrote in message
                      > > > > news:%235dB2Nzb DHA.1872@TK2MSF TNGP12.phx.gbl. ..
                      > > > > > You can't develop COM applications in the .NET Framework.
                      > > > > >
                      > > > > > You can CALL a COM component and use it within a .NET application,[/color][/color]
                      > but[color=green][color=darkred]
                      > > > > this
                      > > > > > usually creates a performance hit, since the .NET Framework will[/color][/color]
                      > have[color=green]
                      > > to[color=darkred]
                      > > > > > create a runtime callable wrapper class around your COM object.
                      > > > > >
                      > > > > >
                      > > > > > "Bryan Gan" <gcy80@yahoo.co m> wrote in message
                      > > > > > news:084e01c36c 6e$46d8edd0$a50 1280a@phx.gbl.. .
                      > > > > > > Dear all,
                      > > > > > >
                      > > > > > > Can I know is there any improvement if develop COM
                      > > > > > > under .NET comparing to develop COM using VC6?
                      > > > > > >
                      > > > > > > thanks.
                      > > > > >
                      > > > > >
                      > > > >
                      > > > >
                      > > >
                      > > >[/color]
                      > >
                      > >[/color]
                      >
                      >[/color]


                        Comment

                        • Christian Wüsthoff
                          #7
                          Re: COM issue under .NET

                          "Daniel O'Connell" <onyxkirx@comca st.net> wrote in message news:<CSj4b.234 084$cF.76426@rw crnsc53>...[color=blue]
                          > "Mr.Tickle" <MrTickle@mrmen .com> wrote in message
                          > news:u0oE245bDH A.724@tk2msftng p13.phx.gbl...[color=green]
                          > > Is it possible to call CORBA stuff from .NET as standard or must I use[/color]
                          > some[color=green]
                          > > other 3rd party libraries.
                          > >
                          > >[/color]
                          > I think it can currently only be done via third party libraries.
                          > From what I've read borlands C# builder provides a CORBA library, Mono
                          > provides a CORBA library, and there is an open source library[1](that I
                          > believe mono either uses or based their CORBA support off of, but i'm not
                          > sure and i'm too tired to look).
                          > As i recall, the CORBA support in all cases is done using remoting.(i could
                          > be wrong about borland's library)[/color]

                          MiddTec provides a C# Object Request Broker: http://www.middtec.com.

                            Comment

                            Previous template Next
                            Working...