Bug 443133 - inconsistency between MD and VS.Net in regards to references with dependent dlls
Summary: inconsistency between MD and VS.Net in regards to references with dependent dlls
Status: RESOLVED FIXED
Alias: None
Product: Mono: Compilers
Classification: Mono
Component: C# (show other bugs)
Version: unspecified
Hardware: Other Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Marek Safar
QA Contact: Mono Bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-08 17:50 UTC by Scott Ellington
Modified: 2011-01-12 10:12 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Ellington 2008-11-08 17:50:25 UTC 
I have a project that uses the latest npgsql (2.0).  On MD, I add as a reference and it works fine, but on Visual Studio 2005, I get:

...You must add a reference to assembly 'System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'.

So on VS.NET, I must explicitly add a reference to System.Data.  It would be nice if it were consistent.
Comment 1 Lluis Sanchez 2009-02-13 01:11:05 UTC 
That's something that has to be detected by mcs. MD can't do much about it.
Comment 2 Andres Aragoneses 2009-02-13 05:10:18 UTC 
Dupe.

*** This bug has been marked as a duplicate of bug 376876 ***
Comment 3 Andres Aragoneses 2009-02-13 05:12:26 UTC 
Mmm, thinking it better, it's not exactly a dupe, but it's very related.
Comment 4 Marek Safar 2011-01-12 10:12:12 UTC 
Fixed in master