Won't Fix
Last Updated: 12 May 2020 08:22 by Hans
Hans
Created on: 20 Jan 2020 09:38
Category: TabControl
Type: Bug Report
5
TabControl: Tab selection does not work in the VS designer when switching between different views
Tab selection does not work in the VS designer when switching between different views.
16 comments
Hans
Posted on: 12 May 2020 08:22

Hi Kalin,

thanks for the reply.  To bad Microsoft won't fix the problem.  And yes, I did try the suggested workaround, and it works, but it is a workaround and not a solution.

Regards,
Hans

ADMIN
Kalin
Posted on: 23 Apr 2020 16:00

Hello Hans,

We spent few days investigating the issue, I discussed it with Microsoft and they checked it on their side. Unfortunately there isn't anything that can be done on our side in order to workaround the problem or resolve it, that is why the status is Won't Fix (as we don't have Can't Fix status..).

At the moment we provide design time support for VS 2010 and above. One of our goals is to provide great design time experience for everybody using our WPF components no matter of the VS version.

Did you try the suggested workaround in my previous reply? 

Regards,
Kalin
Progress Telerik

Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic.
Our thoughts here at Progress are with those affected by the outbreak.
Hans
Posted on: 17 Apr 2020 06:42

Hi Kalin,

why has this item received the 'Won't Fix' label ?  Is this your (and Microsofts) way to force people to migrate to VS 2019 ?  I can tell you I'm not happy about this.  It surely changes the way I look at the Telerik company ...

Regards,
Hans

ADMIN
Kalin
Posted on: 06 Mar 2020 10:58

Hello Has,

What I can suggest you would be - when you need to work on the second view with TabControl (that doesn't work) you could simply kill the VS designer process:

After that just reload the designer in the desired view and will work as expected:

Hope this will help.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Hans
Posted on: 03 Mar 2020 07:25

Hi Kalin,

Yes, I know, the new WPF designer is available in the VS2019 only.  My question is: is there anything else I can do or try or any other solution to solve my problem in VS2017 ?

Regards,
Hans

ADMIN
Kalin
Posted on: 02 Mar 2020 16:31

Hi Hans,

The preview of the new WPF designer is available in the VS2019 only. 

Let us know if you have any other questions.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Hans
Posted on: 26 Feb 2020 13:04

Hi Kalin,

Does this mean there is no solution for this problem if I want to continue using VS 2017 ?

Kind regards,
Hans

ADMIN
Kalin
Posted on: 24 Feb 2020 11:51

Hi Hans,

Indeed the new WPF designer preview feature is only available in the latest preview of VS 2019. 

Let me know if you have any other questions or concerns.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Hans
Posted on: 20 Feb 2020 09:59

Hi Kalin

thanks for the sample project.  I am able to run it, but in the designer I get an Invalid Markup message for both views.  I suppose this is because I need to enable the new WPF XAML designer, but I can't seem to find this option.  I'm working with Visual Studio 2017.  

Regards,
Hans

ADMIN
Kalin
Posted on: 20 Feb 2020 08:12

Hi Hans,

Thanks for your patience. Please check the attached sample project what you need to do would be to:

Enable the new WPF designer - go to Options > Preview Features, select “New WPF XAML Designer for .NET Framework” and restart Visual Studio.

The manual work that needs to be done is to replace the binaries in the Design folder - you would need to move the NetCore design binaries to the WPF40 or WPF45 design folder. In the sample project I included the controls binaries from the WPF40 folder as well as design binaries from the NetCore "design" folder.

Hope this helps.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Attached Files:
Hans
Posted on: 13 Feb 2020 09:34

Hi Kalin,

I will await your sample app before taking any steps.

If I manually replace the Telerik binaries, will they be updated automatically when there's a new release or will I need to do this manually each time ?

Regards,
Hans

ADMIN
Kalin
Posted on: 12 Feb 2020 14:48

Hi Hans,

The suggestion is to switch to the new VS designer and use the Telerik UI for WPF design binaries built for the Net Core version of the controls (with the same full framework project). When the service pack release is live next week - I will attach sample app here demonstrating the suggestion.

Hope this will help.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Hans
Posted on: 12 Feb 2020 14:16

Hi Kalin,

I'm sorry, but we're not planning on switching to .NET Core in the near future.  We need this problem fixed in standard .NET (version 4.6.1)

Regards,
Hans

ADMIN
Kalin
Posted on: 12 Feb 2020 08:14

Hi Hans,

This is already implemented - the solution is to use our .Net Core design binaries with the new VS studio designer enabled. What needs to be done:

1. Enabled the new designer  - go to Options > Preview Features, select “New WPF XAML Designer for .NET Framework” and restart Visual Studio.

2. Replace the Telerik UI for WPF full framework designer binaries with the ones for net core - go to the NetCore folder and copy the content of the design folder to the design folder of the full framework binaries location.

3. Reopen the project/solution and open up the designer.

However when we were testing this we noticed some issue in the NetCore design time implementation of the TabControl (related with the selection logic) and we fixed it. So the suggested solution will work as expected (for the TabControl) next week - using the upcoming R1 2020 Service Pack release binaries.

So please give it a try next week when the release is live and let me know if you have any issues.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.
Hans
Posted on: 10 Feb 2020 14:27

Hi Kalin,

Microsoft has responded to the logged bug:

This issue is resolved in our “New WPF XAML Designer for .NET Framework”. As mentioned in Lutz email, this option is available in preview feature flags.

How soon can Telerik implement this solution ?

Regards,
Hans

ADMIN
Kalin
Posted on: 06 Feb 2020 14:41

Hello,

After further investigation it appeared the issue is caused by VisualStudio designer and we logged bug report in the Microsoft Developer Community portal:

https://developercommunity.visualstudio.com/content/problem/909297/custom-designmodevalueprovider-works-only-in-the-f.html

Will update the status to Won't Fix for the moment, however as soon as we have more information from MS will share it here and update the status if needed.

Regards,
Kalin
Progress Telerik

Get quickly onboarded and successful with your Telerik and/or Kendo UI products with the Virtual Classroom free technical training, available to all active customers. Learn More.