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. General Programming
  3. .NET (Core and Framework)
  4. TypeLib for interop assembly changes case of method name

TypeLib for interop assembly changes case of method name

Scheduled Pinned Locked Moved .NET (Core and Framework)
comhelpquestion
1 Posts 1 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.
  • T Offline
    T Offline
    turbochimp
    wrote on last edited by
    #1

    I have a scenario similar to the following: Assume a single assembly (SomeAssembly.dll) contains the following types: 1. Class B inherits from class A 2. Class A implements properties Moe, Larry and Curly, all of type ArrayList. 3. Class B implements a public interface containing all of the public members of both classes A and B. The problem: I export the type library for SomeAssembly.dll using

    Regasm.exe SomeAssembly.dll /tlb:SomeAssembly.tlb /codebase
    

    When I view the generated type library, I see that while properties Moe and Larry appear as "Moe" and "Larry" (their proper case is preserved), property Curly is exported as "curly" (all lower case). So far, I haven't been able to find an explanation for this behavior, and while the CCW works just fine, the name change is a little disconcerting for my client. The only similar article I was able to find referenced a known issue whereby if there was another "curly" property that was written to the type library first, all following same-named properties would bear the lowercase name, but there is only one "Curly" property in my assembly. Any ideas? Failing a solution, is there any attribute decoration I might use to force the proper case in the generated type library? Thanks.

    The most exciting phrase to hear in science, the one that heralds the most discoveries, is not 'Eureka!' ('I found it!') but 'That's funny...’

    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