470,602 Members | 1,512 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,602 developers. It's quick & easy.

Can't remove old version of external assembly

I'm having a problem with being unable to remove a
reference to an old, nonexistent version of a strongly-
named assembly.

I should mention that my issues arose at the same time I
upgraded from v 1.0.3705 to v 1.1.4322 of the framework
(and to the 2003 IDE); I've been recompiling old 1.0
components.

I had created the assembly and installed in the GAC with a
version # of 1.0.0.2. This assembly, DBParameter, was used
by a serviced component. I uninstalled from the GAC and
created a new version, now up to 1.0.1.4.

The problem is, my components referencing this assembly
refuse to give up the old assembly reference to version
1.0.0.2 -- even though it's been long gone from my box and
the GAC.

What's happening is my manifests are showing a reference
to the new DBParameter, but also to the old one, with an
alias, like so:

..assembly extern DBParameter
{
.publickeytoken = (E9 B4 14 50 D7 FC 48
40 ) // ...P..H@
.ver 1:0:1:4
}
..assembly extern DBParameter as DBParameter_7
{
.publickeytoken = (F7 01 A2 50 74 2F 79
FE ) // ...Pt/y.
.ver 1:0:0:2
}
No matter what I do, I can't get rid of this old assembly
reference. I've used a brand new key file to compile the
new version, yet my apps using this assembly insist on
looking for the old one too (and of course the public key
token is long gone).

Any suggestions on how to break this dependency? I am in
assembly hell ....

TIA,
Paul Klanderud
Jul 19 '05 #1
1 2917
I found the solution to my own problem. One of the other
assemblies my app referenced had an old reference to the
old version -- I thought I had recompiled it, but hadn't.

Paul

-----Original Message-----
I'm having a problem with being unable to remove a
reference to an old, nonexistent version of a strongly-
named assembly.

I should mention that my issues arose at the same time I
upgraded from v 1.0.3705 to v 1.1.4322 of the framework
(and to the 2003 IDE); I've been recompiling old 1.0
components.

I had created the assembly and installed in the GAC with aversion # of 1.0.0.2. This assembly, DBParameter, was usedby a serviced component. I uninstalled from the GAC and
created a new version, now up to 1.0.1.4.

The problem is, my components referencing this assembly
refuse to give up the old assembly reference to version
1.0.0.2 -- even though it's been long gone from my box andthe GAC.

What's happening is my manifests are showing a reference
to the new DBParameter, but also to the old one, with an
alias, like so:

..assembly extern DBParameter
{
.publickeytoken = (E9 B4 14 50 D7 FC 48
40 ) // ...P..H@
.ver 1:0:1:4
}
..assembly extern DBParameter as DBParameter_7
{
.publickeytoken = (F7 01 A2 50 74 2F 79
FE ) // ...Pt/y.
.ver 1:0:0:2
}
No matter what I do, I can't get rid of this old assembly
reference. I've used a brand new key file to compile the
new version, yet my apps using this assembly insist on
looking for the old one too (and of course the public key
token is long gone).

Any suggestions on how to break this dependency? I am in
assembly hell ....

TIA,
Paul Klanderud
.

Jul 19 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by tvaidie | last post: by
3 posts views Thread by Paul Klanderud | last post: by
11 posts views Thread by cybervigilante | last post: by
2 posts views Thread by =?Utf-8?B?Unlhbg==?= | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.