Sprache Conflict?
See original GitHub issueHello,
I just installed EasyNetQ via nuget and am running into a conflict. I am already using the Sprache library in my project and now the compiler is complaining because there are now two instances of the type Sprache.Parser (one from Sprache’s nuget package, the other from EasyNetQ’s nuget package).
This is the error I am getting:
LotNumberParser.cs(12, 24): [CS0433] The type 'Parser<T>' exists in both 'EasyNetQ, Version=3.4.5.0, Culture=neutral, PublicKeyToken=null' and 'Sprache, Version=2.2.0.0, Culture=neutral, PublicKeyToken=null'
Is there something I can do here to make this work?
Thanks, Paul
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
European Pluricentric Languages in Contact and Conflict ...
Amazon.com: European Pluricentric Languages in Contact and Conflict (Österreichisches Deutsch – Sprache der Gegenwart): 9783631802977: Muhr: Books.
Read more >European Pluricentric Languages in Contact and Conflict
This volume comprises 17 papers that are dealing with European pluricentric languages where there are some issues of contact and conflict.
Read more >Language conflicts in the European Union - Ammon - 2006
This contribution presents the conflict of interests between the smaller and the larger language communities in having only one or several ...
Read more >Language and End Time (Sections I, IV and V of 'Sprache und ...
'Language and End Time' is a translation of Sections I, IV and V of 'Sprache und Endzeit', a substantial essay by Günther Anders...
Read more >Language Settings - Bug Reports & Issues
Hi all! Im from Brasil, but I like to play at english language interface. I can change language at start screen, where the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you! I appreciate you looking into it!
Fixed by #935 in 3.5.0.