This question is locked. New answers and comments are not allowed.
Jerry Kurata
Top achievements
Rank 1
Rank 1
Jerry Kurata
asked on 07 Jul 2010, 04:16 PM
Hi,
One of our developers was testing OpenAccess ORM and installed a trial version. We decided that we are not going to use OpenAccess, but now we cannot figure out to remove the trial licence from the solution. Each time we compile we get the warning: OpenAccess Warning: trial licence found for Telerik OpenAccess ORM. Can someone provide me the instructions on how to get rid of this licence?
Thanks,
jerry
6 Answers, 1 is accepted
0
Hi Jerry Kurata,
It seems that your project is still processed by the Telerik OpenAccess Enhancer tool. You have to remove the enhancing part from the project. Can you share more details which OpenAccess feature did you used? If it was the Visual Designer for OpenAccess, you can open the project with XML editor and remove the import statement at the end of the file, that imports the OpenAccess.targets. We will be also glad if you can share your feedback in regards to why you decided not to use OpenAccess in your application? Is something of real importance missing or the reason was something else?
Kind regards,
Dimitar Kapitanov
the Telerik team
It seems that your project is still processed by the Telerik OpenAccess Enhancer tool. You have to remove the enhancing part from the project. Can you share more details which OpenAccess feature did you used? If it was the Visual Designer for OpenAccess, you can open the project with XML editor and remove the import statement at the end of the file, that imports the OpenAccess.targets. We will be also glad if you can share your feedback in regards to why you decided not to use OpenAccess in your application? Is something of real importance missing or the reason was something else?
Kind regards,
Dimitar Kapitanov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Jerry Kurata
Top achievements
Rank 1
Rank 1
answered on 07 Jul 2010, 05:38 PM
Dimitar,
Thank you for your reply. Part of the issue is that I did not do the work that added the ORM, but am stuck cleaning up the results. I will see if I can locate reference.
I believe the reason for not using the ORM had something to do with WCF RIA Services integration. I will try to find out more and let you know.
Thank you for your reply. Part of the issue is that I did not do the work that added the ORM, but am stuck cleaning up the results. I will see if I can locate reference.
I believe the reason for not using the ORM had something to do with WCF RIA Services integration. I will try to find out more and let you know.
0
Jerry Kurata
Top achievements
Rank 1
Rank 1
answered on 08 Jul 2010, 03:18 AM
Dimitar,
I did a search on my solution for the words "openaccess" and "orm" and found no matches. FWIW, here is the compiler output that shows the error.
c:\program files\telerik\openaccess orm\sdk\VEnhance.exe -assembly:D:\ChemInfo\GlobalDart\GlobalDart.Web\obj\Debug\GlobalDart.Web.dll -config:D:\ChemInfo\GlobalDart\GlobalDart.Web\Web.config -debug+ -verbose+
License(-1, 1): warning:OpenAccess Warning: Trial license found for Telerik OpenAccess ORM.
OpenAccess Warning: Trial license found for Telerik OpenAccess ORM.
Enhancement complete -- 0 errors, 1 warnings
GlobalDart.Web -> D:\ChemInfo\GlobalDart\GlobalDart.Web\bin\GlobalDart.Web.dll
0
Accepted
Hi Jerry Kurata,
Typically the enhancer is called by MSBuild tasks - custom or ones in predefined .targets files. You should unload the project in question, open it with an XML editor (OpenWIdth... option in the context menu of the Solution Explorer, and then select an xml editor) and look for the following MsBuild artifacts:
a) import directive for OpenAccess.targets file
b) import directive for other OpenAccess-related .targets file like enhance/enhancer.targets or any other .targets file that looks suspicious.
c) Any custom exec task that fires the vehnace.exe from the command line.
Please keep me updated how things are going with this search.
Kind regards,
Dimitar Kapitanov
the Telerik team
Typically the enhancer is called by MSBuild tasks - custom or ones in predefined .targets files. You should unload the project in question, open it with an XML editor (OpenWIdth... option in the context menu of the Solution Explorer, and then select an xml editor) and look for the following MsBuild artifacts:
a) import directive for OpenAccess.targets file
b) import directive for other OpenAccess-related .targets file like enhance/enhancer.targets or any other .targets file that looks suspicious.
c) Any custom exec task that fires the vehnace.exe from the command line.
Please keep me updated how things are going with this search.
Kind regards,
Dimitar Kapitanov
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Gita
Top achievements
Rank 1
Rank 1
answered on 11 May 2011, 12:47 PM
hello
i am also getting the same problem of trial license for open access found .as you have told to remove the import of enhancing open access .i have already remove the open Acess extension but the problem is not solved out .please help me out
i am also getting the same problem of trial license for open access found .as you have told to remove the import of enhancing open access .i have already remove the open Acess extension but the problem is not solved out .please help me out
0
Hi Jerry Kurata,
did you look into the .csproj or vbproj project with an xml editor?
You may find a node like:
or
Please remove the node from the file and the warning will be gone.
Regards,
Jan Blessenohl
the Telerik team
did you look into the .csproj or vbproj project with an xml editor?
You may find a node like:
<Import Condition="Exists('$(MSBuildExtensionsPath)\OpenAccess.targets')" Project="$(MSBuildExtensionsPath)\OpenAccess.targets" /> or
<UserProperties OpenAccess_ConfigFile="App.config" OpenAccess_ConnectionId="DBConnFirstSteps" OpenAccess_Enhancing="True" OpenAccess_UpdateDatabase="True" OpenAccess_EnhancementOutputLevel="1" />Please remove the node from the file and the warning will be gone.
Regards,
Jan Blessenohl
the Telerik team