Hi,
My company just purchased a license for the latest version of NetAdvantage for ASP.NET, upgrading us from 2007 Vol.3 to 2010 vol. 3. I had previously built a top level horizontal UltraWebMenu that worked very well for us up until we discovered some bugs with it.
We would like to use the latest and greatest from Infragistics, but I don't want to have to refactor my code very much. I realize somethings have changed but what is the best control to use and what are the differences between them?
Hello mizurieta,
Infragistics has 2 ASP.NET menu controls - WebDataMenu and UltraWebMenu. WebNavBar has buttons like "play" and "fast forward", so that's a different type of tool.
The WebDataMenu is a newer version of the UltraWebMenu.
WebDataMenu Help
WebDataMenu Samples
(expand the WebDataMenu node to view the individual samples)
You can still use the UltraWebMenu too. Our 10.3 product comes with a Version Utility which should be listed in the start menu. If you run that utility on your web site (back it up first, of course), you should be able to use mostly the same code. If you find any bugs with it, you can submit them to our Developer Support Staff.
Here is a link to a blog post about our support for IE9.
I would also recommend reading this blog post about upcoming changes to the ASP.NET control set. That is the reason why I would recommend the WebDataMenu.
Let me know if you have further questions.
Elizabeth AlbertLocalization Engineer
Hi Elizabeth,
Thanks for the guidance. Is there anyway I can upgrade the UltraWebMenu only without having any assembly/namespace ambiguity issues in my project?
I need to maintain our existing code base using NetAdvantage v.7.3 for all other controls other than the UltraWebMenu, this is the only control we need to either upgrade to v.10.3 or replace with the WebDataMenu.
Thanks,
Malko
Hello Malko,
I just tried this out, and if you have multiple controls in your website (like a Chart and a Menu), then you will have an assembly conflict. For example, I got a conflict over the Infragistics.WebUI.Shared assembly, since both the Chart (old version) and Menu (new version) use it. I do not know how to resolve this (if it is possible) other than to upgrade the entire website to the newer version.
If you would like, I can forward this on to Developer Support to see if they have found a way to do this.
Just for reference, here are the steps I would have given you.
I found this topic about how to manually upgrade websites.
There are 2 places you need to update: the .aspx file, and the web.config file.
1. At the top of the .aspx file in the source view, there should be <%@Register ... directives.
<%@ Register assembly="Infragistics35.WebUI.UltraWebNavigator.v10.2, Version=10.2.20102.2022, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" namespace="Infragistics.WebUI.UltraWebNavigator" tagprefix="ignav" %>
Update this with the new CLR (if applicable), product version (ex. 10.3), and the new build number (ex. 10.3.20103.1013). It would look like this:
<%@ Register assembly="Infragistics35.WebUI.UltraWebNavigator.v10.3, Version=10.3.20103.1013, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb" namespace="Infragistics.WebUI.UltraWebNavigator" tagprefix="ignav" %>
2. In the web.config file, search for the assembly declaration. It should be under the <assemblies> tag.
<add assembly="Infragistics35.WebUI.UltraWebNavigator.v10.2, Version=10.2.20102.2022, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>
Update this with the same information as in step 1.
<add assembly="Infragistics35.WebUI.UltraWebNavigator.v103, Version=10.3.20103.1013, Culture=neutral, PublicKeyToken=7DD5C3163F2CD0CB"/>