Home › Forums › Bunifu UI Winforms › Migrating Existing Applications Using Bunifu 1.5.3 to 1.5.4+ (Currently 22.214.171.124)
mpappertParticipantMay 25, 2018 at 12:46 amPost count: 5
I see there is documentation on how to create new applications with the newly released Bunifu 126.96.36.199 but what about updating applications that were built with 1.5.3? Is there an easy way to transition all the buttons, etc. to the new version?
Wilberforce SegutonKeymasterMay 25, 2018 at 8:50 amPost count: 35
Thank you for your question.
The current version has a backward compatibility hence controls used in version 1.5.3 will still work. In fact once you extract the lastest version files you will see version 1.5.3 dll which ensures we have backward compatibility.
In the new version 1.5.4+ we added 9 controls which include: new Bunifu Button, checkbox, drodown, label, progressbar, radio button, scrollbar, textbox, toggle switch. We have put together documentation of the same. Please see below:
Progress bar: https://bunifuframework.com/docs/bunifu-ui-winforms-docs/#bunifu-progress-bar-2
Radio button: https://bunifuframework.com/docs/bunifu-ui-winforms-docs/#bunifu-radio-button
Vertical Scrollbar: https://bunifuframework.com/docs/bunifu-ui-winforms-docs/#bunifu-vertical-scrollbar
Horizontal Scrollbar: https://bunifuframework.com/docs/bunifu-ui-winforms-docs/#bunifu-horizontal-scrollbar
Toggle Switch: https://bunifuframework.com/docs/bunifu-ui-winforms-docs/#bunifu-toggle-switch-2
In case you are stuck with migration anywhere kindly let us know we will assist you.
mpappertParticipantMay 25, 2018 at 6:42 pmPost count: 5
So, just for clarity, if I wanted to upgrade the old 1.5.3 button to the new 1.5.4+ version, then I’d have to create a new 1.5.4+ button and migrate the event code to that new button and then delete the old 1.5.3 button … and this would have to be repeated for each 1.5.3 control that we would want to migrate to the corresponding newer 1.5.4+ version? That seems like quite a laborious task …
Wilberforce SegutonKeymasterMay 28, 2018 at 8:35 amPost count: 35
Sorry for the delayed response. Unfortunately that is the only way at the moment. This is because the new Bunifu Button functions as a new feature all together and is different from the older buttons.
We tried to enable backward compatibility so that there is smooth transition to new buttons and make migration less laborious in that you can still use the old buttons.
In future it will be a lot easier as we would like to make Bunifu Button a standard.
I hope I have clarified your question. My apologies for the tedious process.
mpappertParticipantMay 30, 2018 at 8:33 pmPost count: 5
I am now receiving the following error in the application:
Message=Could not load file or assembly ‘Bunifu.Core, Version=188.8.131.52, Culture=neutral, PublicKeyToken=e8e24ccd28363fe9’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Any thoughts on how to fix this?
Wilberforce SegutonKeymasterMay 31, 2018 at 9:42 amPost count: 35
Sorry about that. Seems you need to update the core.dll reference.
Please remove current Bunifu Core from references section. After that please add the new Bunifu core.dll to your reference. You will find the new core dll from the extracted folder 184.108.40.206
Let me know how it goes.
mpappertParticipantJune 1, 2018 at 3:45 amPost count: 5
I’ve removed both references to Bunifu.Core and Bunifu_UI_v1.5.3 and re-added them to the project – ensuring that I was selecting the files from the 220.127.116.11 folder. I notice that the Bunifu.Core file loads as 18.104.22.168 whereas the Bunifu_UI_v1.5.3 is v22.214.171.124 – would this be part of the issue?
mpappertParticipantJune 1, 2018 at 3:48 amPost count: 5
I downloaded the .zip file from the portal again (apparently it’s now 126.96.36.199) and I’ve referenced these versions and everything seems to be working now. Bunifu.Core is now showing as 188.8.131.52 so my guess is somehow I got an old version of it?
Wilberforce SegutonKeymasterJune 1, 2018 at 6:00 pmPost count: 35
Glad that everything is working now.
For the core, we did not do any update on the file therefore it’s all good as it is. Unless you are you are getting an error. If not that shouldn’t worry you.
Thank you for the update.
AnonymousInactiveJune 15, 2019 at 12:29 amPost count: 114
- You must be logged in to reply to this topic.