I was just wondering if there was a reason that the PresentationCore and System.Printing Dlls were set to be copied to the application bin folders for the CSLA 3.0 framework. The reason I ask is because they are in the GAC from the .NET 3.0 framework, and when I tried to publish my web app from my x86 development machine to my x64 web server, I got version issues with those files because they were copied into the bin folder. I removed them from the bin folder to use the gac versions and everything appears to be ok, but is there something that I am overlooking?
Thanks,
Mike
Visual Studio, by default, sets copy local to true on PresentationCore. System.Printing.dll comes along for the ride with another .NET 3.0 assembly.
It appears, but I'm not completely sure, that Microsoft messed up here, and that you can set copy local to false on PresentationCore. It also appears that getting rid of System.Printing.dll requires that you explicitly reference System.Printing.dll and set copy local to false.
On the other hand, Microsoft maybe does have a good reason for having copy local set to true - and it is under that assumption that I left the value as the default...
In my limited testing it does appear that preventing the local copy causes no issue though.
Copyright (c) Marimer LLC