When you change from the default URL to the HTTPS flavor, expect to have some issues. URL rewriting helps, but doesn't solve all of the issues. For example, I needed to refresh all of the build/release definitions. Also I found that some projects (SSIS in particular) keep a reference to the TFS server URL in the project file and so will try to revert the client back to the old URL. This is aggravated by different VS versions because the process for updating the URL on the client varies, so different steps are required.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
ID: 701be5af-1f51-3ac6-8e1d-b4472e6d34a2
Version Independent ID: ff7783d7-c0e5-25ff-4d02-f2c3c2f34d95
When you change from the default URL to the HTTPS flavor, expect to have some issues. URL rewriting helps, but doesn't solve all of the issues. For example, I needed to refresh all of the build/release definitions. Also I found that some projects (SSIS in particular) keep a reference to the TFS server URL in the project file and so will try to revert the client back to the old URL. This is aggravated by different VS versions because the process for updating the URL on the client varies, so different steps are required.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.