Replacement for Extenders? Trying to get away from OCX development.

We are in the process of finally upgrading to 15.

I am wondering if there is a new preferred method of developing extenders or a replacement method to using OCXs? I would much prefer to use .Net

Any pointers or links to documentation would be much appreciated.

TIA

J

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

It really depends on what

It really depends on what your Xtenders are doing. 

In terms of .NET development, you can create iParts and plug them into your webpages using WCM. 
There is plenty of information on the imiscommunity on iParts. 

These don't really replace the traditional OCX Xtenders that are used within the iMIS Desktop though. Customers that I work with continue to use traditional Xtenders within the iMIS desktop. For example, ID tracker, Event Closer, Customer Service Alerts etc.

 Leo

 

iParts

iParts are the intended successor to Xtender.  They work well, but there are some important differences:

  • An Xtender can open once and stay open as you change screens in iMIS.  iParts only live on the pages where you place them, so if you need it on two pages, you have to add it to both pages.
  • Xtenders only work in the desktop (Omnis7-based application).  iParts can work in both the desktop and the staff web view (casual view).
  • Xtenders receive events to indicate that something happened.  The events are the same from any part of iMIS.  iParts can communicate with other iParts on the same page.  Both iParts must be capable of communicating for this to work.

--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.