Last Updated: 08 Sep 2016 08:25 by Luigi
Created on: 27 Nov 2015 11:34
Category: GridView
Type: Bug Report
FIX. RadGridView - the default ContextMenu and ContextMenuStrip properties are not working.
To reproduce:
- Assing context menu using one of the default properties.
Posted on: 08 Sep 2016 08:25
In 2016 Q2 the solution posted by Ralitsa Kumanova works.
Posted on: 27 May 2016 06:12
@Robyn - I would agree with your position. Indeed, we should have explained what should be done to have the menus working. 
What happened here is that RadGridView has its own context menus for different type of elements. And when a ContextMenuStrip was assigned both context menus were shown. In order to resolve this, we introduced properties to disable the grid context menus, so one can show only the ContextMenuStrip.

I agree this is inconvenient and if you have difficulties setting these properties in your project in order to upgrade, I would suggest contacting our support staff that can assist in this matter.

@Slawa - I am happy to see you are satisfied with this solution. Unfortunately, I am unable to understand everything you said, so I would ask to translate it in English should you need a reply from us.

Stefan Stefanov
Posted on: 26 May 2016 07:40
Спасибо огромное за помощь!
Не ожидал, что на мой комментарий так быстро ответят и дадут решение!
Я поставил:
this.rgv.AllowCellContextMenu = false; 
this.rgv.AllowColumnHeaderContextMenu = false;
Стандартное меню снова заработало!

А свойство this.radGridView2.AllowRowHeaderContextMenu в окне свойств даже не отображается, поэтому я его не трогал.

Благодарю вас всех!
Posted on: 25 May 2016 22:59
Slawa, there is more discussion on this here:

This issue was never completely "resolved" in Q1 2016 - Telerik did fix something but whilst doing so they decided to make a functional change to the way these menus work, which DOES require a bunch of refactoring of code our end to support.

As a result of this we are also still sitting back on a old 2015 release version of these controls and have not renewed our license as we don't have the resources to implement all the code changes required to update to 2016
Posted on: 25 May 2016 14:51
Hi Slawa, 

In order to enable the ContextMenu or ContextMenuStrip, you need to disable the default context menu of RadGridView. If you use Telerik UI for Winforms, version R2 2016 (2016.2.503), please refer to the code snippet below how to achieve it: 
this.radGridView2.AllowCellContextMenu = false;
this.radGridView2.AllowRowHeaderContextMenu = false;
this.radGridView2.AllowColumnHeaderContextMenu = false;

In the attachments you can find a sample project how to apply it ( 
Posted on: 25 May 2016 09:39
Sorry, but me there is no time to carry out discussion here. I have just reported that such problem is, since 2016 Q1. At the moment it is a serious obstacle to transition to the new version since it is necessary to transfer everything to RadContextMenu.
Posted on: 25 May 2016 09:28
May I please ask to open a support ticket and discuss the precise case with our support staff. If need be, they will reopen the case accordingly.
Posted on: 25 May 2016 09:12
ContextMenuStrip doesn't work neither in 2016 Q1, nor in 2016 Q2.
Works in 2015 Q3.
I checked only yesterday!
Posted on: 25 May 2016 09:03
Hi Slawa, 

this case has been resolved in Q1 2016 - see the Status and the Scheduled for fields on the right side. 

Feel free to upgrade to our latest version in order to take advantage of the fix.
Posted on: 24 May 2016 08:28
Awful mistake! Please, correct, too much code is required to be rewritten to make everything as was!
Posted on: 03 Dec 2015 07:15
Great to hear you are not in a rush. 
All the best.
Posted on: 02 Dec 2015 23:32
Thanks Stefan,

We just don't have the resources to re-do our context menus as RadContextMenus at this stage. The wait for Q12016 to re-evaluate is acceptable as we are not needing to update urgently!
Posted on: 02 Dec 2015 16:09
Hi Robyn,

you can cast a vote for an item by using the Like button, as you suggested.

I was wondering why this is a roadblock for you? Didn't you manage to work around it with the support officer you communicated? You can discuss possible workarounds with him (if such are available) so you can move forward with your project and not wait for the Q1 2016 release.
Posted on: 01 Dec 2015 20:44
Thanks! I can see this is marked as Completed and Scheduled for the Q1 2016 release. We'll reassess that version when available and renew our license if it all looks good. Thanks again ;)
Posted on: 29 Nov 2015 22:25
Not sure how to 'vote' for this fix! But I 'liked' it and I'll comment. This is currently the roadblock to renewing our license for the latest version. Thanks