Current filter:
                                You should refresh the page.
                                Support Center
                                0
                                  • Since the 11.2 release, it seems, you are relating to the System.Windows.Interactivity.dll assembly from Microsoft.
                                    Unfortunately the one you are using is an older one, compared to the one I'm using in my project.
                                    So my questions:
                                    - Why are you using this assembly (What could be impacted when using another release of the assembly)
                                    - Has this assembly to be deployed or not

                                    Severin

                                Show all comments
                                • Hi Severin,

                                  We will discuss the System.Windows.Interactivity assembly usage with our developers and let you know as soon as we find out anything. Please wait a while.

                                  Thanks,
                                  Ted

                                • Hi Severin,

                                  Thank you for your inquiry. A similar problem has already been discussed. Please take a look at the following thread and let me know if you have any additional questions: MVVMLight.SL5 has new 'system.windows.interactivity.dll' that crashes banded view feature.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.05.2012

                                  Hi Alexander

                                  The case you pointed me to is not helping at all.
                                  So my previous questions are still not answered:
                                  - Why are you using this assembly (What could be impacted when using another release of the assembly)
                                  - Has this assembly to be deployed or not

                                  Severin

                                • Hi Severin,

                                  Thank you for the update.

                                  >> Why are you using this assembly (What could be impacted when using another release of the assembly)
                                  Currently we have included the latest official version of the System.Windows.Interactivity library in our installation. There is a newer version, however it is included in the "MICROSOFT EXPRESSION BLEND PREVIEW FOR SILVERLIGHT 5" and according to the "MICROSOFT PRE-RELEASE SOFTWARE LICENSE TERMS" we cannot include the newer version while Microsoft has not released the final version of the "MICROSOFT EXPRESSION BLEND PREVIEW FOR SILVERLIGHT 5". I have attached the corresponding EULA.

                                  You can re-build our libraries with the newer version of the System.Windows.Interactivity library. A problem should not happen, because the Interactivity library has backward compatibility.

                                  >> Has this assembly to be deployed or not
                                  In a general case, you do not need anything special to deploy this assembly. When you reference DevExpress.Xpf.Core.v11.2.Extensions and set the CopyLocal parameter to "True" (default value), Visual Studio should automatically add System.Windows.Interactivity library to the output directory.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.05.2012

                                  Hi Alexander

                                  My official (non Beta) System.Windows.Interactivity.dll has the version 2.0.20621.0
                                  The DevExpress instance has 2.0.20525.0

                                  Your suggestion of compiling against another version is really not acceptable, as I have to do that on every release of DevExpress.

                                  Also your statement relating the Deployment is confusing.
                                  You write, that it has NOT be to deployed, as it is automaticaly copied to the output directory?
                                  But the output directory has to be deployed. So the conclusion will be, I have to also deploy the System.Windows.Interactivity.dll

                                  But then, I would run into problems with different versions of the dll, as I am not using GAC.
                                  So I have to deploy two dlls with the same name in the same directory, kind of tricky.

                                  DevExpress should really rethink about the usage of this dll. Even if DevExpress compiles with the newest dll, there could be other dlls referencing another version of this dll.

                                  Severin

                                • Hi Severin,

                                  Thank you for the clarification. I understand your concern now and I should say that I am slightly confused by your answer. I'm almost sure that the System.Windows.Interactivity.dll version 2.0.20621.0 is not official and cannot be deployed with our installation, because this contradicts the EXPRESSION BLEND EULA. Perhaps, I am wrong here. Would you please point to a place in the MS Download Center where our clients can download this assembly version? I have looked for this assembly in the Microsoft Download Center, but found only the version we are currently using: Microsoft Expression Blend Software Development Kit (SDK) for Silverlight 4.

                                  As for compiling the extension assemblies, it is unnecessary to recompile them on each release of our products. We will start to use the latest version of the System.Windows.Interactivity.dll assembly immediately after we receive a confirmation about the release of this version.

                                  Regarding the deployment issue: you are right, System.Windows.Interactivity.dll should be deployed on client machines. However, you can deploy only a single version of this assembly. I can offer you three options here:

                                  1. Use the version of the System.Windows.Interactivity.dll assembly that is included in our installation (2.0.20525.0). In this instance, your application should use only this version.
                                  2. Use version 2.0.20621.0 of this assembly. In this case, you will need to rebuild our extension dlls.
                                  3. Use version 2.0.20621.0 and supply the assembly binding mechanism. This approach is described in Redirecting Assembly Versions.

                                  I hope that my explanations help you resolve the problem. Don't hesitate to reactivate this ticket in case of any additional questions.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.07.2012
                                • Hi Severin,

                                  Thank you for the link, it clarifies the cause of the problem. It seems that any non-english version of the Blend SDK for .NET 4 has version 2.0.20621.0. If you select the English language for this page and click the "Sprache wechseln" button, you will see that the original version is 2.0.20525. It means that the API of the System.Windows.Interactivity 2.0.20525 and 2.0.20621.0 libraries is absolutely identical. For this reason, I suggest you use the assembly binding mechanism described in MSDN: Redirecting Assembly Versions.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.11.2012

                                  Hi Alexander

                                  Can you please provide the following informations regarding System.Windows.Interactivity.dll

                                  What kind of binding is used by DevExpress assemblies?
                                  Is a "specific version" used? So only one and only one exact version of the assembly is accepted?

                                  Which functionality is using this assembly?
                                  How can I test if the assembly is loaded correctly. Which Method/Dialog is using the assembly?

                                  Severin

                                • Hi Severin,

                                  Thank you for the update. We use a light binding to this assembly: the SpecificVersion parameter equals "False". The DevExpress.Xpf.Grid.Extensions.BandedViewBehavior class is a Behavior<> descendant that is included in the System.Windows.Interactivity library.

                                  As for the assembly testing, I suggest you create a sample that uses BandedViewBehavior. You will have no problems with it if it operates correctly. I am afraid I cannot suggest any automatic method.

                                  Regarding your last question about the method that uses the assembly, I am afraid I do not quite understand this question. Please clarify what you mean.

                                  P.S. If you have tried the suggested approach with Assembly Bindings, would you please share the results with me? Did you manage to accomplish the required task? If you need assistance with this, just drop me a line.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.12.2012

                                  Hi Alexander

                                  Thanks for the usable information.

                                  As I'm waiting for banded view since years, I am surprised and disappointed by the current implementation.
                                  Banded view sould be a core functionality and not depending on technology from third party assemblies.
                                  This is a show stopper for me of using the Grid. I can't understand why DevExpress is doing such a bad design.

                                  Please rewrite the banded view feature, so it does not depend on 3rd party assemblies and is fully supported by the core.

                                  Assembly Binding: I will not spent time on doing this, because it would be a bad design. So it will result in not using controls of DevExpress which are referencing this assembly. Please publish a maintained list of assemblies which are referencing the System.Windows.Interactivity.dll so I can make sure I don't use a reference to them.

                                  Severin

                                • Hi Severin,

                                  Thank you for your inquiry. We have not implemented Banded View. We have only created a workaround. This solution is not perfect and has some limitations described in the corresponding Knowledge Base article: Advanced Banded View Layout with attached behavior. However, it can be used in a simple case. The workaround we implemented is based on the Attached Behaviors pattern, and uses a library from the Microsoft Blend SDK. This library is free. When we implement the real Banded View, we will not use this library.

                                  Currently only extension libraries are using the System.Windows.Interactivity assembly: DevExpress.Xpf.Core.Extensions and DevExpress.Xpf.Grid.Extensions.

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.12.2012

                                  Hi Alexander

                                  That's much more suitable. Thank for the information.
                                  But why isn't the current banded view workaround titled as a workaround?
                                  There should be a big warning -> "This is a workaround and will be implemented in a different way in the future".

                                  Severin

                                • Hi Severin,

                                  Thank you for the update. We have mentioned that this solution is a workaround in the corresponding suggestion, KB, and the blog post: Add the capability to arrange column headers into Bands and create multi-row layouts, Advanced Banded View Layout with attached behavior, WPF and Silverlight Grid Control - Advanced Banded View Layout (a cool workaround).

                                  Thanks,
                                  Alexander

                                • Severin Meyer 01.12.2012

                                  Hi Alexander

                                  the word workaraound is only in the title of the blog post.
                                  That's really not enough. The KB is not using the word workaround once.
                                  So, please add a warning at least to the KB on top.

                                  Severin

                                • Hi Severin,

                                  In general, we present our KB articles as a guide on how to accomplish a common task, if it cannot be done with our control out of-the-box. However, it's not a problem for me to add the required warning message. I have modified the first article sentence to reflect this.

                                  Thanks,
                                  Alexander

                                • Ilya (DevExpress Support) 10.10.2013

                                  Hi,

                                  is any way to target System.Windows.Interactivity 3.0 from the Net 4.5 , otherwise than bindredirect to force it, because in the desktop version (\DXperience 13.1\Bin\Framework) is still the Net 4.0 version of the System.Windows.Interactivity (2.0..).

                                  May be will be useful to use kind of side by side directly in the installation package .

                                  Regards,
                                  Johannes

                                • Ilya (DevExpress Support) 10.10.2013

                                  Hi Johannes,

                                  You can reference the required version of the System.Windows.Interactivity from your application manually. I have created a screencast demonstrating it. It seems that it all works properly. Would you please clarify what version of the library you wish to use in your application?

                                You must  log in  or  register  to leave comments

                                If you need additional product information, write to us at info@devexpress.com or call us at +1 (818) 844-3383

                                FOLLOW US

                                DevExpress engineers feature-complete Presentation Controls, IDE Productivity Tools, Business Application Frameworks, and Reporting Systems for Visual Studio, along with high-performance HTML JS Mobile Frameworks for developers targeting iOS, Android and Windows Phone. Whether using WPF, Silverlight, ASP.NET, WinForms, HTML5 or Windows 8, DevExpress tools help you build and deliver your best in the shortest time possible.

                                Copyright © 1998-2014 Developer Express Inc.
                                All trademarks or registered trademarks are property of their respective owners