DevExpress Template Gallery Changes (v21.1.3)

News
21 May 2021

With v21.1.3 (RTM) just around the corner, I wanted to describe a couple of changes to the DevExpress Template Gallery - all driven by user feedback and .NET Core/.NET 5 development:

  • The DevExpress Template Gallery now includes WinForms and WPF project templates designed for .NET Core.
    DevExpress WinForms design-time support is available as a CTP (still awaiting design-time from Microsoft). Please review the following knowledge base article for more information: Design-Time Support for DevExpress WinForms Controls for .NET 5 - FAQ.
  • v21.1 includes multiple project templates to better distinguish between different application types. See also a separate blog post about XAF's Solution Wizard v21.1 enhancements.

  • We also improved descriptions and added tags to help you locate DevExpress templates more easily.

Your Feedback Counts

As always, we look forward to your feedback on these enhancements and how we can better address your development needs going forward.

And don't forget to review the following blog post on our product delivery process: Important Changes to NuGet Packages and the Unified Component / .NET Core Desktop Product Installers (v21.1)

If you missed our Installation & NuGet survey last month, feel free to share your opinion below:

FREE DevExpress Xamarin UI Controls

Deliver high-impact native mobile apps with our feature-rich Data Grid, Scheduler, Chart, TabView, Editors, and utility controls. Reserve your free copy today!
mateo rojas
mateo rojas
when is the launch
23 May 2021
Dennis (DevExpress)
Dennis (DevExpress)
@mateo rojas: This week.
24 May 2021
Eduardo Quintana
Eduardo Quintana

I am anxiously waiting for the .Net 5 (6??) winforms support from Microsoft and the corresponding templates from DevExpress.

I am a long time DevExpress user and I do not plan to change this any time soon.

24 May 2021
Customer69806
Mikael 69806
What's happening to the designer in VS with Devexpress winforms? You get to grill Microsoft a little harder. Jump on them and say that we are many who are waiting for full support before starting new projects.
24 May 2021
CRM-40267349-7608-4495-a806-7d5f38270c84
mn
@dennis  this week when?
24 May 2021
DÖNÜŞ ŞENEL
DÖNÜŞ ŞENEL
If I think microsfor winforms solved the design time, I think this problem will not happen anymore when 16.10 is fully released and 21.1.3 is released on devexpress. Is it correct ?
 
24 May 2021
DÖNÜŞ ŞENEL
DÖNÜŞ ŞENEL

@mn

this week (it is friday at the latest) :)

24 May 2021
Dennis (DevExpress)
Dennis (DevExpress)
DÖNÜŞ ŞENEL is accurate :-)
24 May 2021
Christian Benner
Christian Benner

Im really unhappy since month even if DX has no chance to change it.

Today VS 2019 16.10 is available and still no (usable) WinForm Controls from DX.


NET 5 Project (only for testing purposes)  and only the Form1.


Yeah, Toolbox looks like a roastet chicken:



Oh a BarManager... nice...


Klick on "add".... oups nothing happens...

Klick again.. nice sandglass appears...  no response from devenv.exe.... uih VS is restarting




:-(   really unhappy....

Chris


(I like DX very much and in the past it was very nice and great to work with but since that holly sh*t that M$ outs out nothing works. Partners like DX has early access to Microsoft products (even to VS and also to the Alpha of VS 2022 which is  - bless some engineers or product managers - 64 bit -yeah)  and to finish that: its unbelievable that NET5 is out over a year, NET6 is comming soon but without Design time support 'till now..)

Who was sleeping that much?

25 May 2021
Dmitry (DevExpress)
Dmitry (DevExpress)
@Christian Benner, Mikael 69806


Thank you for the feedback. First and foremost, we understand the current design time support state is not acceptable and misses many crucial features. That is why we are not trying to smooth off the rough edges and are always straightforward in saying (in our blog posts and documentation) that currently design-time features are not supported. We have a separate NuGet feed that allows you to test these, but again, it is not a ready-to-use solution.


The "Microsoft partner" status does not work exactly as you would imagine. We have access to Microsoft repositories, but that does not grant any decisive advantage, we're not getting a word about upcoming releases beforehand. We're constantly monitoring Microsoft commits and pre-release notes, and test new versions as soon as they are rolled out. Unfortunately, these updates may include drastic API changes that we need to adapt. And there are a few features Microsoft still has not implemented yet (for example, Data Source and Toolbox). That is why we're currently working hard in both directions - migrate our existing .NET Framework designer to this new API, and explore a possibility to implement a completely custom solution.

I understand none of this addresses your concerns, but things we and any other 3rd party vendor face are monumental in nature. There is no easy way around these difficulties. I'm sure we'll get past this, but as of now, the only viable solution is the one suggested by Microsoft: keep two .csproj files (one for .NET Framework and one for .NET) in your solution and switch between them depending on whether you need design time.
26 May 2021
DÖNÜŞ ŞENEL
DÖNÜŞ ŞENEL
How long do you think microsoft can solve this design time design? 
Do you have such information?
 
26 May 2021
Christian Benner
Christian Benner

@Dmitry 


Thats why I've written "even if DX has no chance to change it".  But it's unbelievable that M$ leave us in the cold. I know that you're not right addressed with it but maybe you'll let them (M$) know about it.


I talked in a sidechannel on M$ Build with Satya and he'll address it with VS Team (not sure if he will really but I asked in the official channel on Build). I addressed also the VS Team and some of the VS Tecs.


I know ot doesn't make anything faster and better but my personal frustration level which grows since a year comes a little bit down..... 

Best wishes and stay healthy



26 May 2021

Please login or register to post comments.