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: Contributing.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
<!-- omit in toc -->
2
-
# Contributing to Azure Cosmos DB Data Migration Desktop Tool
2
+
# Contributing to Azure Cosmos DB Desktop Data Migration Tool
3
3
4
4
First off, thanks for taking the time to contribute! ❤️
5
5
@@ -24,7 +24,7 @@ All types of contributions are encouraged and valued. See the [Table of Contents
24
24
## Code of Conduct
25
25
26
26
This project and everyone participating in it is governed by the
27
-
[Azure Cosmos DB Data Migration Desktop Tool Code of Conduct](https://github.com/AzureCosmosDB/data-migration-desktop-toolblob/master/CODE_OF_CONDUCT.md).
27
+
[Azure Cosmos DB Desktop Data Migration Tool Code of Conduct](https://github.com/AzureCosmosDB/data-migration-desktop-toolblob/master/CODE_OF_CONDUCT.md).
28
28
By participating, you are expected to uphold this code. Please report unacceptable behavior
The Cosmos DB Data Migration Tool is a lightweight executable that leverages the [Managed Extensibility Framework (MEF)](https://docs.microsoft.com/en-us/dotnet/framework/mef/). MEF enables decoupled implementation of the core project and its extensions. The core application is a command-line executable responsible for composing the required extensions at runtime by automatically loading them from the Extensions folder of the application. An Extension is a class library that includes the implementation of a System as a Source and (optionally) Sink for data transfer. The core application project does not contain direct references to any extension implementation. Instead, these projects share a common interface.
35
+
The Azure Cosmos DB Desktop Data Migration Tool is a lightweight executable that leverages the [Managed Extensibility Framework (MEF)](https://docs.microsoft.com/en-us/dotnet/framework/mef/). MEF enables decoupled implementation of the core project and its extensions. The core application is a command-line executable responsible for composing the required extensions at runtime by automatically loading them from the Extensions folder of the application. An Extension is a class library that includes the implementation of a System as a Source and (optionally) Sink for data transfer. The core application project does not contain direct references to any extension implementation. Instead, these projects share a common interface.
36
36
37
37

38
38
39
-
## Cosmos DB project structure
39
+
## Project Structure
40
40
41
41
The Cosmos DB Data Migration Tool core project is a C# command-line executable. The core application serves as the composition container for the required Source and Sink extensions. Therefore, the application user needs to put only the desired Extension class library assembly into the Extensions folder before running the application. In addition, the core project has a unit test project to exercise the application's behavior, whereas extension projects contain concrete integration tests that rely on external systems.
42
42
@@ -51,7 +51,7 @@ This project has adopted the [Microsoft Open Source Code of Conduct](https://ope
51
51
1. From a command prompt, execute the following command in an empty working folder that will house the source code.
This tutorial outlines how to use the Cosmos DB Data Migration tool to move JSON data to Azure Cosmos DB. This tutorial uses the Azure Cosmos DB Emulator.
65
+
This tutorial outlines how to use the Azure Cosmos DB Desktop Data Migration Tool to move JSON data to Azure Cosmos DB. This tutorial uses the Azure Cosmos DB Emulator.
66
66
67
67
### Tutorial Software prerequisites
68
68
@@ -198,7 +198,7 @@ This tutorial outlines how to use the Cosmos DB Data Migration tool to move JSON
198
198
199
199
Multiple extensions are provided in this repository. Find the documentation for the usage and configuration of each using the links provided:
0 commit comments