System.Drawing.StringAlignment in TeeChart.Pocket.Dll
Posted: Wed May 31, 2006 7:01 pm
Hello,
I am experiencing some problems with a name conflict with System.Drawing.StringAlignment where this class can be found in both System.Drawing.dll and TeeChart.Pocket.Dll when I include the TeeChart DLL in my project.
I get the following compile-time error:
The type 'System.Drawing.StringAlignment' exists in both 'c:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Drawing.dll' and '<The path where I placed the dlls>\TeeChart.Pocket.dll'.
I was wondering if you had a fix or a way to work around this conflict.
Please note that when I use the TeeChart.Pocket.Dll from the Evaluation package, I do not get this problem. Also note that I have both TeeChart for .NET v2 2005 & TeeChart for .NET v2 2003 installed on the same machine. I installed both because we are building two flavors of our application with two separate solutions (one with .NET 1.1 and another one with .NET 2.0). The conflict occures with the 2005 version.
Thank you in advance for your help,
Yannick
I am experiencing some problems with a name conflict with System.Drawing.StringAlignment where this class can be found in both System.Drawing.dll and TeeChart.Pocket.Dll when I include the TeeChart DLL in my project.
I get the following compile-time error:
The type 'System.Drawing.StringAlignment' exists in both 'c:\Program Files\Microsoft Visual Studio 8\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\System.Drawing.dll' and '<The path where I placed the dlls>\TeeChart.Pocket.dll'.
I was wondering if you had a fix or a way to work around this conflict.
Please note that when I use the TeeChart.Pocket.Dll from the Evaluation package, I do not get this problem. Also note that I have both TeeChart for .NET v2 2005 & TeeChart for .NET v2 2003 installed on the same machine. I installed both because we are building two flavors of our application with two separate solutions (one with .NET 1.1 and another one with .NET 2.0). The conflict occures with the 2005 version.
Thank you in advance for your help,
Yannick