TFS Migration script unusable with custom port
When clicking the "Add a Migration Script" link on the Commit Changes tab, the TFS url and port are read only. As we use TFS on port 80 instead of port 8080, we cannot use this feature.
The same applies when setting up the link on the Setup tab.
Migrations in SQL Source Control 5 no longer requires a separate repository, so you should now be able to use it with your setup.
If you don’t have the tool installed, you can download it from http://www.red-gate.com/products/sql-development/sql-source-control/.
If you already have SQL Source Control you can get the new version via Check for updates in the Help menu of SQL Source Control inside SSMS.
Thank you for sticking with us while we worked on this, and please keep the feedback coming!
AdminJeff Foster (Admin, Redgate) commented
In the next release (which'll hopefully be available shortly via the Check For Updates mechanism), we have improved the way that TFS ports are handled. We no longer split the URL into host / port, instead requiring a URL to give the port details if it differs from the default. In your case, it sounds like you'll just need to specify the URL as http://yourserver/yourpath and we'll now do the right thing.
I'm afraid you will need to unlink and re-link your database from source control to be able to update the Migration Script URL to include a port number.
When re-linking the database to the schema repository, the migrations folder url field should also be enabled. You can then include the port number in the url.
We hope to add the ability to edit repository URLS (including Migrations Script location) in the future.
Ok, using Win 7 64bit. SSC v188.8.131.52 & SSMS 10.5.2500.0
My database is linked to TFS and I can check items in, etc... Migrations folder is not setup.
Clicking "Setup Link" for the migrations folder BOTH the url and port are read only.
Very disappointed that this port issue still exists in the product as I had raised this as an issue FIVE months ago (ref SOC-3044).
I believe there is a workaround for this; you can specify a port in the Migration Scripts repository URL field. For instance to specify port 8081 I would add the following:
If you have already connected to a Migration Script location but against the wrong port, you will need to unlink and re-link your database from source control to be able to edit the Migration Script URL.