You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cosmos-db/create-table-dotnet.md
+45-24Lines changed: 45 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ ms.workload:
14
14
ms.tgt_pltfrm: na
15
15
ms.devlang: dotnet
16
16
ms.topic: quickstart
17
-
ms.date: 11/20/2017
17
+
ms.date: 12/01/2017
18
18
ms.author: mimig
19
19
20
20
---
@@ -33,7 +33,7 @@ If you don’t already have Visual Studio 2017 installed, you can download and u
33
33
## Create a database account
34
34
35
35
> [!IMPORTANT]
36
-
> You need to create a new Table API account to work with the generally available Table API SDKs. Table API accounts created during preview are not supported by the generally available SDKs.
36
+
> You must create a new Table API account to work with the generally available Table API SDKs. Table API accounts created during preview are not supported by the generally available SDKs.
@@ -49,17 +49,17 @@ You can now add data to your new table using Data Explorer.
49
49
1. In Data Explorer, expand **sample-table**, click **Entities**, and then click **Add Entity**.
50
50
51
51

52
-
2. Now add data to the PartitionKey value box and RowKey value boxes, and click **Add Entity**.
52
+
2. Now add data to the PartitionKey value box and RowKey value box, and click **Add Entity**.
53
53
54
54

55
55
56
-
You can now add more entities to your table, edit your entities, or query your data in Data Explorer. Data Explorer is also where you can scale your throughput and add stored procedures, userdefined functions, and triggers to your table.
56
+
You can now add more entities to your table, edit your entities, or query your data in Data Explorer. Data Explorer is also where you can scale your throughput and add stored procedures, user-defined functions, and triggers to your table.
57
57
58
58
## Clone the sample application
59
59
60
-
Now let's clone a Table app from github, set the connection string, and run it. You'll see how easy it is to work with data programmatically.
60
+
Now let's clone a Table app from GitHub, set the connection string, and run it. You'll see how easy it is to work with data programmatically.
61
61
62
-
1. Open a git terminal window, such as git bash, and use the `cd` command to change to a folder to install the sample app.
62
+
1. Open a Git terminal window, such as Git Bash, and use the `cd` command to change to a folder to install the sample app.
63
63
64
64
```bash
65
65
cd"C:\git-samples"
@@ -70,71 +70,92 @@ Now let's clone a Table app from github, set the connection string, and run it.
3. Then open the TableStorage solution file in Visual Studio.
75
+
1. In Visual Studio, from the **File** menu, choose **Open**, then choose **Project/Solution**.
76
+
77
+

78
+
79
+
2. Navigate to the folder where you cloned the sample application, and open the TableStorage.sln file.
80
+
81
+

75
82
76
83
## Update your connection string
77
84
78
85
Now go back to the Azure portal to get your connection string information and copy it into the app. This enables your app to communicate with your hosted database.
79
86
80
87
1. In the [Azure portal](http://portal.azure.com/), click **Connection String**.
81
88
82
-
Use the copy buttons on the right side of the screen to copy the PRIMARY CONNECTION STRING.
89
+
Use the copy button on the right side of the window to copy the **PRIMARY CONNECTION STRING**.
83
90
84
91

85
92
86
93
2. In Visual Studio, open the App.config file.
87
94
88
-
3. Uncomment the StorageConnectionString on line 8 and comment out the StorageConnectionString on line 7 as this tutorial does not use the Storage Emulator. Line 7 and 8 should now look like this:
95
+
3. Uncomment the StorageConnectionString on line 8 and comment out the StorageConnectionString on line 7, because this tutorial does not use the Azure SDK Storage Emulator. Lines 7 and 8 should now look like this:
4. Paste the PRIMARY CONNECTION STRING from the portal into the StorageConnectionString value on line 8. Paste the string inside the quotes.
102
+
4. Paste the **PRIMARY CONNECTION STRING** from the portal into the StorageConnectionString value on line 8. Paste the string inside the quotes.
96
103
97
104
> [!IMPORTANT]
98
-
> If your Endpoint uses documents.azure.com, that means you have a preview account, and you need to create a [new Table API account](#create-a-database-account) to work with the generally available Table API SDK.
105
+
> If your Endpoint uses documents.azure.com, that means you have a preview account, and you must create a [new Table API account](#create-a-database-account) to work with the generally available Table API SDK.
3. Click **Install** to install the **Microsoft.Azure.CosmosDB.Table** library. This installs the Azure Cosmos DB Table API package and all dependencies.
116
128
117
-
3. From the results, install the **Microsoft.Azure.CosmosDB.Table** library. This installs the Azure Cosmos DB Table API package as well as all dependencies.
If you get an error about dependencies, see [Troubleshooting](table-sdk-dotnet.md#troubleshooting).
126
142
127
-
When you hit the first breakpoint, go back to Data Explorer in the Azure portal and expand the demo* table and click **Entities**. The **Entities** tab on the right shows the new entity that was added, note that phone number for the user is 425-555-0101.
143
+
When you hit the first breakpoint, go back to Data Explorer in the Azure portal. Click the **Refresh** button, expand the demo* table, and click **Entities**. The **Entities** tab on the right shows the new entity that was added for Walter Harp. Note that the phone number for the new entity is 425-555-0101.
7. Continue to run the app to the next breakpoint.
149
+
7. Press F5 to run the app to the next breakpoint.
132
150
133
-
When you hit the breakpoint, switch back to the portal, click Entities again to open the Entities tab, and note that the phone number has been updated to 425-555-0105.
151
+
When you hit the breakpoint, switch back to the Azure portal, click **Entities** again to open the **Entities** tab, and note that the phone number has been updated to 425-555-0105.
134
152
135
-
8. Back in the console window, press CTRL + C to end the execution of the app.
153
+
8. Press F5 to run the app.
154
+
155
+
The app adds entities for use in an advanced sample app that the Table API currently does not support. The app then deletes the table created by the sample app.
136
156
137
-
You can now go back to Data Explorer and add or modify the entitites, and query the data.
157
+
9. In the console window, press Enter to end the execution of the app.
Copy file name to clipboardExpand all lines: articles/time-series-insights/time-series-insights-manage-reference-data-csharp.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title: Manage reference data in Azure Time Series Insights environment by using C# | Microsoft Docs
2
+
title: Manage reference data in Azure Time Series Insights environment using C# | Microsoft Docs
3
3
description: This article describes how to manage reference data for an Azure Time Series Insights environment by creating a custom application written in the C# (c-sharp) .NET language.
0 commit comments