By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
455,201 Members | 1,383 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 455,201 IT Pros & Developers. It's quick & easy.

Non-existing reference yet it compiles

P: n/a
Joe
I'm compiling a class library that includes references to 3 other libraries.
Every time the library compiles the 3 referenced libraries show in the
manifest as a different public key than I have on my machine.

I have checked my machine many times over to see if there are any other
copies with the public key that the library is being compiled with but
nothing turns up.

If I use ADepends to look at the resulting dll, the 3 referenced assemblies
show up in red.

What makes this even stranger is that this only happens with this one
library. I have another one that references the same assemblies and I can
compile either before or after this one and it always shows the correct
reference.

Is there something I'm missing? This is driving me crazy!

-Joe
Apr 5 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Joe
This is even more confusing now... I ran ildasm on the dll and all the
publickeys are correct but when I check the same dll with adepends it shows
an old non-existent public key.

Any ideas?
-Joe

"Joe" <jb*******@noemail.noemail> wrote in message
news:em**************@TK2MSFTNGP02.phx.gbl...
I'm compiling a class library that includes references to 3 other
libraries. Every time the library compiles the 3 referenced libraries show
in the manifest as a different public key than I have on my machine.

I have checked my machine many times over to see if there are any other
copies with the public key that the library is being compiled with but
nothing turns up.

If I use ADepends to look at the resulting dll, the 3 referenced
assemblies show up in red.

What makes this even stranger is that this only happens with this one
library. I have another one that references the same assemblies and I can
compile either before or after this one and it always shows the correct
reference.

Is there something I'm missing? This is driving me crazy!

-Joe

Apr 6 '06 #2

P: n/a
Hi Joe,

We haven't experienced such a strange scenario. It appears there is
something wrong with that particular class library.

Since you mentioned this problem only happens to that class library, have
you tried to remove those 3 assemblies references and then add them again?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Apr 6 '06 #3

P: n/a
Joe
Hi Gary,

I removed the references and re-added them. I also build the other libs
using a different name and tried adding them. Now it doesn't compile. I get
an error that it's trying to find the assemblies with the old name (name,
version, public key) even though I can't find a single reference to these in
the project.

I did a search on the folder that contains the files to see if any file was
referencing it anywhere but I can't find any.

The project was upgraded to VS.Net 2003 from 2002 it that helps at all.

Thanks for any help,
Joe

""Gary Chang[MSFT]"" <v-******@online.microsoft.com> wrote in message
news:9Z**************@TK2MSFTNGXA01.phx.gbl...
Hi Joe,

We haven't experienced such a strange scenario. It appears there is
something wrong with that particular class library.

Since you mentioned this problem only happens to that class library, have
you tried to remove those 3 assemblies references and then add them again?
Thanks!

Best regards,

Gary Chang
Microsoft Community Support
================================================== ====
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng06 when prompted. Once you have entered the
secure code mmpng06, you will be able to update your profile and access
the
partner newsgroups.
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.

Apr 11 '06 #4

P: n/a
Hi Joe,
The project was upgraded to VS.Net 2003 from 2002 it that helps at all.


Do you mean the problematic project is upgraded from VS2002?

If so, some reference link may be corrupted during the upgrading?
Thanks!

Best regards,

Gary Chang
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Apr 12 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.