Thank you for looking into this issue, please find enclosed sample projects for 15.2 and 13.1. We are able to see the difference between the two versions. In our application, it's worse.

Thanks,

Crystal.

Hi Lindos, 

I'm afraid I don't understand what you are asking. You say you cannot update your older applications to the newer version because you are concerned about regression - but then you are asking for a patch. But any patch we were to give you would have the same risks as a new version. You would still have to update you application to use new assemblies, re-test, rebuild, and re-distribute it to your users. So that seems like a contradiction to me. 

Having said that, if you can post a small sample project here that we can run and debug, then we can try to track down exactly what changed between v15.1 and v17.1 and I might be able to tell you what version that change was made. That would limit the number of changes you would be exposing your application to - you wouldn't have to necessarily make a two-year jump.

And maybe even potentially give you a workaround so you wouldn't have to change assemblies at all. But any way you slice it, there's no getting around rebuilding and re-distributing your application. 

Hi Mike,

In regards to the regression of the application. My concern is that if we were to upgrade the application to use a full new release of the Infragistics assemblies that this would require a full regression of the application. Instead, a small patch of the assemblies which have the performance fix would allow us to target regression to the specific areas of our application which would be affected. This is by far a much smaller area of regression. I agree that some level of regression would need to be done, however, limiting the scope would be the ideal solution.

I have done some further testing with the Infragistics dlls. I downloaded the latest release you have for v15.2 (15.2.20152.2118). Our application is currently using v15.2 (15.2.20152.2052) in which we see the performance issue.

I updated our application to use the 2118 dlls and discovered that there is no performance issues with this release. I further narrowed this down by progressively swapping out the 2052 versions with the 2118 versions. This lead to Infragistics4.Win.UltraWinGrid.v15.2.dll being the one dll where the performance issue was noticed as being fixed (note this also required me to reference the 2118 versions of Infragistics4.Shared.v15.2.dll and Infragistics4.Win.v15.2.dll as they are dependencies).

This test has at least helped to narrow down the scope of versions of where the fix may have been introduced to somewhere between the release of 2052 and 2118. I hope this can help you to take a look at what may have changed that would affect scrolling of the grid where there are icons in the FormattedTextEditor column type. I suspect the issue is not necessarily in the scrolling but more in the rendering of the field.

In the meantime, I am working on putting together a sample application which demonstrates the performance issue. This may take some time as I need to migrate the production code for the grid over to the sample application.

Would it be possible for us to distribute the three 2118 versions of the dlls alongside the 2052 ones (which are all installed in the GAC)? This could be considered a kind of patch. Do you foresee any possible conflicts which could arise from having mixed version references in our project? In other words, would 2118 be backwards compatible with 2052?

Thanks for your time,

Lindos.

Hi Lindos, 

That's great that you narrowed it down. Build 2118 might be your best best, then. I am not even sure if there were any service releases in between those two, or if they are still available. 

I took a quick look at the history of the code for 15.2, but I can't narrow it down by control, only by assembly, and most of the code for the FormattedTextEditor is in the Win assembly, which has a ton of changes for that time period, so nothing really jumped out at me. 

If you can provide a smaple that I can run and debug that demonstrates the problem, I can definitely narrow down the exact change or bug fix that fixed it, though. 

Oh... I just checked and apparently 2118 was the only Service release for v15.2. 

Also, to answer your question, all of the versions are always backward compatible (aside from the occasion breaking change that has to be made for a bug fix).

But you can't mix versions. All of the Infragistics assemblies need to be the same version. 

Hi Mike,

Thanks for looking further into this issue and for answering my questions about the version compatibility.

I will continue to attempt to try and reproduce the issue in a sample app.

If I can get the sample app to show the issue, and you are able to track down the cause to a bug in 2052 that was fixed with 2118, what would be your recommended next steps in getting this fixed in our production code? Do you provide small patches/hot fixes for such occasions? Or, would we ultimately need to do a full upgrade to 2118?

Thanks,

Lindos.

The value of the field in the DataRow is being set when we update the UltraDataSource for the grid. This happens as we navigate from one business object to the next (the grid data is refreshed for each business object by first clearing the rows collection in the UltraDataSource). The code spins through a collection (the row data) in the business object and calls the UltraDataSource objects Rows.Add() method for each new row. Each new DataRow's column values are then updated. After all the data has been loaded we don't update it any further. From this point on (until the next business object is loaded) the data remains static.

In what event are you setting the value of the field in the DataRow. I assume that's done before you bind to the grid. Or are you dynamically building or changing the data as you scroll, like in the InitializeRow event of the grid or something?

Okay, that makes sense. Not sure why I was confused - it seems perfectly obvious from the code, now. 

Hi Mike,

Clarifying what ImageX is.

In the Visual Studio project, a Resource file (Resources.resx) is added to the project under the Properties folder. Opening up the Resource file in Visual Studio you can select the Images section from the dropdown. The Images are added to this section by drag and drop from Windows Explorer where the image filename becomes the key in the Resource file. The Resource file has a build action of Embedded Resource.

The embedded images are referenced from the Resource file in code using the following:

var image = Properties.Resources.ImageX;

Where ImageX is the name of the image in the resource file.

We did discuss keeping the images as is, embedded in a resource file, and writing them to disk at the time they were needed. This option was ultimately rejected due to business needs and the decision to deploy the images up front in a folder was made.

If I can reproduce the issue in a sample project I will definitely send it your way.

Thanks for your help.

Lindos.