468,242 Members | 1,655 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

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

Publisher Policy Files / Versioning Problems

I have component A that references component B and component B uses
versioning and publisher policy files. Component A also references
component C and component C also references component B. A was
compiled against version 1.0.0.1 for component B and C was referenced
against version 1.0.0.0 for component B.

Now when A calls functionality within component C that in turn calls
component B I get an error ("component B or one of it's dependencies
not found"). If I go into my GAC, component B is very obviously there
(version 1.0.0.1) with a policy file dll that redirects to version
1.0.0.1. I do not have version 1.0.0.0 in my GAC but from what I
understood I shouldn't need to.

However, if I add version 1.0.0.0 to my GAC, then when A calls C
again, it works. Does anyone know why this is? This seems to
directly contradict how publisher policy files are supposed to behave.
Nov 22 '05 #1
0 1170

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Timothy M Hodgson | last post: by
reply views Thread by SH | last post: by
reply views Thread by andrew.noel | last post: by
reply views Thread by Python_it | last post: by
1 post views Thread by cmrchs | last post: by
1 post views Thread by =?Utf-8?B?U2NvdHQ=?= | last post: by
reply views Thread by NPC403 | last post: by
reply views Thread by kermitthefrogpy | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.