Properties.Settings Ambiguity after adding LINQ to SQL
Posted
by Emmanuel Smith
on Stack Overflow
See other posts from Stack Overflow
or by Emmanuel Smith
Published on 2010-06-11T14:20:59Z
Indexed on
2010/06/11
14:22 UTC
Read the original article
Hit count: 452
I have recently linked a database to my C# service by creating a LINQ to SQL item in my solution. Everything was fine and dandy as I was continuing to code, but then I suddenly noticed that there where 16 Ambiguity errors. e.g.
Ambiguity between 'EmailService.Properties.Settings.defaultInstance' and 'EmailService.Properties.Settings.defaultInstance'
What happened was that the database file decided to create it's own Setting.Designer.cs; So now I have a Settings.Designer.cs and a Settings1.Designer.cs (which was created by the LINQ to SQL file) in my Properties folder.
Is there anyway that I can change where the database file is referencing its settings so I can delete the duplicate?
© Stack Overflow or respective owner