publisher policy in .NET 2.0 ???

cmrchs

Hi,

I'm having problems using publisher policy in .NET 2.0.
whereas I didn't in .NET 1.1

Scenario :
I have a version3.0 component against which a client is compiled.
Then creating version3.1 component and the policy-file.
(The policy-file states a binding-redirect from 3.0 to 3.1.)

I install both the policy-file and 3.1-component in the GAC, then run the client again but I get an error stating that the client doesn't find 3.1-component ???

I repeat : .NET 1.1, I didn't have any problems

Summary:
If I compile the client directly against 3.0-component then no problem
If I compile the client directly against 3.1-component then no problem
If I compile the client against 3.0-component but with the
policy-file in the GAC then crash
And i have verified the correctness of the policy-file !!!

What is wrong then ?
What has changed in .NET 2.0 ?

thanks
Chris
*************** *************** *************** *************** **********
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

Nov 17 '05 #1

Subscribe Reply

1689

Peter van der Goes

"Chris C" <cm****@yahoo.c om> wrote in message
news:eX******** ******@TK2MSFTN GP14.phx.gbl...

Hi,

I'm having problems using publisher policy in .NET 2.0.
whereas I didn't in .NET 1.1

Scenario :
I have a version3.0 component against which a client is compiled.
Then creating version3.1 component and the policy-file.
(The policy-file states a binding-redirect from 3.0 to 3.1.)

I install both the policy-file and 3.1-component in the GAC, then run the
client again but I get an error stating that the client doesn't find
3.1-component ???

I repeat : .NET 1.1, I didn't have any problems

Summary:
If I compile the client directly against 3.0-component then no problem
If I compile the client directly against 3.1-component then no problem
If I compile the client against 3.0-component but with the
policy-file in the GAC then crash
And i have verified the correctness of the policy-file !!!

What is wrong then ?
What has changed in .NET 2.0 ?

thanks
Chris
*************** *************** *************** *************** **********
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP &
ASP.NET resources...

If you need to post an article in multiple groups, please crosspost instead
of multiposting.
If you don't get responses here, I suggest you search through/post in the
forums dedicated to the Beta:

http://forums.microsoft.com/msdn/
--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

Nov 17 '05 #2

Similar topics

7964

Publisher policy file is not found

by: Timothy M Hodgson | last post by:

In the Assembly Load Trace, the error: Publisher policy file is not found comes up. Is this a problem with locating the assembly? Is a publisher policy file required or even necessary as long as the assembly can be found and loaded? Thanks! Tim

.NET Framework

1176

Dependency error on component that uses publisher policy files

by: Doug | last post by:

Hello, We are having a problem with a component in our system that uses publisher policy files. Whenever it gets modified and moved out to where our build processes reference components for other builds, developers get this error: "The dependency 'COMPONENT, Version=VERSION, Culture=neutral, PublicKeyToken=PUBLIC KEY TOKEN' in project 'OTHER COMPONENT' cannot be copied to the run directory because it would conflict with dependency...

.NET Framework

407

Publisher Policy Files / Versioning Problems

by: Doug | last post by:

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...

.NET Framework

2034

How to automatically generate many publisher policies ?

by: Seb LM | last post by:

Hello, I'd like to define a publisher policy which covers many versions of assembly from which the "major.minor version" are different but it's not possible to make a such publisher policy. So it's necessary to create a publisher policy for each new "major.minor version", which can take a long time to make manually. Do there exist tools to generate publisher policy for many "major.minor versions" from a simple and compact configuration...

.NET Framework

1048

Installion of Publisher Policy

by: andrew.noel | last post by:

I have a publisher policy setup that consists of the following two files: policy.0.0.assembly.dll policy.config The policy.config file contains the following: <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">

.NET Framework

1987

Creating publisher policies for DLLs

by: MT | last post by:

We have a .NET dll that we are deploying to our customers using a deployment project in VS .NET 2003. There is a lot of information about creating publisher policies on the web, but we have not been successful in creating one. Here's what the ultimate goal is: When the DLL is deployed to a customer's system, every application using this dll must point to the new version. This has to be an automated process using the deployment project....