Skip to content

Commit 65f5545

Browse files
Merge pull request #98281 from PatAltimore/patricka-blockchain-devkit
Blockchain dev kit changes
2 parents 4ba594f + 284a097 commit 65f5545

18 files changed

+32
-108
lines changed

articles/blockchain/service/connect-vscode.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Use Visual Studio Code to connect to Azure Blockchain Service
33
description: Connect to an Azure Blockchain Service consortium network using the Azure Blockchain Development Kit for Ethereum extension in Visual Studio Code
4-
ms.date: 11/19/2019
4+
ms.date: 12/05/2019
55
ms.topic: quickstart
66
ms.reviewer: chrisseg
77
#Customer intent: As a developer, I want to connect to my blockchain consortium so that I can perform actions on a blockchain.
@@ -55,12 +55,12 @@ You can connect to consortium members using the Azure Blockchain Development Kit
5555
If you don't have access to an Azure Blockchain Service consortium member, complete the prerequisite [Quickstart: Create a blockchain member using the Azure portal](create-member.md) or [Quickstart: Create an Azure Blockchain Service blockchain member using Azure CLI](create-member-cli.md).
5656

5757
1. In the VS Code explorer pane, expand the **Azure Blockchain** extension.
58-
1. Select **Connect to Consortium**.
58+
1. Select **Connect to network**.
5959

60-
![Connect to consortium](./media/connect-vscode/connect-consortium.png)
60+
![Connect to network](./media/connect-vscode/connect-consortium.png)
6161

6262
If prompted for Azure authentication, follow the prompts to authenticate using a browser.
63-
1. Choose **Connect to Azure Blockchain Service consortium** in the command palette dropdown.
63+
1. Choose **Azure Blockchain Service** in the command palette dropdown.
6464
1. Choose the subscription and resource group associated with your Azure Blockchain Service consortium member.
6565
1. Choose your consortium from the list.
6666

articles/blockchain/service/data-manager-cosmosdb.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,15 @@ The contract ABI defines the smart contract interfaces. It describes how to inte
7373

7474
1. Save the **abi** array as a JSON file. For example, *abi.json*. You use the file in a later step.
7575

76-
Blockchain Data Manager requires the deployed bytecode for the smart contract. The deployed bytecode is different than the smart contract bytecode. You can get the deployed bytecode from the compiled contract metadata file.
76+
Blockchain Data Manager requires the deployed bytecode for the smart contract. The deployed bytecode is different than the smart contract bytecode. You use the Azure blockchain development kit extension to copy the bytecode to the clipboard.
7777

78-
1. Open the contract metadata file contained in the **build/contracts** folder of your Solidity project. The file name is the smart contract name followed by the **.json** extension.
79-
1. Find the **deployedBytecode** element in the JSON file.
80-
1. Copy the hexadecimal value without the quotes.
78+
1. In the Visual Studio Code explorer pane, expand the **build/contracts** folder of your Solidity project.
79+
1. Right-click the contract metadata JSON file. The file name is the smart contract name followed by the **.json** extension.
80+
1. Select **Copy Transaction Bytecode**.
81+
82+
![Visual Studio Code pane with the Copy Transaction Bytecode selection](./media/data-manager-cosmosdb/bytecode-devkit.png)
8183

82-
![Visual Studio Code pane with bytecode in the metadata](./media/data-manager-portal/bytecode-metadata.png)
84+
The bytecode is copied to the clipboard.
8385

8486
1. Save the **bytecode** value as a JSON file. For example, *bytecode.json*. You use the file in a later step.
8587

articles/blockchain/service/data-manager-portal.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -73,13 +73,15 @@ The contract ABI defines the smart contract interfaces. It describes how to inte
7373

7474
1. Save the **abi** array as a JSON file. For example, *abi.json*. You use the file in a later step.
7575

76-
Blockchain Data Manager requires the deployed bytecode for the smart contract. The deployed bytecode is different than the smart contract bytecode. You can get the deployed bytecode from the compiled contract metadata file.
76+
Blockchain Data Manager requires the deployed bytecode for the smart contract. The deployed bytecode is different than the smart contract bytecode. You use the Azure blockchain development kit extension to copy the bytecode to the clipboard.
7777

78-
1. Open the contract metadata file contained in the **build/contracts** folder of your Solidity project. The file name is the smart contract name followed by the **.json** extension.
79-
1. Find the **deployedBytecode** element in the JSON file.
80-
1. Copy the hexadecimal value without the quotes.
78+
1. In the Visual Studio Code explorer pane, expand the **build/contracts** folder of your Solidity project.
79+
1. Right-click the contract metadata JSON file. The file name is the smart contract name followed by the **.json** extension.
80+
1. Select **Copy Transaction Bytecode**.
81+
82+
![Visual Studio Code pane with the Copy Transaction Bytecode selection](./media/data-manager-portal/bytecode-devkit.png)
8183

82-
![Visual Studio Code pane with bytecode in the metadata](./media/data-manager-portal/bytecode-metadata.png)
84+
The bytecode is copied to the clipboard.
8385

8486
1. Save the **bytecode** value as a JSON file. For example, *bytecode.json*. You use the file in a later step.
8587

-14.6 KB
Loading
-20 KB
Loading
-19.9 KB
Loading
37.7 KB
Loading
37.7 KB
Loading
Binary file not shown.
-23.2 KB
Loading

0 commit comments

Comments
 (0)