VB.net using complied Dll gives ambiguous between declarations in Modules

Question

2.00/5 (1 vote)

See more:

Im hoping someone has come across this before

I have a compiled VB.net 2008 Dll which works fine, I use standard blocks of code for all of my projects including the dll.

When I create a new app and import the Dll I get the following error when checking contents of some variables.

"g_DataFile' is ambiguous between declarations in Modules localApp and CompiledApp"

I understand that it is a clash between variables and only occurs when I try to use the immediate window to show the variable contents. But I would like to hide the vars in the dll but the compiled dll seem to be expose them.

Any help would be appreciated

Thanks

Posted 20-Jan-15 6:34am

derekbeacroft

Add a Solution

Comments

Sergey Alexandrovich Kryukov 20-Jan-15 12:55pm

Absolutely every name clash is resolvable. First are the type names 100% identical, or namespaces are different. The resolution can be done even of full names are identical, which is just a tiny bit more difficult.
—SA

derekbeacroft 21-Jan-15 5:51am

Ahh Namespaces, I come from 12yrs vb6 and 2 yr .Net so not so great on namespaces
my dll uses a RootNamespace of "UserSecurity"

My app uses a Rootnamespace of "QuotesApplication"

in my app I add "Imports UserSecurity"

Not really sure how to resolve it though, the vars are public in the module Code, should I move them elsewhere ??

Dez

Sergey Alexandrovich Kryukov 21-Jan-15 11:29am

This is irrelevant. I'm not asking what you added, what you used and what are your namespaces, I am asking full names of clashing types, are they 100% identical or not. On cannot be "so great on namespaces" or not "great". You just know them or not. If not, you are not doing programing in .NET. Not at all, nothing to bother about, nothing to talk about. Learn it and come back. I just don't want to confuse you with more difficult cases, when the names are exactly the same.
—SA

derekbeacroft 21-Jan-15 11:40am

Well that's a useful comment, I hope some of the other people on this forum are a little more helpful.

"Learn it and come back"

Why do you think this forum exists ?

But thanks for your comments no mater how unhelp full you are.

Sergey Alexandrovich Kryukov 21-Jan-15 11:56am

Hm. I see you are frustrated. Sorry. But then answer our questions, it's way to easy.
Forum exist for people qualified to ask questions and use the help. Everything has its prerequisite. You cannot hope for help if you don't know the terms to discuss the matters.
But of course, if it was just misunderstanding, I'll gladly admit my fault and apologize.

So, all you need is to find out the declarations of "g_DataFile". You have at least two, in different places. This should be fine, but then you need to find out how are they different. Full type name in one case, full type name in another case. They can be both defined in your code, one can be in one library, both in some libraries you are trying to use, and so on. Two clashing full names. I just asked not the names, but if they are identical or not.

Is that clearer, or..?

—SA

derekbeacroft 21-Jan-15 12:38pm

Ok I will try again.

I have the same .vb code module used in two places
the g_Datafile is defined as a global public in the top of the dll Module code
eg.
Module Soft_Routines
Public g_DataFile As String

and again it appears identically in my normal app

Module Soft_Routines
Public g_DataFile As String

my declaration is Public which I assume is affecting the way it is addressable from my dll to other apps, if I remove the imports UserSecurity the clash is removed.

I understand the referencing and what imports achieves, im having problems with the scope of the variable within the application and how to keep the functionality of a global within the dll but hidden from other apps.

it may be my declaration needs to change or move them into a private module

I should note the application compiles and runs fine g_DataFile also functions as expected, its just using it in the immediate window I have issues where the error appears an only in the module that has the imports statement (obviously referring to the dll with clashing names).

Sergey Alexandrovich Kryukov 21-Jan-15 14:40pm

(Sigh.)
You are not addressing the real issue.
You need to present the following:
assembly: "blah-blah"
declares a.b.c.g_DataFile
and
a2.b.c.g_DataFile
assembly: "another one" (if any)
declared c.d.e.g_DataFile.
That's all.

I cannot advise you to write full name, because this is instance member, it should be accessed as
a.g_DataFile, where "a" is some instance of the declaring class, not class. And that "a" also depends on scope. And so on. Perhaps you only need to understand the principles.

—SA

Kenneth Haugland 20-Jan-15 13:29pm

Has happen to me before, but I ditched the project, hopefully you don't have to. :)

derekbeacroft 22-Jan-15 7:25am

Another late night

I have added a new assembly name “ASM” to the exposed dll class functions which now means that all declared vars within the new assembly use normal calling convention eg “ANotherVar” but classes and Modules outside must use the new assembly name “ASM.ANotherVar” to access them within the same dll Project.

My Imports statement now “UserSecurity.ASM” allows access to the class functions.
The local application calls its local variable ok and do not cross the assembly boundary into ASM namespace. (good!)

So far this seems to work

Im guessing my full namespace for the UserSecurity Dll is now "UserSecurity.ASM"
Giving access to "UserSecurity.ASM.Class.myfunctions"

By using Imports "UserSecurity.ASM" I can now call "Class.myfunctions" and I don't get the old problem

Is this going in the right direction ??

Ps
Asking for help is a sign of accepting others know more than myself !

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)