Hi Luciano,

Yes, you're correct, the first step to upgrade your WebUI would be removing the 2015 version. This can be done simultaneously while you are installing the 2016 R1 version as the installer should ask you to uninstall the previous version first. And the next step would be updating bin and web.config.

You could also try migrating your website to the new unified theming project template to beautify our WebUI Controls into a fresh and modern look, see our new unified theming in action here. These steps have been explained thoroughly in our blog. You could check it out here.

If you've got any questions regarding the steps, feel free to ask here in the Community or contact us through live chat.

Best Regards,
Erwin Sanders

Hi Erwin, I have executed the migration but I experienced the following problems:

·         The working website went in “try mode” no license

·         Browsing from VS 2015 no way to update bin directory with the 2016 R1 dlls

·         Applying “register resources” didn’t produce any change

I did the following steps:

·         Deleted all current licenses codes of WebUI 2015 R1

·         Uninstalled WebUI from control panel programs and features

·         Removed all the assemblies for WebUI 2015

·         Installed WebUI 2016 R1

·         Registed licenses for WebUI 2016 R1

·         Open my working website and deleted under bin all dlls

·         Tried to reassign reference to dlls of WebUI 2016 R1 but VS 2015 didn’t apply the changes.

I have rolled back my server so I can start back from scratch all the migration process. If the way I’m trying is full of pitfalls, please tell me which is the right and tested one.

At the meantime I will read the solution suggested in your answer.

Thank you.

Regards.

Luciano

Looking at your steps, it should all be good. Did you register both Design Time and Run Time license key? You can register the Design Time key from our License Manager and Run Time license key is registered in the Web.config for deployment purpose.

Also, what did you mean by 'VS 2015 didn't apply the changes'? Did your project fail to be rebuilt?

Best Regards,
Erwin Sanders

Hi Erwin, I’ll give you more information:

On the development machine I always install only the design licenses for each component and unless in WebUi 2016 R1 something changed it works perfectly fine.

In Visual Studio 2015, after deleting the dlls IsNet from bin directory, I select add reference, in order to add the dlls for each WebUi component, afterwards I browse the new dll for WebUi 2016 and click add but VS doesn’t add the dll under bin directory. May be I should delete the project’s directory under:

C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files

What about installing side by side WebUi 2015 R1 and WebUi 2016 and after applying all changes remove WebUi 2015 R1?

Thanks for supporting me.

Regards.

Luciano

Hi Luciano,

Thank you for the detailed information, I really appreciate it. When you tried to add the ISNet.dll, it's actually successfully added, but it refers to GAC, therefore you can't see it in the bin folder (the reference is declared in Web.config).

However, if you need to add the assemblies to your bin folder, simply choose Add Existing Item.

About installing two versions of WebUI simultaneously, I think that would be impossible as the installer will ask you to uninstall the older version as you install the new one.

Hope this helps.

Best Regards,
Erwin Sanders

Sure Luciano, but I don't think that would be necessary because as I said earlier the ISNet.dll assembly refers to GAC instead of the bin folder. Have you actually tried to run one of your website after adding the new assemblies? Or is there any error messages that failed your project?

Best Regards,
Erwin Sanders

Hi Luciano,

just tried it on our end and the issue occurs. Our development team are working on this now, there will be a hotfix soon. Thank you for the report.

Best Regards,
Erwin Sanders