I use the data and schema comparison tools in Visual Studio a great deal. I just finished installing VS 2010 on a new VM and realized, of course, that all the saved data connections from my previous installation are not available. Is there a way to transfer these connections between installations of VS 2010?
I believe you just copy the file from
C:\Users\<username>\AppData\Roaming\
Microsoft\VisualStudio\10.0\ServerExplorer\DefaultView.SEView
from the installation with the data connections to the same location in the VM.
Related
When I open Visual Studio and attempt to connect to TFS, I get the following error message:
Error
Unexpected end of file.
I've found a handful of places online (like here and here) where people have run into similar situations but clearing the Team Foundation cache as recommended doesn't solve the issue.
I even completely uninstalled Visual Studio Enterprise 2015 and installed Visual Studio Enterprise 2017 and still get the same error.
I recently created a new TFS instance on another server for testing out some automated build features without messing with our current setup and can connect to the new TFS instance just fine.
What would cause this error?
First you could use another machine with VS installed to connect the same TFS under your account. This will narrow down if the issue only occurs on your local machine or not.
You could try to clear both TFS and VS cache issue.(You may not uninstalled the previous VS clearly).
For TFS cache:
close all instances of Visual Studio on the client machine,
manually delete the corresponding Tfs client cache folder, and then
start Visual Studio
The corresponding Tfs folders to manually delete are as follows:
Tfs 2017: "%localappdata%\Microsoft\Team Foundation\7.0\Cache\"
Tfs 2015: "%localappdata%\Microsoft\Team Foundation\6.0\Cache\"
For VS cache:
Delete the contents from the following folders
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VisualStudio
C:\Users\<<Your Alias>>\AppData\Local\Microsoft\VSCommon
Moreover, also give a try with removing the tfs related credentials from Credential Manager, close all Visual Studio instances, deleting %LOCALAPPDATA%\.IdentityService, use another user account connect to the TFS server.
Update: Op ended up doing an OS reload and haven't had any issues since.
I ended up doing a full OS reload
It was likely overkill as I'm convinced there was a cached file somewhere I couldn't locate that was holding those settings but I didn't have the extra time to fiddle with it and I needed to move to Windows 10 at some point anyway.
I'd venture to guess #PatrickLu-MSFT's answer will work for most people but for whatever reason it didn't for me.
In my case I closed Visual Studio 2017, went to the solution's directory and deleted the .vssscc file.
The file was then regenerated and the problem was solved.
I got a project which includes both a windows service (a C# project/solution in VS2013) and some SQL scripts (a SQL Server Script project/solution in SSMS 2012).
Both of these use TFS as source control.
The strange thing is that pending changes differ between VS and SSMS.
In SSMS I only see changes to files in the SSMS solution.
In VS I see all changes in both solutions except new files added to the SSMS solution.
This means I can't check in all changes in one place and have them in one change set (unless I manually add the new SSMS files in the VS Source Control Explorer).
I am pretty new to TFS (coming from Mercurial/Git) so I still don't understand how many things work, e.g. how pending changes/source control explorer detect new files.
If you are using TFS 2012 or later, you can choose either a local or server workspace from within VS. There are pros and cons to each but with the local workspace you should be able to achieve this requirement. Visual Studio will detect new files that is within it's source control and add/edit/delete as a pending change as required.
What version of TFS are you using?
I added a connection to Oracle database under Server Explorer's Data Connections inside Visual Studio Premium 2012. But after I close the solution and re-open again, the added data connection is gone. How can I keep it there?
update:
I found that the connection information is actually stored at %AppData%\Microsoft\VisualStudio\11.0\ServerExplorer\DefaultView.SEView but Server Explorer doesn't seem to read and display it.
%AppData%\Microsoft\VisualStudio\11.0\ServerExplorer\DefaultView.SEView
if you delete this file, then it is created again and it has no use.
Just delete your web.config or other config files like app.config connection strings that you don't need them again.
I test it for about half a day and deleting the unneeded connection strings from config file help me not loading again that connection string in server explorer of visual studio 2012. Wish you luck
(I'm sorry if this ought to be asked somewhere else)
I get the following error message each time I want to access some data-related feature from my VS installation:
That is either rewire my ORM of choice, or test a database connection visually through the Server Explorer, etc.
What exactly should I reinstall here?
I do have Compact Framework installed, just in case here is a list of the related programs and features installed on this environment.
You need the "Visual Studio 2010 SP1 Tool for SQL Server Compact 4.0" and same for 3.5 (assume they are already installed) - see http://erikej.blogspot.com/2011/01/sql-server-compact-40-released.html
I'll keep it short and simple. I had a OCZ Vertex 100Gb SSD that I had my operating system and programming tools aka VS2010. Anyway the drive failed and Windows went kaput, however I am able to recover certain folders including all those related to VS2010.
My question is where will the old macros be stored and how if possible do I copy them to my new VS2010 install on my new O/S ? I don't want to have to re-program all my macros again.
By default Visual Studio 2010 stores user recorded macros in "%userprofile%\Documents\Visual Studio 2010\Projects\VSMacros80", you can just copy that folder to the new drive to get them on the new install (you may have to load them manually).