Top
 

PowerShell ADO.NET Provider

  • DataBind to PowerShell commands and scripts using standard Visual Studio wizards.
  • Comprehensive support for CRUD (Create, Read, Update, and Delete) operations.
  • Create powerful .NET applications that can easily consume IT resources through PowerShell scripts!



Picture of PowerShell ADO.NET Provider (Standard)
PowerShell ADO.NET Provider (Standard)
  • DataBind to PowerShell commands and scripts using standard Visual Studio wizards.
  • Comprehensive support for CRUD (Create, Read, Update, and Delete) operations.
  • Create powerful .NET applications that can easily consume IT resources through PowerShell scripts!



*
SKU: RPRA-AD
$299.00
$269.10
Picture of PowerShell ADO.NET Provider (Server)
PowerShell ADO.NET Provider (Server)
  • DataBind to PowerShell commands and scripts using standard Visual Studio wizards.
  • Comprehensive support for CRUD (Create, Read, Update, and Delete) operations.
  • Create powerful .NET applications that can easily consume IT resources through PowerShell scripts!



*
SKU: RPRA-A
$249.00
$224.10

ADO.NET Provider Overview

The PowerShell ADO.NET Provider offers the most natural way to access PowerShell data from any .NET application. Simply use PowerShell Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the PowerShell Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.

Using the PowerShell Data Provider

The PowerShell Data Provider wraps the complexity of accessing PowerShell services in an easy-to-integrate, fully managed ADO.NET Data Provider. Applications then access PowerShell through the PowerShell Data Provider with simple Transact-SQL.

The CData ADO.NET Provider for PowerShell hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Working with DataAdapters, DataSets, DataTables, etc.

The PowerShell Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: PowerShellConnection, PowerShellCommand, PowerShellDataAdapter, PowerShellDataReader, PowerShellDataSource, PowerShellParameter, etc. Because of this you can now access PowerShell data in an easy, familiar way.

For example:

using (PowerShellConnection conn = new PowerShellConnection("...")) {
	string select = "SELECT * FROM powershellscript";
	PowerShellCommand cmd = new PowerShellCommand(select, conn);
	PowerShellDataAdapter adapter = new PowerShellDataAdapter(cmd);
	using (adapter) {
		DataTable table = new DataTable();
		adapter.Fill(table);		
		...
	}
}

More Than Read-Only: Full Update/CRUD Support

PowerShell Data Provider goes beyond read-only functionality to deliver full support for Create, Read Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the PowerShell Data Provider as easily as interacting with a database table.

using (PowerShellConnection connection = new PowerShellConnection(connectionString)) {
	PowerShellDataAdapter dataAdapter = new PowerShellDataAdapter(
	"SELECT Id, Where FROM powershellscript", connection);
  
	dataAdapter.UpdateCommand = new PowerShellCommand(
		"UPDATE powershellscript SET Where = @Where " +
		"WHERE Id = @ID", connection);

	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");

	DataTable powershellscriptTable = new DataTable();
	dataAdapter.Fill(powershellscriptTable);

	DataRow firstrow = powershellscriptTable.Rows[0];
	firstrow["Where"] = "New Location";

	dataAdapter.Update(powershellscriptTable);
}


Driver Features

  • Fully managed .NET: 100% fully managed ADO.NET libraries supporting .NET Framework 2.0 and beyond.
  • Developer Friendly: Seamless integration with all versions of Visual Studio.
  • Powerful ADO.NET Features: Including support for ADO.NET Entity Framework (EF 5 & 6), ADO.NET 2.0, LINQ to Datasets, etc.
  • Replication and Caching: Our replication and caching commands make it easy to copy data to local and cloud data stores such as Oracle, SQL Server, Google Cloud SQL, etc. The replication commands include many features that allow for intelligent incremental updates to cached data.
  • String, Date, Numeric SQL Functions: The driver includes a library of 50 plus functions that can manipulate column values into the desired result. Popular examples include Regex, JSON, and XML processing functions.
  • Collaborative Query Processing: Our drivers enhance the data source's capabilities by additional client side processing, when needed, to enable analytic summaries of data such as SUM, AVG, MAX, MIN, etc.
  • Easily Customizable and Configurable: The data model exposed by our ADO.NET Providers can easily be customized to add or remove tables/columns, change data types, etc. without requiring a new build. These customizations are supported at runtime using human-readable schema files that are easy to edit.
  • Secure Connectivity: Includes standard Enterprise-class security features such as TLS/ SSL data encryption for all client-server communications.

ADO.NET Provider Performance

With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData ADO.NET Provider for PowerShell solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.

Smart Caching

Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.

Caching with our ADO.NET Providers is highly configurable, including options for:

  • Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
  • Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
  • No Cache - All requests access only live data and no local cache file is created.

This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.

More information about ADO.NET Provider caching and best caching practices is available in the included help files.


Getting Started with PowerShell ADO.NET Provider

Working with the new PowerShell ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the PowerShell Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.

 

Visual Studio Integration - Server Explorer

As an ADO.NET Data Provider, PowerShell ADO.NET Provider can be used to access and explore PowerShell data directly from the Visual Studio Server Explorer.


It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to PowerShell ADO.NET Provider just like connecting to any standard database.

  • Add a new Data Connection from the Server Explorer and select the PowerShell Data Source

  • Configure the basic connection properties to access your PowerShell account data.

Explore all of the data available! PowerShell ADO.NET Provider makes it easy to access live PowerShell data from Visual Studio.

  • After configuring the connection, explore the feeds, views, and services provided by the PowerShell Data Source.
  • These constructs return live PowerShell data that developers can work with directly from within Visual Studio!

Winforms DataGrid Integration

Connecting Web, Desktop, and Mobile .NET applications with PowerShell is just like working with SQL Server. It is even possible to integrate PowerShell ADO.NET Provider into applications without writing code.


Developers are free to access the PowerShell ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.

  • Developers can connect the PowerShell Data Source directly to form components by configuring the object's smart tags.

  • Add a new Data Connection from the Server Explorer and select the PowerShell Data Source. Then, select the feed, view, or services you would like to connect the object to.

Done! It's just like connecting to SQL Server.

  • Once the object is bound to the data source, applications can easily interact with PowerShell data with full read/write (CRUD) support.



Product description

ADO.NET Provider Overview

The PowerShell ADO.NET Provider offers the most natural way to access PowerShell data from any .NET application. Simply use PowerShell Data Provider objects to connect and access data just as you would access any traditional database. You will be able to use the PowerShell Data Provider through Visual Studio Server Explorer, in code through familiar classes, and in data controls like DataGridView, GridView, DataSet, etc.

Using the PowerShell Data Provider

The PowerShell Data Provider wraps the complexity of accessing PowerShell services in an easy-to-integrate, fully managed ADO.NET Data Provider. Applications then access PowerShell through the PowerShell Data Provider with simple Transact-SQL.

The CData ADO.NET Provider for PowerShell hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Working with DataAdapters, DataSets, DataTables, etc.

The PowerShell Data Provider has the same ADO.NET architecture as the native .NET data providers for SQL Server and OLEDB, including: PowerShellConnection, PowerShellCommand, PowerShellDataAdapter, PowerShellDataReader, PowerShellDataSource, PowerShellParameter, etc. Because of this you can now access PowerShell data in an easy, familiar way.

For example:

using (PowerShellConnection conn = new PowerShellConnection("...")) {
	string select = "SELECT * FROM powershellscript";
	PowerShellCommand cmd = new PowerShellCommand(select, conn);
	PowerShellDataAdapter adapter = new PowerShellDataAdapter(cmd);
	using (adapter) {
		DataTable table = new DataTable();
		adapter.Fill(table);		
		...
	}
}

More Than Read-Only: Full Update/CRUD Support

PowerShell Data Provider goes beyond read-only functionality to deliver full support for Create, Read Update, and Delete operations (CRUD). Your end-users can interact with the data presented by the PowerShell Data Provider as easily as interacting with a database table.

using (PowerShellConnection connection = new PowerShellConnection(connectionString)) {
	PowerShellDataAdapter dataAdapter = new PowerShellDataAdapter(
	"SELECT Id, Where FROM powershellscript", connection);
  
	dataAdapter.UpdateCommand = new PowerShellCommand(
		"UPDATE powershellscript SET Where = @Where " +
		"WHERE Id = @ID", connection);

	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Where", "Where");
	dataAdapter.UpdateCommand.Parameters.AddWithValue("@Id", "80000173-1387137645");

	DataTable powershellscriptTable = new DataTable();
	dataAdapter.Fill(powershellscriptTable);

	DataRow firstrow = powershellscriptTable.Rows[0];
	firstrow["Where"] = "New Location";

	dataAdapter.Update(powershellscriptTable);
}


Driver Features

  • Fully managed .NET: 100% fully managed ADO.NET libraries supporting .NET Framework 2.0 and beyond.
  • Developer Friendly: Seamless integration with all versions of Visual Studio.
  • Powerful ADO.NET Features: Including support for ADO.NET Entity Framework (EF 5 & 6), ADO.NET 2.0, LINQ to Datasets, etc.
  • Replication and Caching: Our replication and caching commands make it easy to copy data to local and cloud data stores such as Oracle, SQL Server, Google Cloud SQL, etc. The replication commands include many features that allow for intelligent incremental updates to cached data.
  • String, Date, Numeric SQL Functions: The driver includes a library of 50 plus functions that can manipulate column values into the desired result. Popular examples include Regex, JSON, and XML processing functions.
  • Collaborative Query Processing: Our drivers enhance the data source's capabilities by additional client side processing, when needed, to enable analytic summaries of data such as SUM, AVG, MAX, MIN, etc.
  • Easily Customizable and Configurable: The data model exposed by our ADO.NET Providers can easily be customized to add or remove tables/columns, change data types, etc. without requiring a new build. These customizations are supported at runtime using human-readable schema files that are easy to edit.
  • Secure Connectivity: Includes standard Enterprise-class security features such as TLS/ SSL data encryption for all client-server communications.

ADO.NET Provider Performance

With traditional approaches to remote access, performance bottlenecks can spell disaster for applications. Regardless if an application is created for internal use, a commercial project, web, or mobile application, slow performance can rapidly lead to project failure. Accessing data from any remote source has the potential to create these problems. Common issues include:

  1. Network Connections - Slow network connections and latency issues are common in mobile applications.
  2. Service Delays - Delays due to service interruptions, resulting in server hardware or software updates.
  3. Large Data - Intentional or unintentional requests for large amounts of data.
  4. Disconnects - Complete loss of network connectivity.

The CData ADO.NET Provider for PowerShell solves these issues by supporting powerful smart caching technology that can greatly improve the performance and dramatically reduce application bottlenecks.

Smart Caching

Smart caching is a configurable option that works by storing queried data into a local database. Enabling smart caching creates a persistent local cache database that contains a replica of data retrieved from the remote source. The cache database is small, lightweight, blazing-fast, and it can be shared by multiple connections as persistent storage.

Caching with our ADO.NET Providers is highly configurable, including options for:

  • Auto Cache - Maintain an automatic local cache of data on all requests. The provider will automatically load data into the cache database each time you execute a SELECT query. Each row returned by the query will be inserted or updated as necessary into the corresponding table in the cache database.
  • Explicit Cache - Cache only on demand. Developers decide exactly what data gets stored in the cache and when it is updated. Explicit caching provides full control over the cache contents by using explicit execution of CACHE statements.
  • No Cache - All requests access only live data and no local cache file is created.

This powerful caching functionality increases application performance and allows applications to disconnect and continue limited functioning without writing code for additional local storage and/or data serialization/deserialization.

More information about ADO.NET Provider caching and best caching practices is available in the included help files.


Getting Started with PowerShell ADO.NET Provider

Working with the new PowerShell ADO.NET Provider is easy. As a fully-managed .NET Data Provider, the PowerShell Data Provider integrates seamlessly with the Visual Studio development environment as well as any .NET application.

 

Visual Studio Integration - Server Explorer

As an ADO.NET Data Provider, PowerShell ADO.NET Provider can be used to access and explore PowerShell data directly from the Visual Studio Server Explorer.


It's easy. As a standard ADO.NET adapter, developers can connect the Server Explorer to PowerShell ADO.NET Provider just like connecting to any standard database.

  • Add a new Data Connection from the Server Explorer and select the PowerShell Data Source

  • Configure the basic connection properties to access your PowerShell account data.

Explore all of the data available! PowerShell ADO.NET Provider makes it easy to access live PowerShell data from Visual Studio.

  • After configuring the connection, explore the feeds, views, and services provided by the PowerShell Data Source.
  • These constructs return live PowerShell data that developers can work with directly from within Visual Studio!

Winforms DataGrid Integration

Connecting Web, Desktop, and Mobile .NET applications with PowerShell is just like working with SQL Server. It is even possible to integrate PowerShell ADO.NET Provider into applications without writing code.


Developers are free to access the PowerShell ADO.NET Provider in whatever way they like best. Either visually through the Visual Studio Winforms or Webforms designers, or directly through code.

  • Developers can connect the PowerShell Data Source directly to form components by configuring the object's smart tags.

  • Add a new Data Connection from the Server Explorer and select the PowerShell Data Source. Then, select the feed, view, or services you would like to connect the object to.

Done! It's just like connecting to SQL Server.

  • Once the object is bound to the data source, applications can easily interact with PowerShell data with full read/write (CRUD) support.



Additional information
Vendor: CDATA