Why is my SqliteConnection not found when I DO have the assembly reference AND the using clause?

Question

2.00/5 (1 vote)

See more:

I'm getting "The type or namespace name 'SqliteConnection' could not be found (are you missing a using directive or an assembly reference?)" on this line of code:

C#

using (SqliteConnection con = new SqliteConnection(HHSUtils.GetDBConnectionStrSite(paddedSiteNum))

...even though I have System.Data.SQLite in my project's References, and I've got:

C#

using System.Data.SQLite;
using System.Data.SQLite.Generic;

...in the source.

What gives? This is a Windows CE project in Visual Studio 2008.

Posted 30-Oct-14 13:37pm

B. Clay Shannon

Add a Solution

Comments

[no name] 30-Oct-14 19:54pm

Maybe before you completely overheat, try to right klick the error message and click something like "resolve bla bla"

If it does not help...it seems to be your Problem....

Your words: "Why is my SqliteConnection not found when I DO have the assembly reference AND the using clause?

*lol* is it really "your" SqliteConnection...seems not...better not shout to your developing environement and also not here. Otherwhise you get lost in the deep of your references :P

B. Clay Shannon 30-Oct-14 19:56pm

Yeah, I should have mentioned that I right-clicked "SqliteConnection" and there was no "Resolve" available.

[no name] 30-Oct-14 20:05pm

Thanks to take my "aggressive" comment that easy. Is it maybe CE env. which is not supporting your request?

Sergey Alexandrovich Kryukov 30-Oct-14 21:48pm

This is just case-sensitive thing; please see my answer.
—SA

PIEBALDconsult 30-Oct-14 20:19pm

Improper casing of the QL in SQLiteConnection
http://www.ivankristianto.com/howto-use-sqlite-ado-net-with-c/
A benefit I get by _not_ using using directives.
And I have to say. they shouldn't have their classes in the System namespace.

Sergey Alexandrovich Kryukov 30-Oct-14 21:49pm

Oh, I already posted the answer when I noticed this comment. All credit goes to you, I'll add the edit to my answer.

As to having namespace declarations based on "System", this is just a discussable point, not really related to the issue. I must say that using some existing namespaces by 3rd parties (or any different parties) is a common practice. I don't think this is a very principle concern.

—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-10-30T15:47:00

This is just because C# is case-sensitive, and correct name of the type is SQLiteConnection:
http://www.devart.com/dotconnect/sqlite/docs/Devart.Data.SQLite~Devart.Data.SQLite.SQLiteConnection.html[^].

By the way, the use of "using" clause is optional and does not really relate to the use of some assembly, which is defined by referencing it. It's just about the way you can name assembly-level types, no matter in what assembly; it equally apply to the same assembly, for example. The "using" clause just happens to shorten some names in use.

[EDIT]

Actually, all credit should go to PIEBALDconsult, who wrote nearly the same in his comment to the question; I just noticed that only after I already posted this answer.

—SA