Reply to thread

Message

No. This release is specific to the version number. I have to create a new release for each version (because all of the DLLs in a release are associated with the specific MP release number).

I would have to create a completely new release for 1.30 and I don't think that is practicable, because it is still in beta. I'll create a version for 1.30 when the final version is released (or that's what I've been doing since 1.28).

To get over the hurdle CyberSimian is having, I think it will be important for someone to install 1.29 on a machine with a standard configuration and then run the upgrade to the refactored version and test that to see whether that works and to then trry to identify why CyberSimian's configuration doesn't seem to work.

As I said earlier, I have performed this process on several machines; 32 bit, 64 bit, Windows 7 and Windows 10. I haven't had any issues using exactly the same BAT file as I posted in the first posting in this thread.

My guess is that, if and when we find out why CyberSimian's config is failing we'll all go "Well, that was obvious" .

<blockquote data-quote="Anthony Vaughan" data-source="post: 1288563" data-attributes="member: 153283">No. This release is specific to the version number. I have to create a new release for each version (because all of the DLLs in a release are associated with the specific MP release number).I would have to create a completely new release for 1.30 and I don't think that is practicable, because it is still in beta. I'll create a version for 1.30 when the final version is released (or that's what I've been doing since 1.28).To get over the hurdle CyberSimian is having, I think it will be important for someone to install 1.29 on a machine with a standard configuration and then run the upgrade to the refactored version and test that to see whether that works and to then trry to identify why CyberSimian's configuration doesn't seem to work.As I said earlier, I have performed this process on several machines; 32 bit, 64 bit, Windows 7 and Windows 10. I haven't had any issues using exactly the same BAT file as I posted in the first posting in this thread.My guess is that, if and when we find out why CyberSimian's config is failing we'll all go &quot;Well, that was obvious&quot; <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /> .</blockquote>

[QUOTE="Anthony Vaughan, post: 1288563, member: 153283"] No. This release is specific to the version number. I have to create a new release for each version (because all of the DLLs in a release are associated with the specific MP release number). I would have to create a completely new release for 1.30 and I don't think that is practicable, because it is still in beta. I'll create a version for 1.30 when the final version is released (or that's what I've been doing since 1.28). To get over the hurdle CyberSimian is having, I think it will be important for someone to install 1.29 on a machine with a standard configuration and then run the upgrade to the refactored version and test that to see whether that works and to then trry to identify why CyberSimian's configuration doesn't seem to work. As I said earlier, I have performed this process on several machines; 32 bit, 64 bit, Windows 7 and Windows 10. I haven't had any issues using exactly the same BAT file as I posted in the first posting in this thread. My guess is that, if and when we find out why CyberSimian's config is failing we'll all go "Well, that was obvious" ;) . [/QUOTE]