![]() If you or other developers want to deploy the cloud service project from different computers, however, then those other computers won't have the necessary certificate to decrypt the password. In this case, you can still use the Enable Remote Desktop for all roles option in the publish wizard. ![]() If you deploy the cloud service project from the same development computer each time, then that local certificate is available. However, the project's configuration files store only an encrypted password, which can be decrypted into plain text only with the local certificate that was originally used to encrypt it. When Visual Studio communicates with the RDP extension, it transmit a plain text password over TLS. This change also aligns with the fact that the Azure portal and PowerShell methods to enable Remote Desktop also use the RDP extension. When enabling Remote Desktop through the publish wizard, earlier versions of Visual Studio communicate with the VM through what's called the "RDP plugin." Visual Studio 2017 version 15.5 and later communicates instead using the "RDP extension" that is more secure and more flexible. This recommendation is due to a change in how Visual Studio 2017 version 15.5 and later communicates with the cloud service VM. If you're working as part of a team, you should instead enable remote desktop on the Azure cloud service by using either the Azure portal or PowerShell. You can also use the Enable Remote Desktop for all roles option if you're working only as a single developer. With Visual Studio 2017 version 15.5 and later, you can still use the publish wizard with a cloud service project. You can publish your cloud service later with these settings.Ĭonfigure Remote Desktop when using Visual Studio 2017 version 15.5 and later If you're not ready to publish, select Cancel and answer Yes when prompted to save changes. ![]() csdef files, including the password that's encrypted using the chosen certificate.Ĭomplete any remaining steps using the Next button, then select Publish when you’re ready to publish your cloud service. Visual Studio adds the Remote Desktop settings to your project's. Don’t use "Administrator" as the user name for the new account.Ĭhoose a date on which the account will expire and after which Remote Desktop connections will be blocked.Īfter you've provided all the required information, select OK. The new certificate appears in the drop-down list box. If creating a new certificate, provide a friendly name for the new certificate when prompted and select OK. Select a certificate from the list or choose. The remote access certificate must have a private key. The certificates that you need for a remote desktop connection are different from the certificates that you use for other Azure operations. This command displays a drop-down list in which you create or choose a certificate so that you can encrypt credentials information when connecting via remote desktop. link to open the Remote Desktop Configuration dialog box.Īt the bottom of the dialog box, select More Options. On the Settings page, select Enable Remote Desktop for all roles, then select the Settings. Sign into your Azure subscription if needed and select Next. In Visual Studio, start the publish wizard by right-clicking your cloud service project in Solution Explorer and choosing Publish. You can still use the wizard with Visual Studio 2017 version 15.5 and later, but don't use the Remote Desktop option. ![]() When using Visual Studio 2017 version 15.4 and earlier, you can use the Enable Remote Desktop for all roles option in the publish wizard. Configure Remote Desktop through Visual Studio 2017 version 15.4 and earlier This recommendation is due to a change in how Visual Studio communicates with Remote Desktop on the cloud service VM, as is explained in this article. For any situation in which the project might be opened by other developers, you instead enable Remote Desktop through the Azure portal, through PowerShell, or from a release pipeline in a continuous deployment workflow. With Visual Studio 2017 version 15.5 and later, however, it's recommended that you avoid enabling Remote Desktop through the publish wizard unless you're working only as a single developer. Using this option is suitable when using Visual Studio 2017 version 15.4 and earlier. The publish wizard that Visual Studio provides for cloud services includes an option to enable Remote Desktop during the publishing process, using credentials that you provide. You can use a Remote Desktop connection to troubleshoot and diagnose problems with your application while it is running. Remote Desktop enables you to access the desktop of a role running in Azure. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |