I have tried installing the WPF 2250 Service Release but error still persists

We are using 9.1.1006 version. In this case which version of source code should I use for the fix? I downloaded both service release 9.1.2215 and Release build version 9.1.1006.

Also what would be steps after download. I was able to compile Infragistics3.Wpf.v9.1 binary but the depandant binaries are failing because Infragistics3.Wpf.v9.1 is not strongly named. Can you please provide some assistance in resolving this post fix failures?

Let me know if there are any specific steps we need to follow to get local compiled binary into our release.

To summarize below are the issues I'm facing now.

Infragistics3.Wpf.v9.1 is not strongly named and compilation is failing. We need a workaround here as all of our binaries are strongly named.

The above dll is been referred in atleast 100 projects across suite. All these dlls are referred from single location. Can we replace the old binary with locally compiled binary and expect everything to work as before?

As I mentioned in my previous step I am facing below compilation issues.

Error 11 The type 'Infragistics.Windows.Selection.ISelectableItem' is defined in an assembly that is not referenced. You must add a reference to assembly 'Infragistics3.Wpf.v9.1, Version=9.1.20091.1006, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb'.

Error 12 The type 'Infragistics.Windows.Helpers.DependencyObjectNotifier' is defined in an assembly that is not referenced. You must add a reference to assembly 'Infragistics3.Wpf.v9.1, Version=9.1.20091.1006, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb'.

pramanju,

For strong naming the assembly the source code that we provide doesn't include the key file so you would need to generate your own key and strong name the assembly yourself.

For error 11 and error 12 where the type is referenced is defined in an assembly that isn't referenced, this is likely coming from another assembly that is already compiled that references the version of the Infragistics3.Wpf.v9.1 assembly that we provide rather than the one that you compiled.  To resolve this you will need to recompile every assembly that is dependent on this assembly.

If you were using version 9.1.20091.1006, then you would want to use the same version of the source code if you are looking to only make the changes needed for the fix you wish to apply.

Let me know if you have any questions with this matter.

Alan/Andres,

Thanks for clarifying. With the suggested fix the issue is fixed . I appreciate your help in this regard.  Here are the steps we followed. Can you please verify these steps and let us know for any issues ?

·         Binaries version currently used 9.1.1006

·         Downloaded binaries from NetAdvantage for Win Client 2009 Vol. 1 - WPF Source Code (Release Build Version 9.1.1006)

·         Opened solution in VS2008

·         Added strong name for all 9.1 version projects in the source code.

·         Compiled all the binaries in release mode.

·         All the binaries are picked from respective bin/Debug folder and replaced in our common location in TFS

pramanju,

Those steps look correct if you need strong named assemblies.

OK, settings at the solution level overridden confguration settings at project level. I'm doing the whole recompilation with solution level release settings. will update you for any issues after that.thanks

Andrew, I debugged the code and verified that these assert statements are poping up now and then.

for example Debug.Assert(adjustedScrollPosOfTargetRecord >= 0); is rasing while editing the records. I indeed built the binaries in release mode but the binaries are not dropping at bin/Release instead they always drop in bin/Debug mode. I'm not sure if some other settings are overriding. Can you help us to build the binaries in release mode and if I'm missing something?

Thanks.

I have never seen that assert being raised so I cannot say what is happening. If you want us to look into that you would need to supply a sample that reproduces the issue. Basically the only assert in that routine is veritying that we have exited edit mode (or more accurately that we don't still have a CVP for a cell in edit mode which would/should have been cleared when the cell exited edit mode unless there was a problem there or unless someone tried to force the cell back into edit mode likely on another cell). That may well have been happening in your real application without you knowing since you would only see the assert if you were using a debug build - which you weren't with the release version.

I'm not sure what you are asking. If you are asking about when GetChildrenCore will be invoked as I mentioned I do not know as that is not something that we control. It is controlled/invoked by the WPF framework when something wants to get the children for a given automation peer or possibly when the associated element has been invalidated to update the cache. For anything further on that method you would have to check with MS or use reflector to review the WPF framework's implementation.

As to the OnSorted that is used to raise the Sorted event and from your description I do not know what is the cause of the NRE - it could be within your handling of the Sorted event or something else.