Hello,
We are having some issues with some name spaces while migrating to 17.2
For example: AzureBusyAnimationPresenter used to be accessible using the ig name space. In 17.2 it is only accessible through igPrim
We had to add an extra name space to access it in 17.2 even though it is in the same dll.
Version 16.1
xmlns:ig="http://schemas.infragistics.com/xaml" xmlns:igDP="http://infragistics.com/DataPresenter" <Style TargetType="{x:Type ig:AzureBusyAnimationPresenter}" BasedOn="{StaticResource {x:Type ig:AzureBusyAnimationPresenter}}"> <Setter Property="Height" Value="75" /> </Style>
Version 17.2
xmlns:ig="http://schemas.infragistics.com/xaml" xmlns:igDP="http://infragistics.com/DataPresenter" xmlns:igPrim="http://schemas.infragistics.com/xaml/primitives" <Style TargetType="{x:Type igPrim:AzureBusyAnimationPresenter}" BasedOn="{StaticResource {x:Type igPrim:AzureBusyAnimationPresenter}}"> <Setter Property="Height" Value="75" /> </Style>
Hello User201,
This change of namespaces for the "Animation Presenters" related to the XamBusyIndicator is known. This actually happened in version 2017.1, and it was documented in the "Breaking Changes" topic that is published with each subsequent version of our online documentation. You can read about this article here: https://ko.infragistics.com/help/wpf/breaking-changes-in-2017-volume-1#_Ref002. I would recommend reviewing these documents any time you upgrade between Infragistics versions.
Please let me know if you have any other questions or concerns on this matter.
Hello Andrew,
I have been looking for a detailed list of Infragistics XML namespace. I found this page but it is missing a lot of mappings.
Is there a list of all Infragistics Clr-namspaces mappings to XML namespaces ?
Thank you
The page that you have linked has the namespace mappings for the "main control" mapping for the listed assembly. For example, for the Infragistics.Controls.Charts.XamDataChart assembly, the "Infragistics.Controls.Charts" namespace is listed, as it contains the XamDataChart control.
There does not currently exist a page that maps all of the Infragistics namespaces, although if it isn't listed on that page, it is very likely encapsulated by one of the two following namespace definitions:
xmlns:ig="http://schemas.infragistics.com/xaml"xmlns:igPrim="http://schemas.infragistics.com/xaml/primitives"
Thank you for your kind explanation.
The reason the the "igPrim" needs to be used in the style whereas the "ig" namespace is used in the documentation article is because your style is targeting the AzureBusyAnimationPresenter, whereas the topic is targeting the AzureBusyAnimation class. These classes do not currently exist in the same namespace, as the Presenter is a "primitive."
In order to see which XML namespace to use per object, I generally would recommend looking at the object's "full" name in code behind. For example, the AzureBusyAnimationPresenter exists in one of our "primitives" namespaces, namely, Infragistics.Controls.Interactions.Primitives. This "Primitives" at the end designates that the element exists in the "igPrim" namespace.
Thank you Andrew.
If there is one to blame for the confusion is myself.
Please take a look at this page. The XML namespace used in the XAML code to access the AzureBusyAnimation is ig and there was no need to use igPrim.