Revert "updated custom activity outputs"

This reverts commit 3cd11e5.

Author: nabhishek

articles/data-factory/transform-data-using-dotnet-custom-activity.md

@@ -29,7 +29,7 @@ To move data to/from a data store that Data Factory does not support, or to tran
 
 > [!NOTE]
 > This article applies to version 2 of Data Factory, which is currently in preview. If you are using version 1 of the Data Factory service, which is generally available (GA), see [(Custom) DotNet Activity in Data Factory version 1](v1/data-factory-use-custom-activities.md).
-
+ 
 
 See following articles if you are new to Azure Batch service:
 
@@ -109,9 +109,6 @@ The following table describes names and descriptions of properties that are spec
 | referenceObjects      | An array of existing Linked Services and Datasets. The referenced Linked Services and Datasets are passed to the custom application in JSON format so your custom code can reference resources of the Data Factory | No       |
 | extendedProperties    | User-defined properties that can be passed to the custom application in JSON format so your custom code can reference additional properties | No       |
 
-> [!NOTE]
-> From September 1, 2018, linked service containing secrets/ secure strings are not recommended to be passed as referenced objects to the custom activity.  We will be allowing only [Azure Key Vault enabled linked services](store-credentials-in-key-vault) to be passed as referenced objects in the future. Please refer to a [Custom activity sample using AKV enabled linked service](https://github.com/nabhishek/customactivity_sample/tree/linkedservice). 
-
 ## Executing commands
 
 You can directly execute a command using Custom Activity. The following example runs the "echo hello world" command on the target Azure Batch Pool nodes and prints the output to stdout. 
@@ -215,10 +212,6 @@ namespace SampleApp
             // From LinkedServices
             dynamic linkedServices = JsonConvert.DeserializeObject(File.ReadAllText("linkedServices.json"));
             Console.WriteLine(linkedServices[0].properties.typeProperties.accountName);
-            
-            // Send an output to ADF to be consumed by donwstream activities - outputs.json
-            string someJSON = "{\"Name\":\"someName\",\"Value\":\"someValue\"}";
-            File.WriteAllText("outputs.json", someJSON );
         }
     }
 }
@@ -283,16 +276,8 @@ namespace SampleApp
   "outputs": [
     "https://shengcstorbatch.blob.core.windows.net/adfjobs/<GUID>/output/stdout.txt",
     "https://shengcstorbatch.blob.core.windows.net/adfjobs/<GUID>/output/stderr.txt"
-  ],
-    "customOutput": {
-        "Name": "someName",
-        "Value": "someValue"
-    },
-     "computeInformation": "{\"account\":\"abaccount\",\"poolName\":\"batch_pool\",\"vmSize\":\"standard_a1\"}",
-  "effectiveIntegrationRuntime": "DefaultIntegrationRuntime (East US)",
-   "executionDuration": 38486
-   
-  
+  ]
+  "effectiveIntegrationRuntime": "DefaultIntegrationRuntime (East US)"
   Activity Error section:
   "errorCode": ""
   "message": ""
@@ -301,8 +286,6 @@ namespace SampleApp
   ```
 If you would like to consume the content of stdout.txt in downstream activities, you can get the path to the stdout.txt file in expression "\@activity('MyCustomActivity').output.outputs[0]". 
 
-To access the **custom output** from your custom code by writing the **outputs.json** file, use expression "\@activity('MyCustomActivity').output.customOutput". In above case, if you would like to access the 'Name' property from your custom output, then use "\@activity('MyCustomActivity').output.customOutput.Name".
-
   > [!IMPORTANT]
   > - The activity.json, linkedServices.json, and datasets.json are stored in the runtime folder of the Batch task. For this example, the activity.json, linkedServices.json, and datasets.json are stored in "https://adfv2storage.blob.core.windows.net/adfjobs/<GUID>/runtime/" path. If needed, you need to clean them up separately. 
   > - For Linked Services uses Self-Hosted Integration Runtime, the sensitive information like keys or passwords are encrypted by the Self-Hosted Integration Runtime to ensure credential stays in customer defined private network environment. Some sensitive fields could be missing when referenced by your custom application code in this way. Use SecureString in extendedProperties instead of using Linked Service reference if needed.