-
February 4th, 2015, 04:07 PM
#2
I guess what I am saying here is that I should be able to install the new version and not have to then give out instructions to customers on how to manually change their bespoke config files to work with the new version. It should be backward compatible. If <monitor> is replaced with <dashboard> it shouldn't just fail to start. At worst it should be a warning. Also why is MPN mandatory when it wasn't before? Presumably a new demo that gets included by default requires it? If so, can I get around it?
Ideally, at the very least, I would like to get a migration tool that would parse and correct an old config file so that it will work with version 6 without manual intervention........please
Similar Threads
-
By bkretschmer in forum Adapter SDKs
Replies: 1
Last Post: June 20th, 2013, 09:44 AM
-
By Alessandro in forum General
Replies: 0
Last Post: January 22nd, 2013, 12:15 PM
-
By anilkumar2508 in forum Adapter SDKs
Replies: 1
Last Post: October 23rd, 2012, 09:16 AM
-
By wwatts in forum Adapter SDKs
Replies: 1
Last Post: May 2nd, 2012, 09:55 AM
-
By DarioCrivelli in forum Client SDKs
Replies: 1
Last Post: April 6th, 2010, 11:12 AM
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
All times are GMT +1. The time now is 11:59 PM.
Bookmarks