WinForms and DXperience v2011

04 March 2011

[UPDATE 7-Mar-2011: fixed grammar, spelling, links]

There has been some feedback recently that we’re not paying enough attention to WinForms in our product plans and roadmap, or, putting it another way, we’re paying way too much attention to WPF, Silverlight, ASP.NET MVC, this, that, and the other to the detriment of WinForms. Let’s be specific here and repeat what I said in the 2011 Roadmap with regard to WinForms:

With regard to the Windows Forms controls, it is most likely that there will be a large number of smaller enhancements and new features rather than any large complex new control. The reason for this is simple: we believe that our offerings for this platform are very mature and robust. That’s not to say that our premier controls like the grid are in any shape or form “complete”, but we recognize that more benefits will come from performance improvements, usability improvements, and simplification of the APIs than by adding major features. Nevertheless, we welcome any thoughts and feedback you may have regarding features and functionality for our WinForms controls.

The scheduler will be enhanced with the year view. It is likely that this will be in the later release rather than the earlier one.

The rich text edit control will be improved with the same features described in the Silverlight section.

sand sculptorphoto © 2005 Ambra Galassi | more info (via: Wylio)When I presented my webinars about the ideas we had for our roadmap at the time of our annual Summit (first, second) in December, I also specifically asked for your thoughts about our WinForms controls. In particular, those WinForms controls that were not part of reporting, charting, pivot grid, scheduler, rich text edit, since they are all cross-platform efforts that share functionality across the platforms. What should we be looking at, what could we implement, what would benefit most from new functionality. I had a grand total of 11 replies. There were all very good (and I thank everyone who emailed me), and I circulated them among our “thick client” R&D team.

Since then, possibly some three months before the actual release, I posted the very first sneak peek about DXperience v2011.1. Coincidentally, it was about some new functionality in WinForms: the Ribbon is gaining a mini toolbar (or whatever the official fluent UI name for it is). I have a couple more ready to write about here, again about enhancements to XtraGrid (one’s about expressions in unbound columns in server mode, one’s about date group intervals in server mode, the other’s about incremental search in column filter dropdowns). Today I got another email from R&D about a new just-added WinForms feature for XtraGrid that we can’t talk about just yet for competitive reasons. It’ll be in XtraGrid first, and then we’ll move it over to the other grids later.

So, I will reject outright that we’ve somehow “abandoned” WinForms and are ignoring it and our customers there. We had some great new features in 2010, and we’ll have some more in 2011.

The other argument is that we’re paying too much attention to all of the other platforms, Oh, and WPF’s performance sucks. And, while we’re at it, it’s dying or dead, didn’t you hear? And, of course, anyone who writes thick client apps uses WinForms. (Most of those comments make me laugh, they’re similar to what we heard from our Delphi customers when we started developing for WinForms in the first place in 2002.)

Look, like it or not, we’re in a very competitive business. All software is. Perceptions about DevExpress come from many sources, some of which we can control, some not. We want to make sure that those perceptions are as positive as we can. Examples are “How open in DevExpress?”, “How well do they support us in the community?”, “How quickly and well do they respond to support queries?”, “How attuned are they to my particular market segment?”, etc. Another one is, do people perceive that we are at the forefront of (or willing to support) new technologies?

This particular perception is a double-edged sword in a way. Yes, customers want us to support new technologies – after all, when they’re ready to move forward with those new technologies themselves, they want their favorite vendor to already be established. And, no, they don’t want us to do so because it will inevitably mean that resources are going to be diverted from their favorite product onto the new stuff.

Me, I view it as planting an apple orchard. Once the orchard is established, all that’s required is pruning, weeding, chopping down the dead trees, yadda yadda. This frees us up to try and create other types of produce: kiwi fruit anyone? Maybe those other orchards will succeed, maybe they won’t. Maybe kiwis will go out of fashion before we get established. Maybe we can’t make any money at it. But, I would stand firm and say we have to, nay, are obligated to, move the company as a whole forward by trying.

32 comment(s)
Sigurd Decroos

I'm happy you embrase new technologies and I want to be in that market too. But can you convince me to convert a 500+ forms app from WinForms to WPF or SL that's working in a Citrix environment? What will my customers think about this when they find out their 'beloved' app is slow as hell because the UI is too fancy? Those customers want better speed, more functionality in the existing components and bugs fixed.

For my part you should take 1 or 2 of your developers and place them a whole year on releasing those accepted items from the past years :).

4 March, 2011

Currently there is no upgrade path from Winforms to WPF and Silverlight. Even if there was, I would not take the task and risk to upgrade all the UI controls to another UI platform.

What will be the difference if my desktop application moves from WinForms to WPF? Almost no difference.

Instead of this, I would invest my time to make my application better, more feature complete, more stable and fast. In this path, I would like to see DevExpress to continue providing new features for WinForms controls.

There are hundreds of wonderful ideas in WinForms support center in a TBD state.

All these ideas come from your customers, trying to solve real world problems and make their products better. By implementing feature requests your controls are becoming better too.  

I would not like to see this huge idea pool to get lost because you want to give more weight to WPF and Silverlight, just because they are new technologies.

I would like to see Winforms controls moving forward together with the new technologies at least until we have a strong alternative that will allow us to abandon Winforms.

4 March, 2011
Roel Vlemmings

I agree w/Sigurd. Many of the WinForms controls, such as XtraGrid and XtraChart have many great suggestions that have been marked by DevExpress as "Accepted - Release TBD" and have been so for years. Why not implement some of those?

5 March, 2011
Martin Hart

May I humbly request that S31303 be implemented. This dates from 2008, and in February 2009 was marked as implemented, only to be reclasified as TBD five days later.

This is a MAJOR sticking point for me with no workaround.

Julian, any chance???

5 March, 2011
Glen Harvy

This post just reinforces my view that DevEx are not listening to their present clients. I think everyone does agree that DevEx must address the emerging markets and remain in the forefront of technology. Please don't keep ramming the bleeding obvious down our throats - WE AGREE WITH YOU. Much of this post seems to be blurring the main thrust of our feedback in that we want more attention given to Winforms - and new controls in Winforms at that.

I'm not to sure what the purpose of your post was other than to re-state DevEx's position on Winforms. Your users are complaining that we don't think it's good enough but hey - it's your company so we just have to accept your position no matter how reluctantly.

Codeproject have some exciting free projects that only lack Devex skins so it's time I had a look at developing my own controls or workarounds. Perhaps we need to form a DevEx support group so that we can help each other add the Winforms controls/tweaks etc ourselves. Or else, perhaps for us  DevEx diehard Winforms users it's time again to Download-Compare-Decide on what's available to us elsewhere.

BTW: An orchardist you will never make.  There is always a need to keep up with market trends and plant new varieties and create new blends to meet changing palettes. Otherwise, your 2010 grape varieties Chablis will just not satisfy the demands of changing palettes. What your doing is ignoring developing the Chablis orchard because your current Chablis sales are pretty good and creating a Rose Wine orchard because next years 'in' wine is Rose.

5 March, 2011
Garry Lowther


Thanks for sharing this with us.

I personally have developed in/on Unix, Apple, DOS, COM, WinForms, WebClasses, ASP, ASP.Net, WPF and Silverlight.

Without a doubt, the most productive toolset I have ever used is Visual Studio 10, DevExpress DXperience and WinForms.

We are developing powerful smart client software which works with cloud services for data, files, e-mail, services etc..

All of this software is written using WinForms and takes full advantage of Software PLUS Services.

I would hate to think that us WinForms developers are seen as people who are stuck in 'departmental IT', writing client-server LAN only fat-client database apps and utilities. We are not. The most successful business software products today are native client apps which make use of internet services e.g. browsers, iPhone iOs+Apps, Android, iTunes, Skype, Reuters/Bloomberg terminals etc.. All of these are written as Software PLUS Services - cloud services.

WinForms is not going to be replaced by WPF or Silverlight or HTML 5 any time soon. WinForms apps work great with internet services on Amazon, Google and Microsoft Windows Azure. CUstomers love and expect responsive business applications which work as fast as Microsoft Office apps. For now, WinForms is still the best method of developing and delivering this.

Please give WinForms Dxperience its due attention. There are a lot of developers out there who will greatly appreciate it.

Regards, Garry@TriSys

5 March, 2011
Michael Thuma

Thats the last straw:))))).

>>Most of those comments make me laugh, they’re similar to what we heard from our Delphi customers when we started developing for WinForms in the first place in 2002

I am bunny but I have brain like my friend Dumbo the flying elephant. We have developed Winform Controls these days in the .net stone age (now at least bronze age), ok others in our company did, GDI, GDI+ mixture - there have been more issues.

.... and Mr. Julian and who comes every year whimpering like a wolve puppy remember last year, 'Redmond wolve pack "is so mean"' ... they shifted priorities, everything on Silverlight and 3 months later, Redmonders come to the conclusion oh - HTML5 is then the answer, back to stone age.

In parallel on Tweetdeck - Julie Lerman ... From friday on I will work on HTML 5 tools - Wednesday the week after the following she prepares presentation for Friday EFW and Azure ... Either the wohle .net blogging Evangelists tell whopers or the Redmond World is simply not focusing on their work ... these are your friends, you have friends:).

>>Look, like it or not, we’re in a very competitive business

Look, like it or not, this is not your customers problem - it is your challenge, you Compared you Decided. Don't complain ... Swim buffalo swim ... when you are drowned in work we seek another vendor ...

>>The other argument is that we’re paying too much attention to all of the other platforms

You only support one ... the Redmond plattform. I think you have common codebase now that makes your developments more responsitive to changes and appropriate to a time to market accepted by your customers? 2 or 3 years ago.

Now coming back to more technical stuff ... I am not a technican but from what I see, WPF will be one of those things - people will say afterwards "If we would have known...." - Winforms is still developed and it seems it runs under 64bit ... nothing has changed, since 2002.

WPF - the original intention was scalable GUI more downscale ... Netbooks I would guess ... this is more on the PADs - sales estimate 70 mio devices this year....

I have now a Workstation with Quad XEON with 2 30" monitors and yes ... also GIMP starts with 0 latency ... guys ... everything is fast on this machine. If someone really is going to write something sophisticated on WPF it works ... you can simple combine controls and develop your own (learning curve is little steep) ... but MS already ships almost everything that is required ... no need for third-parties. Maybe this is not the best place to say this ... truth is truth.

5 March, 2011
Peter Thorpe

Just to reiterate what others have put the reason you only got 11 replies is that most of the additions WinForms users would like to see are in the Accepted Release TBD state.

I personally don't mind you spending more time on WPF, Silverlight and ASP.NET MVC as I would like to start building any new projects on one of those technologies but am often limited if I know I will need certain controls not yet available in the suites.

5 March, 2011
Michael Thuma

@Peter - From the overall feeling I would say WPF or Silverlight. I can remember back I was partner at an MS shop ... WPF was said to be the way to go ... for me it is more a question of a Java + Flash combination or Silverlight. What you would like to start with is very likely built for this decade ... usually MS is changing very ofteh the direction but if something is here usually it is a supported way to go.

5 March, 2011

I said it on the other post, and I'll say it again: I really can't see how "a large number of smaller enhancements and new features" means bad news for Winform developpers.

5 March, 2011
Sigurd Decroos

@Crono: that depends what DX understands under this. If it means they will finally fix those bugs and deliver most of the 'Accepted, Release TBD', then I agree with you and I would be a happy DX customer. If it is just new things, not asked per se, than I get very worried.

5 March, 2011
Richard Choroszewski

I only came across this blog because seeing something winforms related I thought at last something for us. So was disappointed to see a justification for why DX appear to be taking their focus off this particular area.

I say appear but maybe not.

Take a look at the majority of recent blogs, new items and training videos and compared with a year ago winforms items are becoming fewer and further apart.

Our team cam to DX some 2 years ago mainly because of the obviously superb winform tools, and winforms remains and will remain the main focus of our business for the forseeable future.

Experimenting with Silverlight, WPF etc., is good for us to keep an eye on what might become mainstream one day (or maybe not if Ms dev people find some new super toy to play with) but the technology is not yet mature enough to base our business on.

So for us, we would ask that you direct the majority of your resources to winform developement and enhancement


and the 11 suggestions? We agree a red herring when compared to all the outstanding TBDs, some of which have been initiated by us and which we are impatient to see progress on

5 March, 2011
Mark Harby

We certainly became a DevExpress user because of the high-quality WinForms controls. We have 'played' with WPF and Silverlight and really see no advantage as we develop 100% client-server business applications.

I have to a admit to feeling a little 'yesterdays news' with the current DX business plan. There are an awful lot of TBD's already logged so your '11 suggestions' comment was probably a little mis-placed.

There are still some wonderful new features coming for the WinForms platform, the new search panel on the XtraGrid is an example of the sort of innovation we look for (and have come to expect) from DX.

Why not poll your customers to try and get an accurate picture as to what people are really using. I would be very interested to know the split for client-server development between WinForms/WPF/Silverlight.

6 March, 2011
Michael Thuma

Mark - they can build into the Winforms stuff whatever they like as long as it works:))) but what is on the list today.

a) PADs

b) IPhone

c) Android

d) Phone 7

e) HTML 5

f) Javascript JIT compile in IE9

When I look at the rest - looks little like VCL except of


6 March, 2011
Holger Kammerer

Thank you, Julian, for sharing your thoughts with us. Unfortunately, my english is not good enough to express all i want to say. However, i try to say the most important things. Excuse me, if i don't find the right words.....

Julian, it is not fair to set many issues to the state 'accepted TBD' and then ask the customers again, what they want to see in 2011. We already said what we want. If a function is important for me, i create a issue or i track a existing one. Thats the way how we customers vote for the things, which are most important for us. Why: DevExpress told us to do so in the past!

As a customer, i have the following problem: WinForms is a solid platform with many components and the most functionality. WPF is nice and will maybe replace WinForms in a few years. But now, if i want to convert our application to WPF, i have to explain my customers, why they will have less functionality with lower performance! Your WPF-suite is not ready to replace the WinForm-suite. So if i want to switch to WPF, i have to do it with another vendor. But i don't want another vendor. Till now, i am very satisfied with DevExpress. And i like the way you do your job, with the right mixture of severity and fun.

Please, take a look again at the issues, we customers created and voted for. Many of them are important for us to deliver a outstanding application with suitable functions.

A few examples, where my customers ask me, why this doesn't work:

1. If i export a XtraReport to RTF and open this with XtraRichEdit, the layout is confused.

2. If i export a XtraReport to Excel, there are no pagebreaks.

3. HTML as content in XtraReport? Not really!

And there are many more.....

6 March, 2011

@Sigurd Decroos Agreed. And since they did exactly that back in 2009, I see no immediate reason to lose faith for 2011.

6 March, 2011
Adlay Almeida (AA)

I could not agree more with what my fellow customers have stated. There are a plethora of entries with a TBD tag that seem to meander in limbo for what seems like an eternity. Many of these would greatly enhance the functionality of the controls involved and, in turn, make our programming lives far easier.

I think that, rather than trying to be all-encompassing and reallocating resources to a market share that is still in the growing phase, it would be much more helpful to your client base if these ethereal additions were taken care of and implemented.

Perhaps then there wouldn't be so much winning.

7 March, 2011
Tobias Lachmann

For me the future of Windows Applications is everywhere but not in WinForms. It will be there and supported for many years to come, sure, but the future it is not. Not even for business applications.

Microsoft has to fill the gap to apple with Design and Userexperience and WPF/Silverlight is the right way for that. And maybe we will see the next step with the next windows version and an other type of desktop.

We made our decision to WPF for redeveloping our Userinterface and haven't regret it till now.

So I can understand, that Devexpress forces other technologies than putting many resources to add the last 3% to a Controlset.

7 March, 2011
Hugo Barillas Quan

Just a couple of simple questions: Why Q248411 (minitoolbar), created on 18/02/2010 is planned for 2011.1 (according to your post Julian), but no one of the 3,000+ TBD  from 2006, 2007, 2008, 2009 and 2010 is getting the "Planned" state? Who is deciding the order of the development? Who is your customer, a secretary who wants a fancy toolbar or a serious enterprise developer? Sorry if I sound a little hard, but before "new" things, we want the "old" ones done. And again: WPF/SL is not ready for high-demand-critical enterprise applications. Just see how long the DevExpress demo takes to run!

7 March, 2011
Scott Wylie

I have to concur with most of the other respondent's, that the reason no one responded to your post was we already responded in your tracking system with hundreds of feature requests.

However just requesting a feature does not mean that everyone wants it. I had no idea how DevExpress tracks this until one of your own staff responded to one of my own requests.

If you look at Q252891 in your own system (Request for support for Coded UI Tests), I was told the following by your own staff.

"Currently you cannot vote for suggestions. Probably, we'll add this functionality in the future. We determine how popular a suggestion is by the number of users who track it. It is not the only criterion, but it is taken into account when we decide whether we should implement a particular suggestion. So, when you track a suggestion, we know that you want this functionality to be implemented. "

If this is how you determine what gets priority, why would you ask use to respond to your post, why would you not make this practice known to all your users or better yet, why not just put in a official voting system so we can all see the 'priority' together.  This is done by lots of other companies. MS's own Connected site does this.

If you did put in an official voting system, you would know exactly how your customers feel about features they already requested.  We would do your planning for you.

In the mean time, can you respond directly on Coded UI Tests?  There are a number of requests for it in your system but nothing in your roadmap.  If you follow what MS does then this should have been implemented last year when VS 2010 was released.  This is a huge deal for large systems.

7 March, 2011
Scott Wylie

Sorry I miss quoted the tracking number...Q252891 is the original request but my follow up was Q265723 where your own staff responded.

7 March, 2011
Dave Frank

When the question is put forward in the future about what customers would like, is there a way we can see a list of the features stuck in TBD? We can see what we've tracked and if we'd like to track some of the others as well. Almost like a mini "election" of sorts. I agree with many of the others here, there are boatloads of good suggestions in TBD and it would probably take a couple years to work through them as is.

7 March, 2011
Steve Sharkey

As others have said: don't complain about only 11 replies you have the TBD list already. To be fair I am interested in WPF once the feature set maps more fully to what is available in WinForms BUT past experience says that the longer it takes for WPF take up the more likely MS are to change direction and I will miss out on WPF in favour of the next new technology proposed - alternatively I could have left software to sell fruit & vegetables at the local market by then...

8 March, 2011
Holger Kammerer

For me, it's the same like Steve said: i am interested in WPF and when WPF-features >= WinForms-features, we will switch to WPF. But for now, when i read the roadmap the right way, this will not be reached in 2011. So we must use WinForms. We have a large client-server application which is not converted from day to day to WPF. This is a strategical issue, not only a technical.

Like Scott, i am also for a voting system.

8 March, 2011
Theodore p

Most people complain that WPF/Silverlight is too slow, not ready yet or even that the toolset does not cover their needs. To me this sounds like a request for more attention to these technologies and makes no sense to see so many people being agressive about spending resources there. It's never going to be ready or good enough to replace winforms if someone does not put some effort to it.

Personnaly i am a winforms developer and its unlikely that i will switch to these technologies in the near future, but i don't feel that i am somehow loosing support because Devexpress is working to bring their WPF/Silverlight controls to the same level as their winform controls. On the contrary, it makes me feel safe that if in the future i decide to embrace WPF/Silverlight there will be a set of controls ready, tested and documented for me to use. I don't know if WPF/Silverlight is the future or not, but i definetly know that winforms have been around long enough and i would like to see an alternative that will offer much better user experience. In that context i appreciate the risk devexpress is taking to invest in a technology that is still uncertain if and when it will become main stream.

I believe the strongest and most positive point that has been made in this blog is the request for Devexpress to work on these TBD issues. Instead of arguing about the future of WPF lets focus on the most popular and helpfull features we would like to see in winform controls. A voting system would be nice :-)

8 March, 2011

I must admit, Julian, that the "11 replies" part makes me uneasy as well.

I truly hope you guys still consider the customers-tracked TBD list in support center as a valuable feedback on what we truly need.

Remember, some of us have spent valuable time on this. :/

8 March, 2011
Brian Maxim

I understand the difficulty that Julian is talking about- it’s a double edged sword. You’re dammed if you do and dammed if you don’t, proven in some of the replies because people are complaining about lack of resources for winforms in one breath but in the other they need the SL/WPF roadmap completed before they even consider a switchover. I guess it’s about finding a workable balance even though Microsoft is pushing so many technologies- literally forcing component suppliers to jump on the bandwagon if they are to stay competitive.

As winforms is my primary concern, right now it would be impossible to justify an extra $800 per seat for the toolkit to “the powers that be”. Supposedly the UI would look prettier but DX have done such a good job with their skins that there would be apparently little benefit to the end user.

I do get the perception there is a lack of winform’s resource- it’s almost like they need a few more dev’s to tackle some of the age old TBD’s and then additionally a few more to create some new controls- something not seen for a long time in. I’m concerned that many new features will start to bypass winforms in favour of WPF. A case in point - when I enquired about cell templates for PivotGrid I was told I’d need to “upgrade”!

It’s also disappointing not to see some announcements for more data analytic controls- there’s a few gaps at the moment where DX are failing behind competitors. I’m thinking of a slice & dice tree map/heat map, spark line control, map control, a chart bar that allows panning/scrolling/range setting of a chart etc, many that have been sitting in the SC for years. Although I forecast any new big controls will be WPF only.

As Scott originally said, it would be nice if there was a way of publically seeing where the priories lie on outstanding TBD’s, although I was under the impression that tracking it was essentially a vote but perhaps not? My only concern is that actual end-user features might be pushed aside by issues that are popular with dev’s because those users (our clients) would not be voting. There would need to be some flexibility.

9 March, 2011
Hedi Guizani

Honestly the number of reply speaks for itself (rarely a blog post generate 27 replies and counting)

If i can suggest few things other what have been said :

1 / better documentation for some great features you already have (ex : DevExpress.Data.Filtering.Helpers.ExpressionEvaluator,

DevExpress.Data.Filtering.CustomFunctionCollection ...)

2 / much More posts on code central (great ressource) some sample can provide workaround solutions for many problems or even new features

3 / A lot of great TBD are becoming urgent :

-Calculated Fields - Add the capability to use relations : S33669

-Provide the capability to add custom functions : S33667

-Views - Add the Gantt view : A1194

-Implement the editable PivotFileDataSource : S30530

-GridView - add the ability to display unbound fixed rows within a data-aware grid : A1761

-Summary - Provide the capability to define expressions for the summaries : S133081

-Scripting - Add the capability to choose the version of .NET Framework to be used in scripts : S131463

-Filter builder to take expressions for values : S91747 (Natively there is a work around solution)

-Preview - Show the progress bar, immediately display the first page(s) in preview when ready, and provide the capability to cancel report generation : S31303

-SplitContainerControl - two/three direction auto-collapse functionality : Q207419 / S131949

-FilterControl - Be able to add filter criteria that involve children objects S20272

-Extension of the filterrow with operators S131889

-Add the OpenFile/SaveAs/SelectDirectory DevExpress equivalents to .NET standard controls that follows the application look&feel AS5023


Many of these suggestions are easy enough to implement and could be released in the next release

Good Luck

9 March, 2011
Brian Maxim

Hedi touched on more code central samples. I think it would be a good idea if DX could produce some more fully-fledged demos for visual analytics. I’m thinking a sales dashboard which shows a grid with spark lines and bullet graphs. A interactive floor plan showing seating/container/pallet allocations and a financial chart with the range bar I mentioned. Maybe there are workarounds using existing controls that I’ve not seen or are floating around in code central. Either way this would help to see some more potential and with pre-sales as well. The smaller demos showing specific features for learning are great- I’m thinking of bigger multi control apps.

10 March, 2011
Sigurd Decroos

More complex samples would be great, but implementing simple stuff like 'RowDoubleClick' or 'BeforeDeleteRow' events would be nice to have as well in the grids.

10 March, 2011
Eric Carlson

I second the request for more investment in the Coded UI testing framework support.  Many of our applications cannot be tested with this because we use DevExpress controls.

25 March, 2011
Sergio Hernandez

nothing new to say , +1 for develop winforms further

27 March, 2011

Please login or register to post comments.