Abstract: A data source extensibility model establishes extensibility points to allow a data source window or integrated development environment to work with new data source providers and/or new designer technologies and/or new UI controls. Various object/entity management techniques are provided to orchestrate which component is present in given conditions.

Abstract: A system and method that facilitate data access in a software development environment is provided. The system generates strongly typed objects that encapsulate raw, untyped data access logic and groups together like database commands in a common data access component. The system provides a mapping between database types and common language runtime data types including the impedance mismatch of null representations. The system configures data access component(s) that are employed at design-time to facilitate access to data object(s) by application(s) and allows a user of the configured data access component(s) to improve developer productivity and/or reduce the quantity of runtime errors introduced into code. The data access component can be instanced on multiple forms components and/or with the developer's own class(es). Thus, change(s) to a query and/or interface are accomplished within the data access component and be available to the forms components and/or object(s) that utilize the data access component.

Abstract: Form controls can be reused so that the control can be bound to large volumes of data without adverse performance issues because of a large number of controls. A maximum number of rows of data N that can appear in a form are calculated. A container in memory is created for N+2 rows. The additional two rows are used to store the row after the last displayed row and the row previous to the first displayed row. In response to a user scroll or tab operation, rows within the container are reused. Child controls are hosted by the control and are also reused when the data is scrolled out of view.

Abstract: A mechanism for converting control types in a user interface (UI) development framework. The framework includes a UI generation component that facilitates the development of the UI in which control types will be employed and bound to data of a data source. In communication with the generation component is a conversion component that facilitates changing the default control choice immediately after creation, or for evaluating the UI, and later choosing to change the UI control choice. The conversion component employs a service to inspect all controls on a particular form in the designer, and advertises a “Change To” or similar smart tag item for that control, if the control supports data binding and conversions. Selection of the control type or control group view creates the UI of the user's choice, and intelligently maps all control properties and data bindings across the conversion.

Abstract: A system and method for a reentrant database object wizard is provided. The system provides the ability to compare a currently generated dataset to the objects of the underlying database. Columns and tables that are not common between both the dataset and the database are visually displayed for the user to make a decision on inclusion or exclusion. The system includes a comparison that provides comparison information based upon a comparison of a dataset to an associated database and a display component that displays the comparison information. The system further includes an input component which provides information associated with the user's decision on inclusion and/or exclusion of column(s) and/or table(s) to the system. The system is reentrant thus providing long-term value to the developer over the application development cycle.

Abstract: An interface may be provided that enables the user to select a parent list, to view a set of available child lists corresponding to the selected parent list, and to select a particular child list from the set of available child lists. The set of available child lists may be automatically compiled in response to the selection of the parent list. Another interface may be provided that enables the user to select a particular portion of the parent list for which to view corresponding child data. The corresponding child data may be automatically identified and displayed in a running application.

Abstract: A user interface is provided that exposes items such as developer tasks, commands, property settings, and other related information to a user. The user interface may be invoked in a number of development interfaces such as, for example, a designer or an editor. The user interface may be either an object bound interface or an action triggered interface. An object bound interface exposes a set of items that are associated with a corresponding object. An action triggered interface exposes a set of items that are associated with a corresponding triggering action. In addition to enumerating developer tasks, the user interface may provide a direct link to other interfaces that facilitate task execution.

Abstract: Visual controls such as drag and drop are utilized to create object-oriented constructs from corresponding relational constructs, for instance. Similarly, an object-relational map can be generated between the relational constructs and the created object-oriented constructs to facilitate interaction across disparate programmatic models.

Abstract: A development system is provided. The system includes a workspace component to visually display one or more class components. A linking component identifies a database relationship between at least two of the class components, where the database relationship is employed to automatically create a class association between the at least two class components.

Abstract: A development system is provided. The system includes a workspace component to visually display one or more stored procedures and one or more class components. A manipulation component locates the stored procedures onto the class components in order to automatically create methods for the class components.

Abstract: A system and method for a reentrant database object wizard is provided. The system provides the ability to compare a currently generated dataset to the objects of the underlying database. Columns and tables that are not common between both the dataset and the database are visually displayed for the user to make a decision on inclusion or exclusion. In addition, columns and tables that were previously within the dataset that are no longer available on the database connection are displayed, for example, with warning icons so that the user can either resolve the missing column or table within the database, or remove the column/table from their typed dataset. The system includes a comparison component and a display component. The comparison component provides comparison information based upon a comparison of a dataset to an associated database. The display component displays the comparison information.

Abstract: A system and method that facilitate data access in a software development environment is provided. The system generates strongly typed objects (e.g., TableAdapter(s)) that encapsulate raw, untyped data access logic, for example, via generated wrapped method(s). The system can group together like database commands in a common data access component. For example, the TableAdapter can encapsulate a configured DataAdapter and expose public method(s) for the “Fill” and “Update” methods normally found on the DataAdapter. The system provides a mapping between database types and common language runtime data types including the impedance mismatch of null representations. The system includes a data access configuration component (e.g., configuration wizard) that configures data access component(s) (e.g., TableAdapter(s)). The configured data access component(s) can be employed at design-time to facilitate access to data object(s) (e.g., database(s)) by application(s).

Abstract: A rich user interface (UI) development framework that uses the schema of a data source to which it is relevant. The developer is able to rapidly create a data bound UI using a number of familiar gestures, including drag and drop, from the schema in a data tool window, using a designer tasks, or using a data form creation wizard. The system includes a UI generation component that allows a developer to input a number of different controls into the interface using associated control graphics. A data source object, type, or file can be passed to the UI generation component as an input. The developer chooses the desired controls and associates (or binds) the data entity of the data source with the control by any number of gestures.

Abstract: An interface may be provided that enables the user to select a parent list, to view a set of available child lists corresponding to the selected parent list, and to select a particular child list from the set of available child lists. The set of available child lists may be automatically compiled in response to the selection of the parent list. Another interface may be provided that enables the user to select a particular portion of the parent list for which to view corresponding child data. The corresponding child data may be automatically identified and displayed in a running application.

Abstract: A user interface is provided that exposes items such as developer tasks, commands, property settings, and other related information to a user. The user interface may be invoked in a number of development interfaces such as, for example, a designer or an editor. The user interface may be either an object bound interface or an action triggered interface. An object bound interface exposes a set of items that are associated with a corresponding object. An action triggered interface exposes a set of items that are associated with a corresponding triggering action. In addition to enumerating developer tasks, the user interface may provide a direct link to other interfaces that facilitate task execution.

Abstract: A logical view of a data source may be provided. The data source may include a number of data source objects organized according to a data source schema. The data source schema may be retrieved or inferred, and the data source objects may be identified from the data source schema. A logical relationship between the data source objects may be determined based on the data source schema. A logical view of the data source that shows the logical relationship between the data source objects may be displayed. The display may include a tree structure with nodes that correspond to data source objects.

Abstract: A user may select a dataset and choose whether to select an existing parameterized query or to define a new parameterized query to execute upon the selected dataset. If the user chooses to select an existing parameterized query, then a set of existing parameterized queries corresponding to the dataset may be identified and displayed to the user. If the user chooses to define a new parameterized query, then the new parameterized query may easily be merged into the set of existing parameterized queries corresponding to the dataset. In response to the generation of a parameterized query, input fields may be readily provided that enable the user to set the value of query parameters. Thus, the user may easily and efficiently add searching and filtering capabilities in connection with an application.

Abstract: A mechanism for converting control types in a user interface (UI) development framework. The framework includes a UI generation component that facilitates the development of the UI in which control types will be employed and bound to data of a data source. In communication with the generation component is a conversion component that facilitates changing the default control choice immediately after creation, or for evaluating the UI, and later choosing to change the UI control choice. The conversion component employs a service to inspect all controls on a particular form in the designer, and advertises a “Change To” or similar smart tag item for that control, if the control supports data binding and conversions. Selection of the control type or control group view creates the UI of the user's choice, and intelligently maps all control properties and data bindings across the conversion.