> 3. The config file is the one which MSDN recommends > ms-help://MS.VSCC.2003/MS.MSDNQTR.2003APR.1033/cpguide/html/cp > contargetingne > tframeworkversion.htm >
That page documents how to target a different version of the runtime (1.0 v. 1.1). Or are you just saying you followed the syntax used for the binding redirects as an example? Since your build command line looks correct, and contrary to what you're saying about the config file being correct, I'd still like to see what your key is (show us the exact output of "sn -Tp pubsassembly.dll" on your 'code' assembly, not the publisher one) and the contents of the config file you're embedding in the publisher policy assembly. The config file you're embedding in the publisher policy assembly should have a single binding redirect in it, that reroutes assemblies with your public key from version A to version B. If you didn't already, please grab my sample here [1] and follow that lead. It's a bare bones example. Just be sure to use your own key tokens, versions, and assembly names instead of the ones in my sample. -Mike DevelopMentor http://staff.develop.com/woodring [1] http://staff.develop.com/woodring/dotnet/#PublisherPolicySample
