Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
'ExtensionAttribute' is ambiguous in the namespace 'System.Runtime.CompilerServices' RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    hi,

    Im using .net framework 2.0. recently i added the third party dll LINQBRIDGE.DLL in my project for implementing linq operations.

    now when i build the project im getting the below error:

    error bc30560  : 'ExtensionAttribute' is ambiguous in the namespace 'System.Runtime.CompilerServices'.

    i think the other projects are not compatible with this third party dll. please let me know how can i resolve this error when i add linqbridge.dll

    Friday, July 28, 2017 5:32 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Does the error message say which assemblies define ExtensionAttribute? If one of those assembles is built from a project of yours, then delete the definition of class ExtensionAttribute from that project and instead add a reference to LINQBRIDGE.DLL. Perhaps add a TypeForwardedToAttribute, as well.

    (In C#, one can sometimes solve ambiguity errors by giving one of the assemblies an extern alias. In the command-line C# compiler, that would be the /reference:alias=filename syntax. However, you seem to be using Visual Basic, and it looks like the /reference option of the Visual Basic compiler does not support anything similar.)

    Friday, July 28, 2017 6:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    No it didnt specify the assembly name
    Friday, July 28, 2017 7:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi umamaheshwaran ganesan,

    Based on your description and related error message, it seems that 3rd-party dll file cause the issue, I would suggest that you could connect the 3rd-party DLL author for suitable support.

    https://www.nuget.org/packages/LinqBridge/

    Thanks for your understanding.

    Best regards,

    Cole

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Monday, July 31, 2017 2:50 AM