Ready to get started?

Learn more about the CData ADO.NET Provider for PowerShell or download a free trial:

Download Now

LINQ to PowerShell Scripts

LINQ provides general-purpose query facilities in .NET Framework 3.0 and above and provides one easy way to programmatically access data through from CData ADO.NET Data Providers. This example uses LINQ to access information from the PowerShell Data Provider.

This article demonstrates how to use LINQ to access PowerShell tables through the CData ADO.NET Data Provider for PowerShell. To do this you will LINQ to Entity Framework, which is used to generate the connection and can be used with any CData ADO.NET Data Providers to access data via LINQ.

See the help documentation for a guide to setting up an EF 6 project to use the provider.

  1. In a new project in Visual Studio, right-click on the project and choose to add a new item. Add an ADO.NET Entity Data Model.
  2. Choose EF Designer from Database and click Next.
  3. Add a new Data Connection, and change your data source type to "CData PowerShell Data Source".
  4. Enter your data source connection information.

    The ScriptLocation, under the Data section, must be set to a valid script location.

    Below is a typical connection string:

    ScriptLocation='%Public%\Documents\CData PowerShell Scripts';ExecuteQuery=True;
  5. If saving your entity connection to App.Config, set an entity name. In this example we are setting PowerShellEntities as our entity connection in App.Config.
  6. Enter a model name and select any tables or views you would like to include in the model.

Using the entity you created, you can now perform select , update, delete, and insert commands. For example:

PowerShellEntities context = new PowerShellEntities(); var processQuery = from process in context.Process select process; foreach (var result in processQuery) { Console.WriteLine("{0} {1} ", result.Id, result.ProcessName); }

See "LINQ and Entity Framework" chapter in the help documentation for example queries of the supported LINQ.