Hi, Here is the info u wanted :
1. If my assembly is >>pubsassembly.dll<< then my policy is >>pubsassembly.dll.config<< and when I attempted to install it in GAC I named the policy dll >>policy.1.0.pubsassembly.dll<< 2. Command Line : al.exe /link:PubsAssembly.dll.config /out:policy.1.0.PubsAssembly.dll /keyf:pkey.snk /v:1.0.0.1 3. The config file is the one which MSDN recommends ms-help://MS.VSCC.2003/MS.MSDNQTR.2003APR.1033/cpguide/html/cpcontargetingne tframeworkversion.htm 4. MSDN's config file is perfectly alright because it works for me for my VB6Client.EXE - Thanks in advance Nishant Pant -----Original Message----- From: Ian Griffiths [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 4:06 AM To: [EMAIL PROTECTED] Subject: Re: [ADVANCED-DOTNET] Sie By Side Assembly Versions -anyone a clu e how to solve type identity problems? What filename are you giving to the publisher policy assembly? (You are creating a publisher policy assembly and not just a publisher policy file, right?) Rather than just exclaiming "DIDN'T WORK" without providing details, can you do of the following: (1) Tell us the name of the assembly you're trying to write a publisher policy for (2) Show us the publisher policy file you've written (3) Show us the command line you used to build the publisher policy assembly I've done this many times and it's always worked, but you do have to follow all of the steps in the "Creating a Publisher Policy File" help item in the .NET Framework Developer's Guide. If you miss anything out, it's not going to work. -- Ian Griffiths DevelopMentor ----- Original Message ----- From: "Pant, Nishant" <[EMAIL PROTECTED]> > Even I am stuck with this for days now. > I am doing everything according to the book. I tried doing the > following things : > > 1. creating a config file for my local assembly first -DIDN'T WORK 2. > creating a policy dll out of the config and installing both > assembly/policy in GAC - DIDN'T WORK 3. installing just he policy in > GAC - Didn't work 4. renamed the same config for the client exe. Eg. > VB6Client.EXE.Config - WORKED!!! > > Of course, this is not what I wanted ....what I wanted was the policy > for the assembly not the client exe. > > - Regards > Nishant Pant > > > > -----Original Message----- > From: Luca Minudel [mailto:[EMAIL PROTECTED] > > Mike Woodring (DevelopMentor) wrote: > > >> Do publisher policies only work with assemblies installed within > >> the GAC? > > > >Correct. > > > > I think to remember that the assembly must be strong named but it can > be out > of the GAC while the Publisher Policy Assembly must be in the GAC. > > Isn't it???
