Uploaded image for project: 'NPanday'
  1. NPanday
  2. NPANDAY-636

Support .Net4 Additional option "Embed Com Interop" to ArtifactType.COM_REFERENCE

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.5.0-incubating
    • None
    • None

    Description

      Visual studio makes available when compiling a .NetFramework 4 module, for references that are Interop/com a new option "Embed Interop Types".

      This option swaps between using /reference to /link and also manages Copy Local where an embedded /link[ed] item doesn't need to be copied to the output location.

      About embedded Interop types Vs Primary Interop Assemblies (PIA)
      Where MS suggest

      About compilation
      http://msdn.microsoft.com/en-us/library/538aes2a%28v=vs.110%29.aspx
      http://msdn.microsoft.com/en-us/library/dd264728(v=vs.110).aspx

      My understanding is that these Interop modules are not attached/kept as output for maven, rather rebuilt in downstream as necessary.
      It seems that if not embedding, then it is more appropriate to have the Interop as a seperate module. Makes me wonder if COM_REFERENCE is an appropriate dependency if not embedding, could COM_REFERENCE imply embedding?

      Attachments

        Activity

          People

            Unassigned Unassigned
            gdomjan Greg Domjan
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: