The application I'm working on was originally coded in VB.net 2003. It was migrated to VS 2005 and since the infragistics controls have also been upgraded to NetAdvantage 2005 Volume 2.
The program compiles sucessfully, but when I run the program and attempt to open the form containing the UltraWinChart.UltraChart, it brings the application down.
The control UltraWinChart is placed in a UserControl which at run time is added to a UltraTabControl.
I created a new UserControl in a blank new windows application and added this dynamically at run time. This seems to work fine by itself in this application, but if I integrate this control in the original application, it still fails.
The references added are:
Infragistics.Win.v5.2
Infragistics.Win.UltraWinChart.v5.2
Infragistics.Shared.v5.2
Infragistics.Win.Misc.v5.2
Infragistics.Win.UltraWinTabControl.v5.2
and some more for addition controls.
The original application was referencing Infragistics.UltraChart.Core.v4.1.dll plus .Data and .Resources dll's and I don't see corresponding Dll's for v5.2.
Has anyone else ran into these problems? Any ideas on how to resolve this?
NetAdvantage 2005 Volume 2 wasn't updated for use with Visual Studio 2005. Though most of the problems I've personally seen have been design-time issues, it's possible that you may be hitting a simple runtime incompatibility between this version of the tooset and version 2.0 of the .NET Framework.
Does the same problem occur in later versions of the toolset? I suggest that you download a trial version of NetAdvantage Win Client 2008 Volume 3 to test there.
I now have infragistics NetAdvantage 2005 volume 3 installed. I upgraded the VB.net project with the project upgrade utility which indicated the upgrade as successful with no errors.
But when I run the program and attempt to open the form that holds the UltraChart, the application closes again. It does not allow me to step in the code to find out where it fails. Although I did notice that it fails when trying to initialize the component.
In Visual Studio 2003 the version for Ultrachart was: Infragistics.Win.UltraWinChart.v4.1.dll. The ugradeed project references Infragistics2.Win.UltraWinChart.v5.3.dll
Thanks
I don't think there's enough information to tell whether this is a bug in our controls or something specific to the project.
Can you reproduce the problem using NetAdvantage Win Client 2008 Volume 3, our most recent release? NetAdvantage 2005 Volume 3 is no longer eligible for maintenance, so anything not fixed in the hot fix posted won't be addressed in this version. Our more recent releases, on the other hand, are still eligible for both maintenance and support.
If using NetAdvantage Win Client 2008 Volume 3 fixes the issue, then this was likely a bug that we've fixed or otherwise worked around.
If it doesn't address the problem, then we'll likely need to look into this in more depth. In this situation, please submit a support request so that we can investigate this more in-depth. The more information you can provide in your support request, the better. We normally ask for sample projects whenever possible, though I expect this would be very difficult to reproduce in a sample.
I have a chart on a user control and at runtime it fails on initializing the chart. The exact syntax used is:
Dim chartTrendData as New Infragistics.Win.UltraWinChart.UltraChart
As a side effect when I have a base user control and call the same line of code above in the constructor of the base, the subsequent initialization works fine. But it then crashes when I attempt to view the chart.
How can this issue not be related to the Ultrachart control if all I'm trying to do is initialize? Is there a tool I could use to get further in debugging because it completely crashes the application now.
As an additional note, 2005 Volume 3 is no longer maintained by Infragistics, which means we are not providing any new bug fixes for it. If the problem you're encountering is a bug, as opposed to something about your system's or project's setup, then it might be fixed in the last hot fix we released for this version of the toolset. You may want to try installing that, using the Project Upgrade Utility on your project again, and testing one last time to see if that addresses the issue you're seeing.
Based on the information available, there isn't enough information to tell for certain what the cause of the problem is. I suggest submitting a support request, as detailed in my previous post, to provide more details that a Developer Support Engineer can investigate.