Microsoft KB Archive/314775

= INFO: Migrating Visual InterDev Design-Time Controls to ASP.NET =

Article ID: 314775

Article Last Modified on 2/23/2007

-

APPLIES TO


 * Microsoft ASP.NET 1.1
 * Microsoft ASP.NET 1.0
 * Microsoft Visual InterDev 6.0 Standard Edition

-



This article was previously published under Q314775



SUMMARY
This article describes how to migrate Microsoft Visual InterDev Design-Time Controls (DTCs) to ASP.NET Web server controls and HTML server controls.

For general information about how to migrate Microsoft Active Server Pages (ASP) pages, refer to the &quot;References&quot; section.



MORE INFORMATION
Microsoft Visual InterDev 6.0 includes 22 design-time controls.  Seven of these controls have equivalent ASP.NET server controls:  Button CheckBox Grid Label ListBox OptionGroup</li> TextBox</li></ul>

</li> Two of these controls have other equivalent ASP.NET features: <ul> Include</li> PageObject</li></ul>

</li> Three of these controls are Microsoft Visual InterDev 1.0 DTCs that are included in Visual InterDev 6.0 only for backward compatibility. Other DTCs replace their functionality in Visual InterDev 6.0. <ul> Data Command</li> Data Range Header</li> Data Range Footer</li></ul>

</li> Ten of these controls require that you write custom code to migrate to ASP.NET: <ul> FormManager</li> Layout Header Start</li> Layout Header End</li> Layout Footer Start</li> Layout Footer End</li> PageNavBar</li> <li>PageTransitions</li> <li>Recordset</li> <li>RecordsetNavBar</li> <li>Timelines</li></ul> </li></ul>

For additional information about ASP.NET server controls, click the article number below to view the article in the Microsoft Knowledge Base:

306459 INFO: ASP.NET Server Controls Overview

For DTCs that do not have equivalent features in ASP.NET, you can keep pages that use these DTCs as ASP pages in your ASP.NET application. You can then share session state and application state between the ASP pages and the ASP.NET pages with cookies, form fields, query strings, or a database.

Button DTC
To migrate pages that use the Button DTC to ASP.NET, use the Button Web server control or the HtmlButton control.

back to the top

CheckBox DTC
To migrate pages that use the CheckBox DTC to ASP.NET, use the CheckBox Web server control or the HtmlInputCheckBox control.

For additional functionality that is not available in the CheckBox DTC, you can also use a CheckBoxList Web server control to create a multiselection check box group.

back to the top

<span id="Data_Command" class="bookmark"> Data Command DTC
Visual InterDev 6.0 includes the Data Command DTC for backward compatibility with Visual InterDev 1.0. Visual InterDev 6.0 replaces the functionality of the Data Command DTC with the Recordset DTC. The Data Command DTC is not added to the Visual InterDev 6.0 toolbox by default. You must use the Customize Toolbox dialog box to add this DTC.

ASP.NET does not include a server control or other feature that is equivalent to the Data Command DTC. To migrate pages that use Data Command DTCs, follow these steps:
 * 1) Write ADO.NET code that creates DataView, DataSet, or DataReader objects.
 * 2) Set the DataSource properties of the data-bound Web Forms controls to the objects from step 1.
 * 3) Call the DataBind methods of the controls from step 2.

back to the top

<span id="Data_Range" class="bookmark"> Data Range Header and Data Range Footer DTCs
Visual InterDev 6.0 includes the Data Range Header and the Data Range Footer DTCs for backward compatibility with Visual InterDev 1.0. Visual InterDev 6.0 replaces the functionality of these DTCs with the Grid DTC. The Data Range Header and the Data Range Footer DTCs are not added to the Visual InterDev 6.0 toolbox by default. You must use the Customize Toolbox dialog box to add these DTCs.

To migrate pages that use Data Range Header and Data Range Footer, use the DataGrid Web server control.

back to the top

FormManager DTC
ASP.NET does not include a server control or other feature that is equivalent to the FormManager DTC. To migrate pages that use the FormManager DTC, you must write ASP.NET code that automates all necessary events.

back to the top

Grid DTC
To migrate pages that use the Grid DTC to ASP.NET, use the DataGrid Web server control.

back to the top

Include DTC
ASP.NET does not include a server control that is equivalent to the Include DTC. The Include DTC is not added to the Visual InterDev 6.0 toolbox by default. You must use the Customize Toolbox dialog box to add this DTC.

To migrate pages that use Include DTCs, encapsulate the functionality of the include file in an ASP.NET Web Forms user control.

For more information about Web Forms user controls, refer to the following topic in the .NET Framework Developer's Guide:

Web Forms User Controls

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpconwebformsusercontrols.asp

Alternately, you can use an ASP server-side include directive. For example:

For more information on ASP server-side include directives, refer to the following MSDN documentation:

Including Files

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iissdk/iis/includingfiles.asp

back to the top

Label DTC
To migrate pages that use the Label DTC to ASP.NET, use the Label Web server control or the HtmlGeneric control.

back to the top

Layout Header Start, Layout Header End, Layout Footer Start, and Layout Footer End DTCs
ASP.NET does not include features that are equivalent to the Visual InterDev Layouts. In addition, ASP.NET does not include server controls or other features that are equivalent to the Layout Header Start, the Layout Header End, the Layout Footer Start, and the Layout Footer End DTCs.

These DTCs are not added to the Visual InterDev 6.0 toolbox by default. You must use the Customize Toolbox dialog box to add these DTCs. In addition, these controls are added to pages automatically when you use Layouts.

To migrate pages that use these DTCs, use one of the following options:
 * Use the HyperLink or the Button Web server control.
 * Create HTML hyperlinks that are set to run as server controls.
 * Use the HtmlButton control.

back to the top

ListBox DTC
To migrate pages that use the ListBox DTC to ASP.NET, use one of the following controls:
 * ListBox Web server control
 * DropDownList Web server control
 * HtmlSelect control

back to the top

OptionGroup DTC
To migrate pages that use the OptionGroup DTC to ASP.NET, use one of the following controls:
 * RadioButton Web server control
 * RadioButtonList Web server control
 * HtmlInputRadioButton control

back to the top

PageNavBar DTC
ASP.NET does not include a feature that is equivalent to Visual InterDev Site Diagrams. In addition, ASP.NET does not include a server control or other feature that is equivalent to the PageNavBar DTC.

To migrate pages that use PageNavBar DTCs, use one of the following options:
 * Use the HyperLink or the Button Web server control.
 * Create HTML hyperlinks that are set to run as server controls.
 * Use the HtmlButton control.

back to the top

PageObject DTC
ASP.NET does not include a server control that is equivalent to the PageObject DTC. To migrate pages that use PageObject DTCs, create an ASP.NET Web service. To call an ASP.NET Web Service from client-side script, use a WebService behavior.

For more information about ASP.NET Web services, refer to the &quot;ASP.NET Web Service Projects in Visual Studio&quot; topic in the Microsoft Visual Studio .NET Online Help documentation.

For more information on WebService behaviors, refer to the following MSDN documentation:

About the WebService Behavior

http://msdn.microsoft.com/library/default.asp?url=/workshop/author/webservice/overview.asp

back to the top

PageTransitions DTC
ASP.NET does not include a server control or other feature that is equivalent to the PageTransitions DTC. To migrate pages that use PageTransitions DTCs, use the revealTrans filter in an HTML <META> tag. For example: <META HTTP-EQUIV=&quot;Page-Enter&quot; CONTENT=&quot;revealTrans(Duration=2,Transition=3)&quot;> For more information about the revealTrans filter, refer to the following MSDN documentation:

RevealTrans Filter

http://msdn.microsoft.com/library/default.asp?url=/workshop/author/filter/reference/filters/revealtrans.asp?frame=true

back to the top

Recordset DTC
ASP.NET does not include a server control or other feature that is equivalent to the Recordset DTC. To migrate pages that use Recordset DTCs, follow these steps:
 * 1) Write ADO.NET code that creates DataView, DataSet, or DataReader objects.
 * 2) Set the DataSource properties of the data-bound Web server controls to the objects from step 1.
 * 3) Call the DataBind methods of the page or of the controls from step 2.

back to the top

RecordsetNavBar DTC
ASP.NET does not include a server control or other feature that is equivalent to the RecordsetNavBar DTC. To migrate pages that use RecordsetNavBar DTCs, follow these steps:
 * 1) Use Button Web server controls or HtmlButton controls.
 * 2) Write ADO.NET code in the Click events of these buttons to control DataView, DataSet, or DataReader navigation.

back to the top

TextBox DTC
To migrate pages that use the TextBox DTC to ASP.NET, use one of the following controls:
 * TextBox Web server control
 * HtmlTextArea control
 * HtmlInputText control

back to the top

Timelines DTC
ASP.NET does not include a server control or other feature that is equivalent to the Timelines DTC. To migrate pages that use Timelines DTCs, use the JScript SetTimeout or SetInterval method in client-side script.

back to the top

<div class="references_section">