Has anyone tried to use XamNumericSlider in the VS 2015 Update 1 RC designer?
I get an error:
InvalidOperationException: Can only base on a Style with target type that is base type 'XamNumericSlider'.
I'm incorporating this style:
Office2010Blue.xamSlider.xaml
X:\Program Files (x86)\Infragistics\2015.2\WPF\Themes\Office2010Blue
My example is below
<IgSliders:XamNumericSlider
xmlns:IgSliders="http://schemas.infragistics.com/xaml"
Orientation="Vertical"
TrackFillBrush="Transparent"
Width="120"
Height="500"
FontWeight="Bold"
VerticalAlignment="Center"
MinValue="-11"
MaxValue="12"
Value="{Binding HoursOffset, Mode=TwoWay}"
Grid.Column="0"
Grid.RowSpan="1" />
I should note that this seems to only affect the designer. The app itself has no problems related to the slider.
There may be a regression in the Visual Studio designer. I had no problems before I upgraded to update 1. Although I also updated to IG15.2 at the same time so I couldn't be sure where things went wrong.
Anyhow, I found that I can use the new "disable project code" button in the palette below the XAML designer and that makes the designer error go away. (Although the slider now is replaced by a simple place-holder).
In my investigation, I found the following on CONNECT. Maybe all the WPF control vendors are running into the same issue now that update 1 is released?
https://connect.microsoft.com/VisualStudio/Feedback/Details/2005303
I've just tested it with VS2015(without update) and the designer seem to be working as expected(the slider is shown).
The description of the issue's details seem to be matching the case with the theme for the XamNumericSlider - that exactly how the style for the control is structured - based on another style that has it's target type pointing to the base class that all of the different sliders are inheriting from.
I'm testing this out on a VM with Update 1 RC installed in order to be sure that's causing the issue with the designer.
I don't know from which version you've upgraded to 15.2 but there hasn't been much changes in the control or in its theme lately so it seems not likely this issue is because of a change in the control.
Thanks a lot for your investigation. We're up-voting this connect issue for sure :)
I'll get back to you after finishing the testing against VS 2015 Update 1 RC.