Infralution Support Forum Index Infralution Support
Support groups for Infralution products
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Upgrade 5.x to 6.x

 
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support
View previous topic :: View next topic  
Author Message
SdB



Joined: 31 Aug 2010
Posts: 35

PostPosted: Mon Jan 26, 2015 10:40 am    Post subject: Upgrade 5.x to 6.x Reply with quote

I upgraded ILS from 5.x to 6.x.
I noticed that products created with ILS 5.x now contain new information "Backward Compatibility". This field is now filled with a Version number. Can I assume that the version number contained in the field is valid or do I have to check manually if that Information is correct ? If the latter is the case does this invalidate my licensing parameters integrated in the product binary ?

Best regards,
Stefan
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Tue Jan 27, 2015 7:15 am    Post subject: Reply with quote

That's a good question.

The Backward Compatibility setting just disables certain features (like the ability to set Expiry Dates) if those features weren't supported in the selected version. This prevents you accidently trying to use those features if your code is compiled against a version of ILS that didn't support them. If this isn't set explicitly then License Tracker deduces the version of ILS that the product was created with based on the existing settings. It should get this right - but is somewhat conservative so you should review the setting after upgrading to Version 6. If License Tracker has set Backward Compatibility to 5.0 but you know your code is compiled against 5.7 of ILS (and customers aren't still using earlier versions of your application compiled against earlier versions of ILS) then you can safely change this to enable you to access all the features available in 5.7.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Fri Jan 30, 2015 11:01 pm    Post subject: Reply with quote

I just upgraded to 6.0 and my backward compatibility is set to 5.0 on my product.

I upgraded from 5.11.1 but the nearest compatibility setting is 5.10 so I presume I use that?

Also I downloaded the source in the version before 6 and imbedded in my code. I couldn't find anywhere in the source where it references the version I compiled in; is there an easy way to check in the source?

I want to be sure I set the backward compatibility setting correctly so help appreciated.

Julian
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Fri Jan 30, 2015 11:13 pm    Post subject: Reply with quote

Yes if your code is compiled against Version 5.10 or later then you can just use the 5.10 setting.

If you still have the source code you originally downloaded then you can check AssemblyInfo files which have the version embedded in them. If you didn't keep the original download code and don't have the AssemblyInfo files then you can email a copy of your AuthenticatedLicenseProvider code file to support@infralution.com and we can tell you what version it was.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Sat Jan 31, 2015 9:30 am    Post subject: Reply with quote

Ah OK it was 5.11.1.

So can I ask a related question (sorry to hi-jack this thread).

After upgrading I'm a bit confused about what to do with embedding the v6 source code into my App. Obviously I have software out there including the 5.11.1 source code (compiled using say "Product A" settings which is set to 5.10 compatibility level), but now I've upgraded I want to replace that source with v6 code for my next app release. So do I now have to setup a new "Product B" (compatibility set to Version 6.00) in ILS if I want to use the new features. Then also can I still point that at the same IPN.NET product without having to create a new PayPal object?

Apologies but this is my first major upgrade like this so don't want to make a mistake in my procedure in building in the new source code to my app.

Julian
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Sun Feb 01, 2015 4:52 am    Post subject: Reply with quote

You can update your application to use the Version 6 source code and leave the backward compatibility set to Version 5.10. This will mean both older code and newer code will continue to be able to authenticate license keys - however you won't have access to the new version 6 features.

If you want to use the new version 6 features then you have three options:

1. Upgrade your code to use Version 6 source code and release a new version of your application. Then change backward compatibility to Version 6.0. Customers who have an older version of the application will still be able to run the application, however they won't be able to install their licenses on another computer using an older version of the application. They will need to download and install your latest version. If they do attempt to install their license key using an older version of the application they will get an error message like:

Quote:
The license file contents have been modified and the license is no longer valid. You may need to reinstall the license using the original License Key provided to you when you purchased the product.


This is because the license file now contains elements that the old version doesn't recognise and so the signature no longer matches.

2. The second option is to create a new product and use the same product settings. To do this you need to use the "Export Settings" button for the existing product then use the "Import Settings" button for the new product. Using the same settings will ensure that old license keys can be used for the new product. The new product has to have a different name (eg "My Product" => "My New Product") - which may be problematic because this name is displayed by default in the license dialogs and messages. You setup the IPN.NET data for this product to match your existing product and remove the IPN.NET data for the old product. The advantage of this approach is that existing customers can continue to install their license keys on both the old and new versions of your application. But this is a disadvantage for you too - because they can bypass the new features in Version 6 (Clone Detection/Block Terminal Services) by continuing to use the old version of your application.

3. The third option is to wait until you are doing a more major upgrade (possibly paid) and at that stage create a new Product with completely new settings. Existing customers have to obtain a new license key to use the new version of the application (if it is a paid upgrade then this isn't an issue).

We ourselves are using a mixture of approaches 1 and 3. For ILS the change to using the Version 6 features was (obviously) associated with a major paid upgrade so we created a new Product (option 3). For Globalizer we will shortly be releasing a new minor upgrade will include changing the licensing over to use Version 6 features (option 1).
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Sun Feb 01, 2015 5:53 am    Post subject: Reply with quote

Thank you, a very comprehensive and easy to understand set of options.
Back to top
View user's profile Send private message
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Wed Feb 04, 2015 8:00 am    Post subject: Reply with quote

Hi

Since I upgraded to 6.0, users that were issued keys under v5.5 but had not activated them yet are getting this error (see attached). What can I do to fix.



Julian
Back to top
View user's profile Send private message
Infralution



Joined: 28 Feb 2005
Posts: 5027

PostPosted: Wed Feb 04, 2015 8:05 am    Post subject: Reply with quote

It looks like your Authentication Server was configured to connect directly to your License Tracker database. You have upgraded License Tracker (and the database) but you have not deployed the new Authentication Server binaries. You need to FTP copy the files from C:\Program Files (x86)\Infralution\Licensing System 6\AuthenticationServer to your web server. Copy all the files EXCEPT for Web.Config and the App_Data directory. After uploading the files navigate the Install.aspx page in a web browser and run the installation script.
_________________
Infralution Support
Back to top
View user's profile Send private message Visit poster's website
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Wed Feb 04, 2015 8:45 am    Post subject: Reply with quote

OK now i'm confused.

I copied over the IPN files and ran the install.aspx. Then deleted install.aspx as suggested.

Now I need to overlay the ILS files over these file in the same folder and run the install.aspx in the ILS copied files? Tried that and I get


Server Error in '/Ipn' Application.
--------------------------------------------------------------------------------


Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:


An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:



[NullReferenceException: Object reference not set to an instance of an object.]
AuthenticationServer.Settings..cctor() +81

[TypeInitializationException: The type initializer for 'AuthenticationServer.Settings' threw an exception.]
AuthenticationServer.InstallForm.LoadSettings() +36
System.Web.UI.Control.LoadRecursive() +71
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3178
Back to top
View user's profile Send private message
juwi_uk



Joined: 10 Mar 2014
Posts: 47

PostPosted: Wed Feb 04, 2015 8:57 am    Post subject: Reply with quote

Sorry my mistake was putting the files in the "ipn" virtual directory instead of the "authenticate" one. Doh!

Think it's OK now.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    Infralution Support Forum Index -> Licensing Support All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group