Page 1 of 1

2.5 trial licensing woes continue

Posted: Mon 24 Apr 2006 20:15
by bradk
I created an asp.net web service in Visual Studio 2005. I copied the following strong named components from a working machine to my machine and registered them:

CoreLab.PostgreSql.dll
CoreLab.PostgreSql.EnterpriseLibrary.dll (my build, strong named)
Microsoft.Practices.EnterpriseLibrary.Common.dll (strong named)
Microsoft.Practices.EnterpriseLibrary.Data.dll (strong named)
Microsoft.Practices.ObjectBuilder.dll (strong named)

I have references to these assemblies in my project.

I then created a licenses.licx and added it to my asp.net project:

CoreLab.PostgreSql.PgSqlConnection, CoreLab.PostgreSql, Version=2.50.15.0, Culture=neutral, PublicKeyToken=09af7300eec23701

I then did a Build Runtime Licenses from the menu in Solution Explorer. I now have a Bin\App_licenses.dll assembly in my project.

When I run this project in debug mode and try to make a call I still get a licensing error:

CoreLab.PostgreSql.PgSqlException: License not valid. Please view "Licensing" topic in PostgreSQLDirect .NET documentation for details or contact Core Lab technical support.
at CoreLab.PostgreSql.PgSqlConnection.Open()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.OpenConnection()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteReader(DbCommand command)
at Service.PaulsPre380Postgres() in c:\Visual Studio 2005\Projects\PostgresTest\App_Code\Service.cs:line 95

I did not run the installer for your product on this machine, since I'm trying to find the configuration which will work on our servers. The deployment docs state all I need is the GAC enabled component.

I'm trying really hard to make this work so we can make a purchase.

Posted: Wed 26 Apr 2006 05:42
by Alexey
You ought to have our product installed on the machine where you compile your project.

Posted: Wed 26 Apr 2006 22:02
by bradk
yes, thank you that takes care of it after regenerating the app_licenses.dll for the project.