Comments
Sort by recent activity
A couple challenges with that approach: /MakeScripts Option
1) Doesn't apply the filter I'm sending to the Command Line
2) Must be used with a blank scripts folder /Scripts2 Option
1) "Error: Deployment to scripts folders is not supported by VersionedWork." - I assume this is caused by SQL Source Control having a connection to TFS.
It might still be possible to use /MakeScripts but leverage another script to filter out unwanted files, based on the business rules we need and then check only the remaining files into TFS.
Open to other options, if you have any suggestions.[/u] / comments
A couple challenges with that approach:/MakeScripts Option
1) Doesn't apply the filter I'm sending to the Command Line
2) Must be used with a blank scripts folder/Scripts2 Option
1) "Error: Deploym...
Restarting didn't solve the problem. Perhaps it is related to scripting out to a network drive? I will try locally at some point today to see if that resolves the problem. / comments
Restarting didn't solve the problem. Perhaps it is related to scripting out to a network drive? I will try locally at some point today to see if that resolves the problem.
Oh no! We can still get our changes into TFS via SQL Source Control, so we can make it work.
Was really hoping to monitor & check into test using the command line - at least I'm still able to see the potential changes. Would be used for purposes of integrating into our mechanism for version control on a wide array of file types.
Any chance it is something being considered for a future release?
Thanks very much for your help!
Edit: I see what you're suggesting now would still give us what we need (I think) - will try to implement that. Thanks again / comments
Oh no! We can still get our changes into TFS via SQL Source Control, so we can make it work.
Was really hoping to monitor & check into test using the command line - at least I'm still able to see ...
My mistake: the variable passed into the database name was null.
Would be nice if that error message were slightly more helpful, but problem resolved. / comments
My mistake: the variable passed into the database name was null.
Would be nice if that error message were slightly more helpful, but problem resolved.