Skip to content

Commit c4fd18a

Browse files
authored
Merge pull request #1 from MicrosoftDocs/master
Updating Master
2 parents 5b1cdb2 + e38ae25 commit c4fd18a

File tree

5,975 files changed

+132196
-129776
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

5,975 files changed

+132196
-129776
lines changed

.openpublishing.publish.config.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@
8080
],
8181
"notification_subscribers": [],
8282
"sync_notification_subscribers": [
83-
"gewarren@microsoft.com"
83+
"ghogen@microsoft.com"
8484
],
8585
"branches_to_filter": [],
8686
"git_repository_url_open_to_public_contributors": "https://github.com/MicrosoftDocs/visualstudio-docs",
@@ -110,7 +110,7 @@
110110
]
111111
},
112112
"need_generate_pdf_url_template": true,
113-
"Targets": {
113+
"targets": {
114114
"Pdf": {
115115
"template_folder": "_themes.pdf"
116116
}
@@ -119,4 +119,4 @@
119119
"need_generate_intellisense": false,
120120
"enable_branch_build_custom_validation": true,
121121
"enable_pull_request_custom_validation": true
122-
}
122+
}

.openpublishing.redirection.json

Lines changed: 9407 additions & 7987 deletions
Large diffs are not rendered by default.

docs/_breadcrumb/toc.yml

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,10 +13,10 @@
1313
tocHref: /visualstudio/cross-platform/
1414
topicHref: /visualstudio/cross-platform/index
1515
- name: Data Tools
16-
tocHref: /visualstudio/data-tools/
16+
tocHref: /visualstudio/data-tools/
1717
topicHref: /visualstudio/data-tools/index
1818
- name: Debugging
19-
tocHref: /visualstudio/debugger/
19+
tocHref: /visualstudio/debugger/
2020
topicHref: /visualstudio/debugger/index
2121
items:
2222
- name: Debug Interface Access SDK
@@ -28,9 +28,6 @@
2828
- name: Deployment
2929
tocHref: /visualstudio/deployment/
3030
topicHref: /visualstudio/deployment/deploying-applications-services-and-components
31-
- name: Designers
32-
tocHref: /visualstudio/designers/
33-
topicHref: /visualstudio/designers/designing-user-interfaces
3431
- name: Extensibility
3532
tocHref: /visualstudio/extensibility/
3633
topicHref: /visualstudio/extensibility/index
@@ -71,12 +68,12 @@
7168
topicHref: /visualstudio/rtvs/index
7269
- name: Office and SharePoint
7370
tocHref: /visualstudio/vsto/
74-
topicHref: /visualstudio/vsto/office-and-sharepoint-development-in-visual-studio
71+
topicHref: /visualstudio/vsto/office-and-sharepoint-development-in-visual-studio
7572
items:
7673
- name: SharePoint
7774
tocHref: /visualstudio/sharepoint/
7875
topicHref: /visualstudio/sharepoint/create-sharepoint-solutions
79-
- name: VSTO
76+
- name: VSTO
8077
tocHref: /visualstudio/vsto/
8178
topicHref: /visualstudio/vsto/create-vsto-add-ins-for-office-by-using-visual-studio
8279
- name: Testing
@@ -85,6 +82,9 @@
8582
- name: Workflow Designer
8683
tocHref: /visualstudio/workflow-designer/
8784
topicHref: /visualstudio/workflow-designer/developing-applications-with-the-workflow-designer
85+
- name: XAML Tools
86+
tocHref: /visualstudio/xaml-tools/
87+
topicHref: /visualstudio/xaml-tools/
8888
- name: XML Tools
8989
tocHref: /visualstudio/xml-tools/
9090
topicHref: /visualstudio/xml-tools/xml-tools-in-visual-studio

docs/ai/about-ai-tools.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.workload:
1515

1616
Visual Studio Tools for AI is an extension to build, test, and deploy Deep Learning / AI solutions. It seamlessly integrates with Azure Machine Learning for robust experimentation capabilities, including but not limited to submitting data preparation and model training jobs transparently to different compute targets. Additionally, it provides support for custom metrics and run history tracking, enabling data science reproducibility and auditing. Enterprise ready collaboration, allow to securely work on project with other people.
1717

18-
Get started with deep learning using [Microsoft Cognitive Toolkit (CNTK)](http://www.microsoft.com/en-us/cognitive-toolkit), [Google TensorFlow](https://www.tensorflow.org), or other deep-learning frameworks today.
18+
Get started with deep learning using [Microsoft Cognitive Toolkit (CNTK)](https://docs.microsoft.com/cognitive-toolkit/), [Google TensorFlow](https://www.tensorflow.org), or other deep-learning frameworks today.
1919

2020
## Develop, debug, and deploy deep learning models and AI solutions
2121
Use the productivity features of Visual Studio to accelerate AI innovation today. Use built-in code editor features like syntax highlighting, IntelliSense, and text auto formatting. You can interactively test your deep learning application in your local environment using step-through debugging on local variables and models.
@@ -40,4 +40,4 @@ This extension makes it easy to train models on your local computer or you can s
4040
Currently this extension supports Windows 64-bit operating systems.
4141

4242
## Support
43-
Support for this extension is provided on our [GitHub Issue Tracker](http://github.com/Microsoft/vs-tools-for-ai/issues). You can submit a bug report or feature suggestion and participate in discussions.
43+
Support for this extension is provided on our [GitHub Issue Tracker](https://github.com/Microsoft/vs-tools-for-ai/issues). You can submit a bug report or feature suggestion and participate in discussions.

docs/ai/create-project-existing.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,4 +36,4 @@ Once you've [installed Visual Studio Tools for AI](installation.md), it's easy t
3636
3737
## See also
3838

39-
- [Manually identify an existing Python environment](../python/managing-python-environments-in-visual-studio.md#manually-identify-an-existing-environment)
39+
- [Manually identify an existing Python environment](../python/managing-python-environments-in-visual-studio.md#manually-identify-an-existing-environment)

docs/ai/create-project-gallery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -53,4 +53,4 @@ Once you've [installed Visual Studio Tools for AI](installation.md), it's easy t
5353

5454
7. Run in a Docker container or on your local machine
5555

56-
![mnist](media/create-project-gallery/azml-local.png)
56+
![mnist](media/create-project-gallery/azml-local.png)

docs/ai/installation.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Before training deep learning models on your local computer, make sure you have
3838
3939
### NVIDIA GPU driver
4040

41-
Deep learning frameworks take advantage of NVIDIA GPU to let machines learn at a speed, accuracy, and scale towards true artificial intelligence. If your computer has NVIDIA GPU cards, see [NVIDIA Driver Downloads](http://www.nvidia.com/Download/index.aspx) or try an operating system update to install the latest driver.
41+
Deep learning frameworks take advantage of NVIDIA GPU to let machines learn at a speed, accuracy, and scale towards true artificial intelligence. If your computer has NVIDIA GPU cards, see [NVIDIA Driver Downloads](https://www.nvidia.com/Download/index.aspx) or try an operating system update to install the latest driver.
4242

4343
### CUDA
4444

@@ -188,7 +188,7 @@ pip3.5 install Theano==0.9.0
188188

189189
### PyTorch
190190

191-
[PyTorch](http://pytorch.org/) is a python package that provides two high-level features:
191+
[PyTorch](https://pytorch.org/) is a python package that provides two high-level features:
192192

193193
- Tensor computation (like numpy) with strong GPU acceleration
194194
- Deep Neural Networks built on a tape-based autograd system

docs/ai/job-details.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,4 +19,4 @@ Once the jobs are submitted, you can view the list of jobs to see their status,
1919

2020
![monitor jobs](media/job-details/monitor-jobs.png)
2121

22-
> Job history submitted to Linux VMs is stored on the VM in the /tmp directory. Therefore, whenever it is rebooted the job history is cleared. For a permanent record of your job history, please configure your VM as a compute context in Azure Machine learning, then Submit Job to Azure Machine Learning (selecting your VM as the compute context).
22+
> Job history submitted to Linux VMs is stored on the VM in the /tmp directory. Therefore, whenever it is rebooted the job history is cleared. For a permanent record of your job history, please configure your VM as a compute context in Azure Machine learning, then Submit Job to Azure Machine Learning (selecting your VM as the compute context).

docs/ai/manage-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,4 +26,4 @@ You can browse all storage on the remote machine or Azure file share to enable u
2626
2. Select the job.
2727
3. Click **Working Folder** or click **StdOut / Stderr** for quick access to these important log files.
2828

29-
![storage](media/manage-storage/job-workingfolder.png)
29+
![storage](media/manage-storage/job-workingfolder.png)

docs/ai/monitor-tensorboard.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,4 +18,4 @@ You can visualize your model training progress with TensorBoard.
1818

1919
2. Notice the error decreasing over time, which means the quality is improving.
2020

21-
![run tensorboard](media/monitor-tensorboard/tensorboard.png)
21+
![run tensorboard](media/monitor-tensorboard/tensorboard.png)

docs/ai/tensorflow-local.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,4 +54,4 @@ Download this [GitHub repository](https://github.com/Microsoft/samples-for-ai) c
5454
![Sample output from console](media/tensorflow-local/console-output.png)
5555

5656
> [!div class="nextstepaction"]
57-
> [Train a TensorFlow model in the cloud](tensorflow-vm.md)
57+
> [Train a TensorFlow model in the cloud](tensorflow-vm.md)

docs/azure/includes/storage-try-azure-tools.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,4 +4,4 @@
44
>
55
> [Microsoft Azure Storage Explorer](/azure/vs-azure-tools-storage-manage-with-storage-explorer) is a free, standalone app from Microsoft. You can use it to work visually with Azure Storage data on Windows, macOS, and Linux.
66
>
7-
>
7+
>

docs/azure/vs-azure-tools-azure-project-create.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ This section walks you through creating an Azure cloud service project in Visual
5555

5656
The Visual Studio Azure project has associations to the role projects in the solution. The project also includes the *service definition file* and *service configuration file*:
5757

58-
- **Service definition file** - Defines the runtime settings for your application, including what roles are required, endpoints, and virtual machine size.
58+
- **Service definition file** - Defines the run-time settings for your application, including what roles are required, endpoints, and virtual machine size.
5959
- **Service configuration file** - Configures how many instances of a role are run and the values of the settings defined for a role.
6060

6161
For more information about these files, see [Configure the Roles for an Azure cloud service with Visual Studio](vs-azure-tools-configure-roles-for-cloud-service.md).

docs/azure/vs-azure-tools-configure-roles-for-cloud-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ An Azure cloud service can have one or more worker or web roles. For each role,
1616

1717
The information for your cloud service is stored in the following files:
1818

19-
- **ServiceDefinition.csdef** - The service definition file defines the runtime settings for your cloud service including what roles are required, endpoints, and virtual machine size. None of the data stored in `ServiceDefinition.csdef` can be changed when your role is running.
19+
- **ServiceDefinition.csdef** - The service definition file defines the run-time settings for your cloud service including what roles are required, endpoints, and virtual machine size. None of the data stored in `ServiceDefinition.csdef` can be changed when your role is running.
2020
- **ServiceConfiguration.cscfg** - The service configuration file configures how many instances of a role are run and the values of the settings defined for a role. The data stored in `ServiceConfiguration.cscfg` can be changed while your role is running.
2121

2222
To store different values for the settings that control how a role runs, you can define multiple service configurations. You can use a different service configuration for each deployment environment. For example, you can set your storage account connection string to use the local Azure storage emulator in a local service configuration and create another service configuration to use Azure storage in the cloud.

docs/azure/vs-azure-tools-connected-services-storage.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -61,14 +61,14 @@ After completion, the **Add Connected Services** dialog automatically displays d
6161

6262
When you finish the dialog, Visual Studio adds references and modifies certain configuration files. The specific changes depend on the project type:
6363

64-
- ASP.NET project - [What happened – ASP.NET Projects](http://go.microsoft.com/fwlink/p/?LinkId=513126)
65-
- ASP.NET Core project - [What happened – ASP.NET 5 Projects](http://go.microsoft.com/fwlink/p/?LinkId=513124)
66-
- Cloud service project (web roles and worker roles) - [What happened – Cloud Service projects](http://go.microsoft.com/fwlink/p/?LinkId=516965)
64+
- ASP.NET project - [What happened – ASP.NET Projects](/azure/visual-studio/vs-storage-aspnet-getting-started-blobs)
65+
- ASP.NET Core project - [What happened – ASP.NET 5 Projects](/azure/visual-studio/vs-storage-aspnet5-getting-started-blobs)
66+
- Cloud service project (web roles and worker roles) - [What happened – Cloud Service projects](/azure/visual-studio/vs-storage-cloud-services-getting-started-blobs)
6767
- WebJob project - [What happened - WebJob projects](/azure/visual-studio/vs-storage-webjobs-what-happened)
6868

6969
## See also
7070

7171
- [MSDN Forum: Azure Storage](https://social.msdn.microsoft.com/forums/azure/home?forum=windowsazuredata)
72-
- [Microsoft Azure Storage Team Blog](http://blogs.msdn.com/b/windowsazurestorage/)
73-
- [Azure Storage documentation](https://docs.microsoft.com/azure/storage/)
72+
- [Microsoft Azure Storage Team Blog](https://blogs.msdn.microsoft.com/windowsazurestorage/)
73+
- [Azure Storage documentation](/azure/storage/)
7474
- [Connected services (Visual Studio for Mac)](/visualstudio/mac/connected-services)

docs/azure/vs-azure-tools-debug-cloud-services-virtual-machines.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ To debug a cloud service from a remote machine, you must enable that functionali
4444
If you enable remote debugging for a cloud service, it doesn't exhibit degraded performance or incur additional charges. Don't use remote debugging on a production service, because clients who use the service might be adversely affected.
4545

4646
> [!NOTE]
47-
> When you publish a cloud service from Visual Studio, you can enable **IntelliTrace** for any roles in that service that target the .NET Framework 4 or the .NET Framework 4.5. By using **IntelliTrace**, you can examine events that occurred in a role instance in the past and reproduce the context from that time. See [Debugging a published cloud service with IntelliTrace and Visual Studio](http://go.microsoft.com/fwlink/?LinkID=623016) and [Using IntelliTrace](https://msdn.microsoft.com/library/dd264915.aspx).
47+
> When you publish a cloud service from Visual Studio, you can enable **IntelliTrace** for any roles in that service that target the .NET Framework 4 or the .NET Framework 4.5. By using **IntelliTrace**, you can examine events that occurred in a role instance in the past and reproduce the context from that time. See [Debugging a published cloud service with IntelliTrace and Visual Studio](vs-azure-tools-IntelliTrace-debug-published-cloud-services.md) and [Using IntelliTrace](../debugger/intellitrace.md).
4848
4949
### To enable remote debugging for a cloud service
5050

@@ -70,7 +70,7 @@ If you enable remote debugging for a cloud service, it doesn't exhibit degraded
7070

7171
![Attach Debugger](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC746719.gif)
7272

73-
3. After the debugger attaches to an instance, debug as usual. The debugger automatically attaches to the appropriate host process for your role. Depending on what the role is, the debugger attaches to w3wp.exe, WaWorkerHost.exe, or WaIISHost.exe. To verify the process to which the debugger is attached, expand the instance node in Server Explorer. See [Azure Role Architecture](http://blogs.msdn.com/b/kwill/archive/2011/05/05/windows-azure-role-architecture.aspx) for more information about Azure processes.
73+
3. After the debugger attaches to an instance, debug as usual. The debugger automatically attaches to the appropriate host process for your role. Depending on what the role is, the debugger attaches to w3wp.exe, WaWorkerHost.exe, or WaIISHost.exe. To verify the process to which the debugger is attached, expand the instance node in Server Explorer. See [Azure Role Architecture](https://blogs.msdn.microsoft.com/kwill/2011/05/05/windows-azure-role-architecture/) for more information about Azure processes.
7474

7575
![Select code type dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC718346.png)
7676

@@ -123,7 +123,7 @@ You can debug programs that run on Azure virtual machines by using Server Explor
123123

124124
![Select code type dialog box](./media/vs-azure-tools-debug-cloud-services-virtual-machines/IC718346.png)
125125

126-
5. Select the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) and [Azure Role Architecture](http://blogs.msdn.com/b/kwill/archive/2011/05/05/windows-azure-role-architecture.aspx) for more information.
126+
5. Select the processes you want to debug on the virtual machine and then select **Attach**. For example, you might choose the w3wp.exe process if you wanted to debug a web app on the virtual machine. See [Debug One or More Processes in Visual Studio](https://msdn.microsoft.com/library/jj919165.aspx) and [Azure Role Architecture](https://blogs.msdn.microsoft.com/kwill/2011/05/05/windows-azure-role-architecture/) for more information.
127127

128128
## Create a web project and a virtual machine for debugging
129129

@@ -144,7 +144,7 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
144144
> [!NOTE]
145145
> You'll be asked to sign in to your Azure account if you're not already signed in.
146146
147-
3. Select the various settings for the virtual machine and then select **OK**. See [Virtual Machines](http://go.microsoft.com/fwlink/?LinkId=623033) for more information.
147+
3. Select the various settings for the virtual machine and then select **OK**. See [Virtual Machines](/azure/virtual-machines/) for more information.
148148

149149
The name you enter for DNS name will be the name of the virtual machine.
150150

@@ -182,6 +182,6 @@ Visual Studio ASP.NET projects offer an option to create a handy virtual machine
182182

183183
## Next steps
184184

185-
* Use **IntelliTrace** to collect a log of calls and events from a release server. See [Debugging a Published Cloud Service with IntelliTrace and Visual Studio](http://go.microsoft.com/fwlink/?LinkID=623016).
185+
* Use **IntelliTrace** to collect a log of calls and events from a release server. See [Debugging a Published Cloud Service with IntelliTrace and Visual Studio](vs-azure-tools-IntelliTrace-debug-published-cloud-services.md).
186186

187-
* Use **Azure Diagnostics** to log detailed information from code running within roles, whether the roles are running in the development environment or in Azure. See [Collecting logging data by using Azure Diagnostics](http://go.microsoft.com/fwlink/p/?LinkId=400450).
187+
* Use **Azure Diagnostics** to log detailed information from code running within roles, whether the roles are running in the development environment or in Azure. See [Collecting logging data by using Azure Diagnostics](/azure/cloud-services/cloud-services-dotnet-diagnostics).

0 commit comments

Comments
 (0)