Skip to content

Commit

Permalink
Update windowsazure.com links (dotnet#4323)
Browse files Browse the repository at this point in the history
* Update windowsazure.com links

Fixes dotnet#4178

Updates

Updates

Updates

* Remove one link

* Link update
  • Loading branch information
guardrex authored and scottaddie committed Sep 19, 2017
1 parent 8c11a14 commit 53e19c9
Show file tree
Hide file tree
Showing 42 changed files with 119 additions and 119 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -168,7 +168,7 @@ The database creation script retrieves the dev machine's IP address and sets a f

[!code-powershell[Main](automate-everything/samples/sample14.ps1)]

The Fix It app uses separate membership and application databases. It's also possible to put both membership and application data in a single database. For an example that uses a single database, see [Create an ASP.NET MVC app with auth and SQL DB and deploy to Azure App Service](https://www.windowsazure.com/en-us/develop/net/tutorials/web-site-with-sql-database/).
The Fix It app uses separate membership and application databases. It's also possible to put both membership and application data in a single database.

### Store app settings and connection strings

Expand Down Expand Up @@ -250,15 +250,15 @@ In the [next chapter](source-control.md) we'll look at source code and explain w

## Resources

- [Install and Configure Windows PowerShell for Azure](https://www.windowsazure.com/en-us/manage/install-and-configure-windows-powershell/). Explains how to install the Azure PowerShell cmdlets and how to install the certificate that you need on your computer in order to manage your Azure account. This is a great place to get started because it also has links to resources for learning PowerShell itself.
- [Azure Script Center](https://www.windowsazure.com/en-us/documentation/scripts/). WindowsAzure.com portal to resources for developing scripts that manage Azure services, with links to getting started tutorials, cmdlet reference documentation and source code, and sample scripts
- [Install and Configure Windows PowerShell for Azure](https://docs.microsoft.com/powershell/azure/overview?view=azurermps-4.3.1). Explains how to install the Azure PowerShell cmdlets and how to install the certificate that you need on your computer in order to manage your Azure account. This is a great place to get started because it also has links to resources for learning PowerShell itself.
- [Azure Script Center](https://docs.microsoft.com/azure/automation/automation-runbook-gallery). WindowsAzure.com portal to resources for developing scripts that manage Azure services, with links to getting started tutorials, cmdlet reference documentation and source code, and sample scripts
- [Weekend Scripter: Getting Started with Azure and PowerShell](http://blogs.technet.com/b/heyscriptingguy/archive/2013/06/22/weekend-scripter-getting-started-with-windows-azure-and-powershell.aspx). In a blog dedicated to Windows PowerShell, this post provides a great introduction to using PowerShell for Azure management functions.
- [Install and Configure the Azure Cross-Platform Command-Line Interface](https://www.windowsazure.com/en-us/manage/install-and-configure-cli/). Getting-started tutorial for an Azure scripting framework that works on Mac and Linux as well as Windows systems.
- [Azure Command Line Tools](https://www.windowsazure.com/en-us/downloads/#cmd-line-tools). Portal page for documentation and downloads related to command line tools for Azure.
- [Install and Configure the Azure Cross-Platform Command-Line Interface](https://docs.microsoft.com/cli/azure/install-azure-cli?view=azure-cli-latest). Getting-started tutorial for an Azure scripting framework that works on Mac and Linux as well as Windows systems.
- [Command-line tools section of the Download Azure SDKs and Tools topic](https://azure.microsoft.com/downloads/). Portal page for documentation and downloads related to command-line tools for Azure.
- [Automating everything with the Azure Management Libraries and .NET](http://www.hanselman.com/blog/PennyPinchingInTheCloudAutomatingEverythingWithTheWindowsAzureManagementLibrariesAndNET.aspx). Scott Hanselman introduces the .NET management API for Azure.
- [Using Windows PowerShell Scripts to Publish to Dev and Test Environments](https://msdn.microsoft.com/library/azure/dn642480.aspx). MSDN documentation that explains how to use publish scripts that Visual Studio automatically generates for web projects.
- [PowerShell Tools for Visual Studio 2013](https://visualstudiogallery.msdn.microsoft.com/c9eb3ba8-0c59-4944-9a62-6eee37294597). Visual Studio extension that adds language support for Windows PowerShell in Visual Studio.

>[!div class="step-by-step"]
[Previous](introduction.md)
[Next](source-control.md)
[Next](source-control.md)
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ Documentation:
- [Azure Business Continuity Technical Guidance](https://msdn.microsoft.com/en-us/library/windowsazure/hh873027.aspx). White paper by Patrick Wickline and Jason Roth.
- [Disaster Recovery and High Availability for Azure Applications](https://msdn.microsoft.com/en-us/library/windowsazure/dn251004.aspx). White paper by Michael McKeown, Hanu Kommalapati, and Jason Roth.
- [Microsoft Patterns and Practices - Azure Guidance](https://msdn.microsoft.com/en-us/library/dn568099.aspx). See Multi Data Center Deployment guidance, Circuit breaker pattern.
- [Azure Support - Service Level Agreements](https://www.windowsazure.com/en-us/support/legal/sla/).
- [Azure Support - Service Level Agreements](https://azure.microsoft.com/support/legal/sla/).
- [Business Continuity in Azure SQL Database](https://msdn.microsoft.com/en-us/library/windowsazure/hh852669.aspx). Documentation about SQL Database high availability and disaster recovery features.
- [High Availability and Disaster Recovery for SQL Server in Azure Virtual Machines](https://msdn.microsoft.com/en-us/library/windowsazure/jj870962.aspx).

Expand All @@ -128,4 +128,4 @@ Videos:

>[!div class="step-by-step"]
[Previous](unstructured-blob-storage.md)
[Next](monitoring-and-telemetry.md)
[Next](monitoring-and-telemetry.md)
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ In .NET System.Diagnostics tracing, logs can be assigned Error, Warning, Info, a

While it's worthwhile to have logging always on in production, another best practice is to implement a logging framework that enables you to adjust at run-time the level of detail that you're logging, without redeploying or restarting your application. For example when you use the tracing facility in `System.Diagnostics` you can create Error, Warning, Info, and Debug/Verbose logs. We recommend you always log Error, Warning, and Info logs in production, and you'll want to be able to dynamically add Debug/Verbose logging for troubleshooting on a case-by-case basis.

Web Apps in Azure App Service have built-in support for writing `System.Diagnostics` logs to the file system, Table storage, or Blob storage. You can select different logging levels for each storage destination, and you can change the logging level on the fly without restarting your application. The Blob storage support makes it easier to run [HDInsight](https://www.windowsazure.com/en-us/documentation/services/hdinsight/) analysis jobs on your application logs, because HDInsight knows how to work with Blob storage directly.
Web Apps in Azure App Service have built-in support for writing `System.Diagnostics` logs to the file system, Table storage, or Blob storage. You can select different logging levels for each storage destination, and you can change the logging level on the fly without restarting your application. The Blob storage support makes it easier to run [HDInsight](https://docs.microsoft.com/azure/hdinsight/) analysis jobs on your application logs, because HDInsight knows how to work with Blob storage directly.

### Log Exceptions

Expand All @@ -147,7 +147,7 @@ We highly recommend that you write a log every time your app calls out to a serv

What we recommend doing when you create a production application is to create a simple *ILogger* interface and stick some methods in it. This makes it easy to change the logging implementation later and not have to go through all your code to do it. We could be using the `System.Diagnostics.Trace` class throughout the Fix It app, but instead we're using it under the covers in a logging class that implements *ILogger*, and we make *ILogger* method calls throughout the app.

That way, if you ever want to make your logging richer, you can replace [`System.Diagnostics.Trace`](https://www.windowsazure.com/en-us/develop/net/tutorials/troubleshoot-web-sites-in-visual-studio/#apptracelogs) with whatever logging mechanism you want. For example, as your app grows you might decide that you want to use a more comprehensive logging package such as [NLog](http://nlog-project.org/) or [Enterprise Library Logging Application Block](https://msdn.microsoft.com/en-us/library/dn440731(v=pandp.60).aspx). ([Log4Net](http://logging.apache.org/log4net/) is another popular logging framework but it doesn't do asynchronous logging.)
That way, if you ever want to make your logging richer, you can replace [`System.Diagnostics.Trace`](https://docs.microsoft.com/azure/app-service-web/web-sites-dotnet-troubleshoot-visual-studio#apptracelogs) with whatever logging mechanism you want. For example, as your app grows you might decide that you want to use a more comprehensive logging package such as [NLog](http://nlog-project.org/) or [Enterprise Library Logging Application Block](https://msdn.microsoft.com/en-us/library/dn440731(v=pandp.60).aspx). ([Log4Net](http://logging.apache.org/log4net/) is another popular logging framework but it doesn't do asynchronous logging.)

One possible reason for using a framework such as NLog is to facilitate dividing up logging output into separate high-volume and high-value data stores. That helps you to efficiently store large volumes of INFORM data that you don't need to execute fast queries against, while maintaining quick access to ACT data.

Expand Down Expand Up @@ -215,13 +215,13 @@ This code basically says that anywhere a constructor needs an *ILogger* interfac

## Built-in logging support in Azure

Azure supports the following kinds of [logging for Web Apps in Azure App Service](https://www.windowsazure.com/en-us/develop/net/tutorials/troubleshoot-web-sites-in-visual-studio/):
Azure supports the following kinds of [logging for Web Apps in Azure App Service](https://docs.microsoft.com/azure/app-service-web/web-sites-dotnet-troubleshoot-visual-studio):

- System.Diagnostics tracing (you can turn on and off and set levels on the fly without restarting the site).
- Windows Events.
- IIS Logs (HTTP/FREB).

Azure supports the following kinds of [logging in Cloud Services](https://www.windowsazure.com/en-us/develop/net/common-tasks/diagnostics/):
Azure supports the following kinds of [logging in Cloud Services](https://docs.microsoft.com/azure/cloud-services/cloud-services-dotnet-diagnostics):

- System.Diagnostics tracing.
- Performance counters.
Expand Down Expand Up @@ -272,7 +272,7 @@ Documentation mainly about troubleshooting:

- [Azure Troubleshooting & Debugging blog](https://blogs.msdn.com/b/kwill/).
- [AzureTools – The Diagnostic Utility used by the Azure Developer Support Team](https://blogs.msdn.com/b/kwill/archive/2013/08/26/azuretools-the-diagnostic-utility-used-by-the-windows-azure-developer-support-team.aspx?Redirected=true). Introduces and provides a download link for a tool that can be used on an Azure VM to download and run a wide variety of diagnostic and monitoring tools. Useful when you need to diagnose an issue on a particular VM.
- [Troubleshoot a web app in Azure App Service using Visual Studio](https://www.windowsazure.com/en-us/develop/net/tutorials/troubleshoot-web-sites-in-visual-studio/). A step-by-step tutorial for getting started with System.Diagnostics tracing and remote debugging.
- [Troubleshoot a web app in Azure App Service using Visual Studio](https://docs.microsoft.com/azure/app-service-web/web-sites-dotnet-troubleshoot-visual-studio). A step-by-step tutorial for getting started with System.Diagnostics tracing and remote debugging.

Videos:

Expand All @@ -285,4 +285,4 @@ Code sample:

>[!div class="step-by-step"]
[Previous](design-to-survive-failures.md)
[Next](transient-fault-handling.md)
[Next](transient-fault-handling.md)
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ To implement the queue pattern, we need to make two changes to the Fix It app.
- When a user submits a new Fix It task, put the task in the queue, instead of writing it to the database.
- Create a back-end service that processes messages in the queue.

For the queue, we'll use the [Azure Queue Storage Service](https://www.windowsazure.com/en-us/develop/net/how-to-guides/queue-service/). Another option is to use [Azure Service Bus](https://www.windowsazure.com/en-us/documentation/services/service-bus/).
For the queue, we'll use the [Azure Queue Storage Service](https://www.windowsazure.com/en-us/develop/net/how-to-guides/queue-service/). Another option is to use [Azure Service Bus](https://docs.microsoft.com/azure/service-bus/).

To decide which queue service to use, consider how your app needs to send and receive the messages in the queue:

Expand Down Expand Up @@ -191,4 +191,4 @@ Video:

>[!div class="step-by-step"]
[Previous](distributed-caching.md)
[Next](more-patterns-and-guidance.md)
[Next](more-patterns-and-guidance.md)
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ There are many security issues to think about when you're developing a cloud app

## Introduction to Azure AD

[Azure AD](https://www.windowsazure.com/en-us/documentation/services/active-directory/) provides [Active Directory](https://msdn.microsoft.com/en-us/library/windows/desktop/aa746492.aspx) in the cloud. Key features include the following:
[Azure AD](https://docs.microsoft.com/azure/active-directory/) provides [Active Directory](https://msdn.microsoft.com/en-us/library/windows/desktop/aa746492.aspx) in the cloud. Key features include the following:

- It integrates with on-premises Active Directory.
- It enables single sign-on with your apps.
Expand Down Expand Up @@ -178,8 +178,8 @@ The [next chapter](data-storage-options.md) looks at the data storage options av

For more information, see the following resources:

- [Azure Active Directory Documentation](https://www.windowsazure.com/en-us/documentation/services/active-directory/). Portal page for Azure AD documentation on the windowsazure.com site. For step by step tutorials, see the **Develop** section.
- [Azure Multi-Factor Authentication](https://www.windowsazure.com/en-us/documentation/services/multi-factor-authentication/). Portal page for documentation about multi-factor authentication in Azure.
- [Azure Active Directory Documentation](https://docs.microsoft.com/azure/active-directory/). Portal page for Azure AD documentation on the windowsazure.com site. For step by step tutorials, see the **Develop** section.
- [Azure Multi-Factor Authentication](https://docs.microsoft.com/azure/multi-factor-authentication/). Portal page for documentation about multi-factor authentication in Azure.
- [Organizational account authentication options](../../../../visual-studio/overview/2013/creating-web-projects-in-visual-studio.md#orgauthoptions). Explanation of the Azure AD authentication options in the Visual Studio 2013 new-project dialog.
- [Microsoft Patterns and Practices - Federated Identity Pattern](https://msdn.microsoft.com/en-us/library/dn589790.aspx).
- [HowTo: Install the Azure Active Directory Sync Tool](https://social.technet.microsoft.com/wiki/contents/articles/19098.howto-install-the-windows-azure-active-directory-sync-tool-now-with-pictures.aspx).
Expand All @@ -190,4 +190,4 @@ For more information, see the following resources:

>[!div class="step-by-step"]
[Previous](web-development-best-practices.md)
[Next](data-storage-options.md)
[Next](data-storage-options.md)
Original file line number Diff line number Diff line change
Expand Up @@ -262,7 +262,7 @@ If you want to run in Azure without using queues, and you made the changes to ru

These instructions assume you have already downloaded and run the Fix It solution locally, and that you have an Azure account or have an Azure subscription that you are authorized to manage.

1. Install the **Azure PowerShell** console. For instructions, see [How to install and configure Azure PowerShell](https://www.windowsazure.com/en-us/manage/install-and-configure-windows-powershell/).
1. Install the **Azure PowerShell** console. For instructions, see [How to install and configure Azure PowerShell](https://docs.microsoft.com/powershell/azure/overview?view=azurermps-4.3.1).

This customized console is configured to work with your Azure subscription. The Azure module is installed in the *Program Files* directory and is automatically imported on every use of the Azure PowerShell console.

Expand Down Expand Up @@ -386,13 +386,13 @@ In the same MyFixIt.WorkerRoler\app.config file, under `appSettings`, replace th

[!code-xml[Main](the-fix-it-sample-application/samples/sample33.xml?highlight=2-3)]

You can get the access key from the portal. See [How To Manage Storage Accounts](https://www.windowsazure.com/en-us/manage/services/storage/how-to-manage-a-storage-account/).
You can get the access key from the portal. See [How To Manage Storage Accounts](https://docs.microsoft.com/azure/storage/common/storage-create-storage-account).

In MyFixItCloudService\ServiceConfiguration.Cloud.cscfg, replace the same two placeholders values for the Azure storage account.

[!code-xml[Main](the-fix-it-sample-application/samples/sample34.xml?highlight=3)]

Now you are ready to deploy the cloud service. In Solution Explore, right-click the MyFixItCloudService project and select **Publish**. For more information, see "[Deploy the Application to Azure](https://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-web-site/2-download-and-run/#deployAz)", which is in part 2 of [this tutorial](https://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-web-site/1-overview/).
Now you are ready to deploy the cloud service. In Solution Explore, right-click the MyFixItCloudService project and select **Publish**. For more information, see "[Deploy the Application to Azure](https://www.windowsazure.com/en-us/develop/net/tutorials/multi-tier-web-site/2-download-and-run/#deployAz)", which is in part 2 of [this tutorial](https://code.msdn.microsoft.com/Windows-Azure-Multi-Tier-eadceb36).

>[!div class="step-by-step"]
[Previous](more-patterns-and-guidance.md)
[Previous](more-patterns-and-guidance.md)
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ There are several ways you can implement smart retry logic.

[!code-csharp[Main](transient-fault-handling/samples/sample1.cs)]

TFH also supports [Azure In-Role Cache](https://msdn.microsoft.com/en-us/library/windowsazure/dn386103.aspx) and [Service Bus](https://www.windowsazure.com/en-us/services/messaging/).
TFH also supports [Azure In-Role Cache](https://msdn.microsoft.com/en-us/library/windowsazure/dn386103.aspx) and [Service Bus](https://azure.microsoft.com/services/service-bus/).
- When you use the Entity Framework you typically aren't working directly with SQL connections, so you can't use this Patterns and Practices package, but Entity Framework 6 builds this kind of retry logic right into the framework. In a similar way you specify the retry strategy, and then EF uses that strategy whenever it accesses the database.

To use this feature in the Fix It app, all we have to do is add a class that derives from *DbConfiguration* and turn on the retry logic.
Expand Down Expand Up @@ -101,4 +101,4 @@ Code sample

>[!div class="step-by-step"]
[Previous](monitoring-and-telemetry.md)
[Next](distributed-caching.md)
[Next](distributed-caching.md)
Loading

0 comments on commit 53e19c9

Please sign in to comment.