Licensing / Nightly build process
Posted: Wed 24 Jun 2009 14:54
I am currently trying to fit your component into our build system, and have a question on licence.
Generally speaking, we create a .licence file from the .licx, using lc.exe, and then the .licence file is the one included in CVS and compiled by the build. If I try to do this with OraDirect, it works fine for ASP.NET, but the administration module (a WinForms application) that also uses the class library that points to your component throws the following :
Devart.Data.Oracle.OracleException: Assembly that contains embedded dotConnect for Oracle license cannot be used with this application: MGDIS.Administration.exe.
Do this mean we have to deliver an App_Licence.dll with the ASP.NET part of the solution and include a .licence in the MGDIS.Administration.exe ? Or is there still a way to simply include the licence in our AglNETDB class library that is used from both ?
Thanks in advance for your help,
Generally speaking, we create a .licence file from the .licx, using lc.exe, and then the .licence file is the one included in CVS and compiled by the build. If I try to do this with OraDirect, it works fine for ASP.NET, but the administration module (a WinForms application) that also uses the class library that points to your component throws the following :
Devart.Data.Oracle.OracleException: Assembly that contains embedded dotConnect for Oracle license cannot be used with this application: MGDIS.Administration.exe.
Do this mean we have to deliver an App_Licence.dll with the ASP.NET part of the solution and include a .licence in the MGDIS.Administration.exe ? Or is there still a way to simply include the licence in our AglNETDB class library that is used from both ?
Thanks in advance for your help,