Welcome to the PowerScript Bridge API Reference!
This document provides API reference of the 1.0.x release of PowerScript Bridge (PowerScript.Bridge).
This readme page will prepare you for getting a better usage of this API Reference document. It contains the recommendation for acquiring a basic understanding of the C# language, and also brief instructions for understanding the document structure.
Why DataStore functions in PowerScript.Bridge
The DataStore functions included in PowerScript.Bridge are for non-generic .NET DataStore. They are used only by the C# scripts migrated from PowerScript, and thus are not recommended for new development. For new developments, you should use the generic .NET DataStore in DWNet.Data.
If you have done development before, but are new to C#, we recommend you thoroughly read through the following Microsoft .NET documents first to get a basic understanding of the C# language and .NET development.
A Tour of the C# Language: It provides an overview of the language. It covers the elements that make up C# programs and the capabilities of the language. It shows small samples of all the syntax elements of C# and discussions of the major C# language topics. After reading this, you will have answers to the following questions:
- What is an attribute? What is the difference between an attribute and a property?
- What is the difference between List, Array, and Dictionary?
- What is Data Context?
- What are the differences between a class and a structure?
- What is a namespace? What is an assembly?
- What is a delegate? How to use delegate with events?
- What is the difference between “int” and “system.Int32”
Introduction to C# Tutorials: It provides interactive tutorials for brand-new developers to explore and learn the C# language in the browser using a Read-Eval-Print Loop (REPL) interface. The tutorials provide a step-by-step process to create C# programs. They show the language concepts and how to build C# programs on your own. After you finish the interactive lessons, you can improve your coding skills by practicing the same lessons on your machine.
How the API Reference is organized
The APIs are listed in the following order: first the package by alphabetical order, then the category for the frequently-used objects of the same type or functionalities (such as DataObject, DataStore etc.), and finally the public APIs (if any) by alphabetical order.
So if you want to view all APIs related with DataStore, you expand the DataStore tree item to view the list; and you will find not only IDataStore and DataStore under the tree item, but also a bunch of subsidiary APIs for implementing DataStore.
Some base classes/interfaces are for internal use only, so the only available documentation for it is its derived classes/interfaces.
IDataObject (interface) vs. DataObject (class)
When you explore the APIs, you may find two categories with similar name, for example, IDataObject vs. DataObject. The APIs starting with the letter “I” is an interface (“I” short for “interface”); and the ones without the “I” are classes. The class (e.g. DataObject) implements the interface (e.g. IDataObject). So normally the class only contains documentation for constructors, while the interface contains documentation for methods and properties.
.NET-style page layout
The API Reference presents a page layout which is consistent with the Microsoft .NET API documents, for example, each API page has the same sections as the Microsoft .NET API page; if a method has no return value, the Return section does not appear in the document either.
Filter or Search
There are two ways to search in the API Reference:
- Filter: You input the API name in the Filter text box on top of the left navigation pane, to let the navigation list filter out the APIs matching with your input. The filter function works better when you know the API name (or part of the API name).
- Search: If you want to search for any keyword (not just API names), then you would need to use the Search box on the top right corner. The search function will search all Appeon C# documents (not just API Reference).