GdPicture.NET V.11 .Net 4.0 Client Profile
Posted: Mon Feb 23, 2015 12:38 pm
Hi,
We tested your Product for our upcoming project. We used for these tests a trial Version of GdPicture.NET 10. This project must use .NET Framework 4.0 Client Profile.
As we were convinced of the component, we decided to buy it. Meanwhile, the version 11 was out, so we bought this version. Now, as we tried to integrate the component in our project, we get the following warning while building the project:
The currently targeted framework ".NETFramework,Version=v4.0,Profile=Client" does not include "System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which the referenced assembly "GdPicture.NET.11, Version=11.1.0.1, Culture=neutral, PublicKeyToken=1acb5b54ec09fcd9, processorArchitecture=MSIL" depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project.
So, as we're now under pressure to complete the project, we need a fast solution for this problem. You can give us license keys for version 10 in addition, that would be the easiest but only temporary solution for us.
Do you plan to build a dll of version 11 which works with the Client Profile only?
Is there another quick solution for our problem?
We tested your Product for our upcoming project. We used for these tests a trial Version of GdPicture.NET 10. This project must use .NET Framework 4.0 Client Profile.
As we were convinced of the component, we decided to buy it. Meanwhile, the version 11 was out, so we bought this version. Now, as we tried to integrate the component in our project, we get the following warning while building the project:
The currently targeted framework ".NETFramework,Version=v4.0,Profile=Client" does not include "System.Web, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" which the referenced assembly "GdPicture.NET.11, Version=11.1.0.1, Culture=neutral, PublicKeyToken=1acb5b54ec09fcd9, processorArchitecture=MSIL" depends on. This caused the referenced assembly to not resolve. To fix this, either (1) change the targeted framework for this project, or (2) remove the referenced assembly from the project.
So, as we're now under pressure to complete the project, we need a fast solution for this problem. You can give us license keys for version 10 in addition, that would be the easiest but only temporary solution for us.
Do you plan to build a dll of version 11 which works with the Client Profile only?
Is there another quick solution for our problem?