Hi,
We currently have a licence for Infragistics NetAdvantage 2004 Vol.3 (version 4.3.20043.84) which we are successfully using in our WinForms application built with Visual Studio 2008 using .NET 3.5.
We are considering upgrading to Visual Studio 2010 and want to know if this is supported. Our initial conversion to Visual Studio 2010 shows us the Visual Studio designer still displays the UltraGrid properly. We don't yet know if the application will actually build and run because we have many other items to clean up to get the solution to build since the conversion. None of the build errors look like show stoppers so far, so we are confident we will get a build working in the next few days.
We initially wanted to upgrade to Visual Studio 2012, but another one of our 3rd party controls companies says their product will not draw in the Visual Studio 2012 designer as it will generate an exception.
I searched you support pages and only found prior versions of the NetAdvantage products going back to the 2007 edition only.
Do you have a support page that lists all your product version going back to the very first one and what editions of Visual Studio/.NET CLR they work with?
We are still building our solution with all projects set to 32bit architecture and .NET 3.5 runtime only. We have no plans to upgrade the bit level or the .NET level for our application. We want to take advantage of the enhanced IDE features mainly.
Thank you!
Hi Andre,
I guess you are talking about the following page: http://www.infragistics.com/help/supported-environments/.
As you can see there, we are not supporting anything less than NetAdvantage v10.1 for Visual Studio 2010. And v12.1 and v12.2 are supported by Visual Studio 2012. The version you are talking about is no longer supported for some time now, so we are only making any promises for the newest versions out there. Another link you could take a lok at is: http://www.infragistics.com/help/product-lifecycle/. It might be best to upgrade to v12.2 or wait for 13.1, so you can work with Visual Studio 2012 and the latest technologies.
I am checking about the progress of this issue. Please let me know If you need any further assistance on this.
Hi Boris,
I successfully upgraded our solution (which has 130 projects) from Visual Studio 2008 to Visual Studio 2010 and the Infragistics controls still appear to be working find in the Visual Studio designer (particularly the UltraGrid control) and in the application itself.
This is truly amazing that a technology now nearly 9 years old is running in a Visual Studio edition created 4 years after your controls were released. I must commend you.
Now, we would've really liked to upgrade to Visual Studio 2012 next, but I don't think that will work due to some other controls from a different vendor we have that says their controls will absolutely not work in Visual Studio 2012 as they will crash in the designer, so you can't easily work with the controls.
Depending on the future lifespan of this application, we will consider upgrading your controls and the other vendor's controls as well if we want to continue running in Visual Studio 2012 and possibly beyond.
Thank you for the kind words! This is truly amazing, I agree and I am not extremely surprised, since our engineering staff is working really hard on that side of the control set, as you saw. And as I already mentioned, these scenarios are not officially supported, which does not mean, that they will not work and I am glad, that they do for you!
Please let me know if you face any issues on your way!
Well, I spoke a bit too soon. Most of our forms work in the Visual Studio 2010 designer except those that use the UltraWinToolbars control.
Please see the discussion thread at: http://www.infragistics.com/community/forums/t/68669.aspx
It seems that any form with the UltraWinToolbars control (well, actually the control is called UltraToolbarsManager as it appears in the Visual Studio Toolbox panel in Visual Studio).
So far there is no work around for this. The code compiles cleanly and runs fine, but you can't view/edit the form in the Visual Studio designer due to the crash in this control.
Any ideas on how to fix this (other than a complete upgrade to the latest version of the .NetAdvantage control suite)?
Thanks,
Andre