I'm working on a large app that has been written in WinForms using Infragistics controls where we made very heavy use of the AppStyling to get the app to look a certain way. We're now starting to use WPF for new development on this app (so it will have a mix of WinForms and WPF until all controls are converted), and our open questions deals with styling. Is there some way that we can continue to use the existing style files, either directly or after a conversion? The files themselves have been practically static for the last couple of years, so a conversion would work just fine.
Note: I'm not talking about styling of non-Infragistics controls (like is discussed in http://forums.infragistics.com/forums/p/3663/19032.aspx), I'm talking about using (directly or via conversion) the WinForms AppStylist files for Infragistics WPF controls.
Hello,
Thank you for your post. I have been looking into it and I can say that you are not allowed to use the AppStylist in WPF as it is stated here:
http://blogs.infragistics.com/forums/p/55702/286120.aspx
Hope this helps you.
It wasn't clear from the linked forum post if there was a feature request created for this or not - if not, I'd definitely like to add one to provide a converter from ISL to the equivalent WPF style. The lack of this feature is definitely blocking a switch to WPF for the product I'm working on, we've customized the look of the UI significantly with styling, and it would be too much work to completely re-do this for WPF - a converter that even got us 50% there would be extremely helpful.
How do I go about adding a rquest, do I just submit a support request (the same as I would file a bug), or is there some other mechanism to do that? All the requests I've seen added from the forums look like it is added by an Infragistics employee, not from someone outside.
Also, is there some way to watch the status of a feature request once it has been submitted? I did find a forum post that talked about the lack of this ability (http://community.infragistics.com/forums/t/43190.aspx), but that was from nearly a year ago - is there any change in this?