Bug 11144 - System.Data classes not recognized after added reference and using statement
Summary: System.Data classes not recognized after added reference and using statement
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-03-13 21:32 UTC by palmern22
Modified: 2015-08-25 07:28 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description palmern22 2013-03-13 21:32:00 UTC
Description of Problem:


Steps to reproduce the problem:
1. Add System.Data Reference
2. Add Mono.Data.Sqllite
3. Add Appropriate Using Statements
4. Access classes from either namespace


Actual Results:
 No Code hints or code completion. Classes are colored red(not found) But still builds

Expected Results:
 Code hints and code completions. Recognized symbols

How often does this happen? 
 When First adding the reference and using statements.

Additional Information: I have a business license, when I restart xamarin, it seems to resolve.
Comment 1 Lluis Sanchez 2015-08-25 06:59:05 UTC
Is this still an issue?
Comment 2 palmern22 2015-08-25 07:28:53 UTC
Huzzah two years and I finally hear back from support!


The problem was a license issue as you no doubt have figured out. 

Thanks for checking in however. I can't imagine the size of your backlog!

Best Regards,

Nate