Diagrama de temas

• .NET QuickStart

  .NET QuickStart

  Content Type
  Exercise

  Duration
  10m

  Level
  Introductory

  InterSystems supports three lightweight .NET APIs that provide direct access to InterSystems IRIS® databases via relational tables, objects, or multidimensional storage.

  .NET features available in InterSystems IRIS include:

  • Relational access through an ADO.NET API
  • Object access through the InterSystems XEP API
  • Access to multidimensional storage through the InterSystems Native SDK
  • Multi-model access to use multiple APIs together
  • Support for third-party APIs such as Entity Framework
  • An underlying consistent structure, avoiding data duplication

  Learning Objectives

  • Explain how ADO.NET, XEP, and the Native SDK can be used to access and manage data in InterSystems IRIS.
  • Use ADO.NET for SQL-based access to relational tables in a .NET application.
  • Implement XEP for high-volume, real-time object insertions into InterSystems IRIS.
  • Determine a suitable strategy using ADO.NET, XEP, and Native SDK for several data-access scenarios.

  
  

  Prerequisites

  None
  
  

  Watch the video and try the exercise below!
• Start the Exercise

  Start the Exercise
  • Launch your lab

    In this exercise, you will work with sample stock data in an InterSystems database using a .NET application.

    
    

  •  You must be logged in to launch an InterSystems IRIS instance.

    • Log in with your existing account.
    • Don't have an InterSystems account? Create a new account.
  • Use the standard ADO.NET API for SQL-based access to relational tables
    

    1. In your lab, open VS Code using the link on the desktop.
    2. Expand project > quickstarts-dotnet > ADO.
    3. Open ADONETplaystocks.cs to view the ADO.NET sample code.
       This code uses the InterSystems IRIS client library for .NET to create, read, update, and delete data within InterSystems IRIS.
    4. Locate the server connection string, which draws connection information from iris-server-config.txt:Begin code.

       connect.ConnectionString = "Server = " + ip + "; Port = " + port + "; Namespace =  " + Namespace + "; Password = " + password + "; User ID = " + username; 

       End code.
    5. Open a Linux terminal in VS Code in the lab by clicking Terminal> New Terminal. Go to the correct directory for this sample with the following command:

       cd quickstarts-dotnet/ADO

    6. Run the ADO.NET sample using the command dotnet run.
       This code simulates a stock trading application, allowing you to manage your personal portfolio and see how you would have done selling on a particular date.
    
    
    7. Interact with the prompt to use the ADO.NET application. Compare the results you see with the code in adoNetPlayStocks.cs to understand how the API is being used. Run the following options:
       • Option 1: View the top 10 stocks on the date 2016/08/12.
       • Option 2: Create the Portfolio table.
       • Option 3: Add three new portfolio items for AMZN, GOOGL, and EQIX, using a value between the opening and closing price on 2016/08/12.
       • Option 6: See how much you would have made on your portfolio if you had sold on 2017/08/10.
       • Option 7: Quit.
  • Use XEP for high performance, real-time object insertions
    

    1. In XEP folder, open xepplaystocks.cs to view the XEP code. You will notice the connection string uses these variables to connect:

       xepPersister.Connect(ip, port, Namespace, username, password); 

    2. In the terminal, change to the XEP directory:

       cd ../XEP

    3. Run the command dotnet run to run the code in xepplaystocks.cs. This code simulates real-time stock trades. Run the following options:
       • Option 1: Make a sample trade.
         For example, trade two shares on 2016/08/12 for $300/share, using your own name as the trader.
       • Option 2: Save this trade.
       • Option 3: Generate 500 generic trades.
       • Option 4: Retrieve the trade objects from the database.
       • Option 6: Update the names to prepend NYSE- to each stock name and retrieve the trade objects from the database again.
       • Option 7: Quit.

    With XEP, you can efficiently stores objects directly to InterSystems IRIS, requiring no translation to rows.

  • Use the Native SDK to store to a custom structure and call InterSystems IRIS methods or routines

    1. In Native SDK directory, open nativeplaystocks.cs to view the Native SDK code.
       Notice the connection string uses these variables to connect:

       connect.ConnectionString = "Server = " + ip + "; Port = " + port + "; Namespace = " + Namespace + "; Password = " + password + "; User ID = " + username;

    2. Run nativeplaystocks.cs from the Native SDK directory. This code stores stock data in a custom data structure. Run the following options:
       • Option 2: Store the stock data in a custom structure.
       • Option 3: Retrieve and view the stock data from this custom structure.
       • Option 4: Call population methods within InterSystems IRIS to generate better information for trades, as seen in the XEP example above.
       • Option 6: Quit.

    With the Native SDK, you can efficiently store data in your own custom data structure, allowing you to answer questions you could not answer using tables or objects.

  • Use ADO.NET, XEP, and Native access side-by-side, choosing the best model for each task
    

    1. In the MultiModel folder, open multimodelplaystocks.cs to see how all APIs work together. You will notice the connection string uses these variables to connect:

       xepPersister.Connect(ip, port, Namespace, username, password);

       Notice this code connects using the XEP connection. Since EventPersister inherits from IRISConnection, all ways to connect leverage the same underlying connection to InterSystems IRIS.
    
    
    2. Run multimodelplaystocks.cs. This code stores information about the stocks of various companies. Run the following options:
       • Option 1: Retrieve quickly all distinct stock names from the Demo.Stock table with ADO.NET.
       • Option 2: Create objects and store them directly to the database with XEP, avoiding any translation back to tables.
       • Option 3: Call population methods within InterSystems IRIS for founder and mission statement with the Native SDK.
       • Option 4: Quit.

    With InterSystems IRIS, you can use one connection to InterSystems IRIS and use the method that is best for each task, decreasing the time it takes to develop your applications while also increasing your application performance. XEP efficiently stores objects directly to InterSystems IRIS, requiring no translation to rows. It is worth it to mention that ADO.NET can also be used to retrieve the data stored using XEP, reducing data redundancy.

• What's Next?

  What's Next?
  • Walk through the sample code in this QuickStart in Stock Trading with .NET (exercise, 1h 30m).
  • Connect your .NET applications to InterSystems products (learning path, 3h)
  • Read more about using .NET with InterSystems software (documentation).

  • Share Your Feedback!