Error 15216 putting Ultragrid on form

Posted by keesvlasblom on 09-Dec-2010 02:47

Hi all,

When I try to put an Ultragrid on a form in the Designer I get the following error:

Substitution parameters do not conform to the type parameter constraints of Generic class.

Infragistics.Win.Design.SubObjectCodeDomSerializer1[Infragistics.Win.Appearance], Infragistics2.Win.v10.2.Design, Version= 10.2.20102.1004, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb (15216)

Does anyone have a clue what could be wrong and how to solve it?

Regards

Kees Vlasblom

All Replies

Posted by Peter Judge on 09-Dec-2010 09:31

keesvlasblom wrote:

Hi all,

When I try to put an Ultragrid on a form in the Designer I get the following error:

Substitution parameters do not conform to the type parameter constraints of Generic class.

Infragistics.Win.Design.SubObjectCodeDomSerializer1[Infragistics.Win.Appearance], Infragistics2.Win.v10.2.Design, Version= 10.2.20102.1004, Culture=neutral, PublicKeyToken=7dd5c3163f2cd0cb (15216)

Does anyone have a clue what could be wrong and how to solve it?

Regards

Kees Vlasblom

Do you know if it works with the in-the-box UltraControls version ( 2009.2.xxx)?

-- peter

Posted by keesvlasblom on 09-Dec-2010 09:50

Yep, 2009 does work, but 2010.1 and 2010.2 do not.

Kees

Posted by Peter Judge on 09-Dec-2010 10:20

I believe that 10.2B only supports up to 2009.2. I do not know what the support situation is for 2010.x; you may want to check with tech support on that.

-- peter

Posted by DaveBonas on 24-Jan-2011 06:43

Kees,

did you get any response from progress regarding this problem as we are getting the same error having just upgraded from 10.2A to 10.2B. We have been developing within 10.2A using infragistic controls v10.1 for the last 7-8 months but since we upgraded openedge we are now getting the same error number when adding a ultraGrid.

Regards,

Dave

Posted by Wouter Dupré on 24-Jan-2011 06:46

Hi,

Thank you for your email. I'm currently out of the office for a training. I will return on January 28. During my absence I will have no or very limited access to my email. For urgent matters, call me on my mobile and leave a message on my voice mail or call our office.

Best regards,

Wouter

--

Wouter Dupré

Senior Solution Consultant

Progress Software NV

Stocletlaan 202 B| B-2570 Duffel | Belgium

Office +32 (0) 15 30 77 00 | Mobile +32 (0) 478 50 00 49 wdupre@progress.com

Posted by Shelley Chase on 24-Jan-2011 10:28

Any controls that are based on the .NET Framework 3.5 or less are supported. As Peter said, in 10.2x UltraControls are Infragistics 2009.x but you can buy a later version from Infragistics as long as it is based on the correct .NET framework version. I would suggest checking that you do not have a .NET 4.0 based Infragistics controls set. If it is 3.5 or earlier, please log a bug with technical support

Thanks

-Shelley

Posted by DaveBonas on 25-Jan-2011 02:48

Hi Shelly,

As far as I can tell the v10.1 controls are based on the 3.5 framework. We had been using this version of the controls with 10.2A for about 7 months without any issues it was only when we upgraded to 10.2B that we started to get the issues.

I have logged a call with Tech support and it has been confirmed that the error I have been getting was a known issue that was due to be fixed in Openedge 11 due out in December 2011 but we are trying to push for an earlier fix as this seems to be a issue within the progress code and we cannot put our development plans on hold for 12 months.

Regards,

Dave.

Posted by Admin on 25-Jan-2011 02:59

Hi Shelley,

as customer of mine has logged another issue with the 2010 UltraGrid in August (W008050006) and just received the message that the 2010 release of Infragistics is not yet supported. Their issue was related to parsing the ProBindingSource schema in the UltraGrid designer.

The've received the response, the the support for the 2010 UltraGrid is expected for OE11 only.

Is this still the current thinking or will the issue from above call be resolved sooner???

Mike

Posted by DaveBonas on 25-Jan-2011 03:13

Mike,

lets hope it is fixed sooner, just for your info we are getting the error as soon as we add the ultraGrid to a form long before we get to the parsing of the proBindingSource.

Also the error seems to occur on the following components as well which I have reported to Progress as part of the call I raised.

UltraCombo

UltraDropDown

UltraToolbarsManager.

Dave.

Posted by Admin on 25-Jan-2011 03:41

lets hope it is fixed sooner,

Absolutely. It would be adorable especially to use a later version of the Ribbon. That's way overdue!

Posted by Shelley Chase on 25-Jan-2011 10:36

Let me look into this issue. I will post again once I know more details.

-Shelley

Posted by DaveBonas on 26-Jan-2011 02:17

Shelly.

For your info I was dealing with Frank Meulblok at progress when I logged my call.

Dave.

Posted by Admin on 31-Jan-2011 08:34

schase schrieb:

Any controls that are based on the .NET Framework 3.5 or less are supported.

Just checked Infragistics online docs: All 2010 releases from Infragistics are still CLR 2.0 based, with a few exceptions that are .NET 3.0 based (Office 2007 file type support).

Posted by DaveBonas on 31-Jan-2011 08:46

For Every Ones Information....

this bug has been rescheduled to be fixed in the 10.2B04 service packe, due end of March 2011.

Posted by Admin on 31-Jan-2011 12:13

dbo schrieb:

For Every Ones Information....

this bug has been rescheduled to be fixed in the 10.2B04 service packe, due end of March 2011.

Good news! I hope this announcement is for both bugs discussed in this thread.

Posted by Shelley Chase on 31-Jan-2011 15:47

Hi Mike,

I have tried but I may not have found all the related bugs. To make sure please have your customer contact Progress tech support to check. It has been clarified with tech support that we support Infragistics 2010.x as third party controls with 10.2x releases.

Sorry for the confusion.

-Shelley

Posted by Admin on 31-Jan-2011 22:56

Hi Shelley,

I've contacted that customers. Just FYI, the bug number logged in that call was OE00199612

Cheers,

Mike

Posted by Shelley Chase on 01-Feb-2011 14:41

Hi Mike,

That bug looks to be scheduled now for 10.2B04.

-Shelley

Posted by Admin on 01-Feb-2011 14:46

Thanks!

This thread is closed