Hi,
Thanks for your quickly reply!
This is a known issue, and I have reported it to our product team, but I
can not guarantee if it will be fixed in the next release of VS.NET.
The problem was caused by the fact that when you set the copylocal to true,
in the design time, the VS.NET IDE will not load the assembly from the GAC,
so even the two assemblied are the same binary files but their full
qulified name are not the same(i.e. the path is not the same). So that
there will be a mismatch which cause the problem. However in the runtime,
(i.e. Press Ctrl + F5 to run the winform app) we will not get the error
because the system.windows.forms.dll is loaded from the GAC.
For your concern about the internationlization, if the assembly is in the
GAC, I think we do not need to set the copylocal to true, since in the run
time, the CLR will try to load the assembly from the GAC first. As for the
other assembly which is not placed in the GAC, it is proper to set the
copylocal to true, which will help to make sure the application will load
the correct assembly.
For now, I suggest try to set the copylocal to false to workaround the
problem.
Here are some links.
How the Runtime Locates Assemblies
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/htm
l/cpconhowruntimelocatesassemblies.asp
CopyLocal Property (Reference Object)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vbcon/html/
vxlrfvslangprojreferencecopylocal.asp
Best regards,
Peter Huang
Microsoft Online Partner Support
Get Secure! -
www.microsoft.com/security This posting is provided "AS IS" with no warranties, and confers no rights.