-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
license error for powerpack from an old dotnet site #1
Comments
Hi, I'm afraid not, or at least no tricks spring to mind. One option would be to take the code here and compile it for your old dotnet site. This code is 'unlicensed', so freely available to do with as you please. Off the top of my head, the only change you may need to make could be to change OpinionatedGeek.Web.PowerPack.Licensing.PowerPackLicenseProvider.GetLicense() to return a ValidLicense():
Since this was last released in 2008, I suspect you'd need an older version of .NET to compile it. |
thanks for the quick reply. we'll have to see if/how we can re-compile it. i wasn't sure if the licensing data was stored in the registry or a flat file we could copy from the old server to the new server. |
Oh I can certainly answer that one! The only place the code looks for licensing information is in the configuration, which - unless you've done something a little unusual - will be in the web.config. You should have a line like this near the top of the old web.config:
Then you should have a config section like this somewhere in the old web.config:
You'll need to copy those across to the new web.config. That's all I can think/remember that you'd need to do to take the license across. Good luck! |
license error for powerpack from an old dotnet site.
any tricks to fix this?
The text was updated successfully, but these errors were encountered: