How to link SQL Source Control to SQL Connect
I see the option to connect with SQL Source Control, but I don't have a RedGate.ssc file on my disk. I see the file is checked into the SVN Server though.
Running Windows 7 64-bit - perhaps I'm not looking in the right area?
We’re looking into this now and have emailed you for more information.
If anybody else hits the issue please do send us your most recent log file from this location:
LOCALAPPDATA\Red Gate\logs\SQL Connect 1
You can email us on: sqlconnect [at] red-gate [dot] com
More information: even when I start over and import only one SQL Source Control project, I only see the Synchronize dialog the first time I try; after that, it goes to the "Get Started" dialog.
One step forward, one step back . . . thirteen rg projects loaded and look good, but when I right-click and choose "Synchronize project and database", the "Get Started" dialog box appears, asking me to create or import. This works correctly in my small test solution with just one .rgproj --- what is wrong?
Indeed it is, thank you.
Now I'll have to use that unload/reload workaround, since I have over a dozen databases :-( Wish me luck.
AdminDavid Atkinson (Admin, Red Gate) commented
The SQL Connect panel can be invoked from the View menu in Visual Studio.
I would like to do this. Unfortunately I cannot get to the "getting started" panel --- I've seen it once (the first time I ran VS after installing SQL Connect) and I haven't seen it since. How do I get it back?
AdminNick Sutherland (Admin, Red Gate) commented
Try following these steps:
1. Use your source control client to checkout the repository linked with SQL Source control
2. Click on the "Import existing SQL Source Control Project" link on the SQL Connect getting started panel
3. Browse to the local directory where you checked out the repository in step 1 and click the Generate button
This will create a new SQL Connect project linked to the same repository as SQL Source Control
To link SQL Connect to an existing SQL Source Control repository, you will need to do a SVN checkout of the SQL Source Control files.
To do this, you can use any SVN client (e.g. http://tortoisesvn.net/) to checkout the files. TortoiseSVN have a guide on their site about how to do a checkout. (http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-checkout.html)