NTA

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Dave

    #1

    NTA

    How is a .NET Serviced Component marked as NTA?
    Currently, I'm only getting STA.
  • Perry Deng

    #2
    RE: NTA

    Hi Dave,

    Thanks for contacting Microsoft Community Support. I am performing research
    on the issue and will paste here with my findings.

    Best regards,
    Perry Deng
    Microsoft

    This posting is provided "AS IS" with no warranties, and confers no rights.

    Comment

    • Perry Deng

      #3
      RE: NTA

      Hi Dave,

      Thanks for contacting Microsoft Community Support. I am performing research
      on the issue and will paste here with my findings.

      Best regards,
      Perry Deng
      Microsoft

      This posting is provided "AS IS" with no warranties, and confers no rights.

      Comment

      • Perry Deng

        #4
        RE: NTA

        Managed objects that are exposed to COM behave as if they had aggregated
        the free-threaded marshaler. In other words, they can be called from any
        COM apartment in a free-threaded manner. An context Agile .NET component
        (those that do not extend from ContextBoundObj ect) are analogous to
        thread-neutral COM objects that aggregate the free-threaded marshaler. The
        only managed objects that do not exhibit this free-threaded behavior are
        those objects that derive from ServicedCompone nt. Objects that derive from
        ServicedCompone nt currently behave more like normal COM objects and live
        inside OLE32 contexts and apartments.

        Best regards,
        Perry Deng
        Microsoft

        This posting is provided "AS IS" with no warranties, and confers no rights

        Comment

        • Perry Deng

          #5
          RE: NTA

          Managed objects that are exposed to COM behave as if they had aggregated
          the free-threaded marshaler. In other words, they can be called from any
          COM apartment in a free-threaded manner. An context Agile .NET component
          (those that do not extend from ContextBoundObj ect) are analogous to
          thread-neutral COM objects that aggregate the free-threaded marshaler. The
          only managed objects that do not exhibit this free-threaded behavior are
          those objects that derive from ServicedCompone nt. Objects that derive from
          ServicedCompone nt currently behave more like normal COM objects and live
          inside OLE32 contexts and apartments.

          Best regards,
          Perry Deng
          Microsoft

          This posting is provided "AS IS" with no warranties, and confers no rights

          Comment

          Working...