Options
Asp.net nag message
Brian Donahue
Posts: 6,590 Bronze 1
Hi Mike,
There are two things that the licensing needs to succeed: One is the SQL
Toolkit.lic file that you get when you successfully activate the Toolkit,
and the second is the .licx file in your Visual Studio project.
When you build your Toolkit application, you need to include a
plain-text file called licenses.licx. To create the file, right-click on
your project in the Solution Explorer, select Add->Add new item, Text File,
and call that licenses.licx. This file needs an entry for each object that
you're going to use from the SQL Bundle. For instance, if you're creating a
project that references RedGate.SQLCompare.Engine.dll, enter
RedGate.SQLCompare.Engine.Database. For RedGate.SQLDataCompare.Engine.dll,
enter RedGate.SQLDataCompare.Engine.ComparisonSession. If your project
references both assemblies, enter both object names.
Save this file, and when you build the project, Visual Studio will look
for the licensing information for the objects that you had referenced in the
SQL Toolkit.lic file to embed in the resulting assembly, which will cause
that assembly to run without asking for licensing information. If there is
no SQL Toolkit.lic file present, Red Gate's licensing provider will contact
our web service on the licensing server and send back some information that
will become a SQL Toolkit.lic file and embed that in the assembly.
I hope this helps!
Regards,
Brian Donahue
Red Gate Technical Support
"Mike B" <nospam@nospam.com> wrote in message
news:zdEwYsWTEHA.1512@server53...
> I'm having the same problem as was described in a previous post by Dan
> Hammond. I'm trying to do an ASP.net web form and it errors out when
trying
> to instantiate the toolkit objects on the server side because of the
> registration nag message. We own the license and were able to register it
> successfully on windows applications (although the nag message comes up
with
> every new app! Once it is registered for each indidual windows app things
> work fine). Is there any way around this problem? I've tried copying
the
> license to the web bin folder, re-registering objects et. al. to no avail.
>
>
There are two things that the licensing needs to succeed: One is the SQL
Toolkit.lic file that you get when you successfully activate the Toolkit,
and the second is the .licx file in your Visual Studio project.
When you build your Toolkit application, you need to include a
plain-text file called licenses.licx. To create the file, right-click on
your project in the Solution Explorer, select Add->Add new item, Text File,
and call that licenses.licx. This file needs an entry for each object that
you're going to use from the SQL Bundle. For instance, if you're creating a
project that references RedGate.SQLCompare.Engine.dll, enter
RedGate.SQLCompare.Engine.Database. For RedGate.SQLDataCompare.Engine.dll,
enter RedGate.SQLDataCompare.Engine.ComparisonSession. If your project
references both assemblies, enter both object names.
Save this file, and when you build the project, Visual Studio will look
for the licensing information for the objects that you had referenced in the
SQL Toolkit.lic file to embed in the resulting assembly, which will cause
that assembly to run without asking for licensing information. If there is
no SQL Toolkit.lic file present, Red Gate's licensing provider will contact
our web service on the licensing server and send back some information that
will become a SQL Toolkit.lic file and embed that in the assembly.
I hope this helps!
Regards,
Brian Donahue
Red Gate Technical Support
"Mike B" <nospam@nospam.com> wrote in message
news:zdEwYsWTEHA.1512@server53...
> I'm having the same problem as was described in a previous post by Dan
> Hammond. I'm trying to do an ASP.net web form and it errors out when
trying
> to instantiate the toolkit objects on the server side because of the
> registration nag message. We own the license and were able to register it
> successfully on windows applications (although the nag message comes up
with
> every new app! Once it is registered for each indidual windows app things
> work fine). Is there any way around this problem? I've tried copying
the
> license to the web bin folder, re-registering objects et. al. to no avail.
>
>
This discussion has been closed.
