Sublime TFS Settings - sublimetext3

When working with Classic ASP, Sublime is AWESOME, but what has been stopping me so far is the fact that at work we use Visual Studio Team Services (previously Team Foundation Service) to Check-out / Check-in files we edit and work on and that goes rather well with Visual Studio 2012 that we use. But VS is so slow compared to Sublime especially when all I care about is editing text.
Today I found out that Sublime Text (I use Version 3) has a plugin for TFS! So I installed it (also installed the TFS Power Tools 2012). But now I'm confused as I can not see any visual clues to my files like I do with Visual Studio 2012, so I don't know what files are up to date, and what files need checking in ... etc.
After reading the official page of the Sublime TFS plugin. I understand that I need to set tf_path somewhere! The page though doesn't say where and in what format :( I am lost.
Where do I set the tf_path and in what format?
Any help would be great, Thank You.

Navigate to Preferences -> Package Settings -> Sublime TFS and open both Settings - Default and Settings - User (which will be an empty file). Copy the entire contents of the default settings file to the user file, then change any paths to reflect your personal setup. Save the user file (you are not allowed to modify the default file, just close it), restart Sublime for good luck, and you should be all set.

If you want your Sublime Text changes to be seen in Visual Studio Team Explorer, then you can change your Workspace to a local one.
For more information: https://www.visualstudio.com/en-us/docs/tfvc/decide-between-using-local-server-workspace
Like this, you can use Sublime Text for editing and have as much ST windows as you want. And you can do the check-in of files using the Team Explorer. This is how I work. One Visual Studio with one or more Sublime Text windows. Very light-weight, efficient and productive.

Related

When we compare local version with server version in Visual Studio, how to make the local version editable?

I found that sometimes when I use "compare" in Visual Studio, I couldn't edit the local version at all. But sometimes it does allow this. Is there any setting in TFS that is related to this functionality?
The steps I followed:
Right clicked the file in Solution Explorer I want to compare, and chose "Compare", with the dialog window popped out like this:
and cliked "OK"
I found several questions similar to my question, but amazingly all of them don't have even a relevant answer:
Visual Studio Diff Tool - When is Editing Allowed?
Under what conditions will the Visual Studio 2012 Difference Viewer allowing editing a source file

Pressing Ctrl + S automatically opens Output window

Whenever i press Ctrl+S from keyboard or whenever i click on any file in Solution Explorer it automatically opens output window only in Visual Studio 2012.
I tried
Tools > Options > Projects and Solutions > Show output window when build starts
I am using Visual Studio Professional 2012
But its just not working. Its irritates a lot. Please suggest how to get rid of it.
if someone is facing this issue in visual studio community 2015, in my case the issue was caused because of the use of Backup and sync utility from google, I have synced my source directory to my google drive to maintain the latest copy of source backed up.
The backup utility locks the file which you might be editing for syncing it to cloud storage. since the file is locked by another process, the visual studio cannot save the changes in the file.
The fix was to pause the syncing for the time you are doing frequent changes.
In your case, it might be some other process which might be locking the file.
If you're using an extension, one of them could be the reason.
I had the same problem while saving the CMakeLists.txt files. I checked one of the extension's setting, "CMake Tools", it has a "Cmake: Reveal Log" settings which causing this problem. I simply deactivated it
I suggest you to check extensions' settings or try to find on settings with searching "output", "focus" etc.

How do I add folders into the Solution Explorer for Visual Studio Express 2012 for Web?

I am very new to Visual studio, so I am trying to learn the basics.
I have read so many articles but some are for 2012, some are for the non-web version, etc, but I seriously can't find a solution to such a simple task as this.
I am using Visual Studio Express 2012 for Web, and have created a "Blank Solution".
I end up with this view:
Now my goal is to add all my existing files and folders and have it shown in Visual Studio.
So, I have located my solution file on disk and copied all my files into the same folder:
Now, I know its possible to add single items into the view by right clicking and picking add item:
But I cant include folders here. I have tried to drag and drop, I have read guides about using the "Show all files" button, but apparently that does not exist for the Web version of Visual Studio 2012.
Could anyone please tell me what the proper way is to include all my files into the solution explorer?
I just had this same problem in Visual Studio 2012 Ultimate. I know your question is about Web but maybe this will work for you too.
Assuming the files/folders you want to include are in your solution folder, from the Project menu toggle on "Show All Files", then you should see the files/folders in Solution Explorer. Select those you want to include, right click and choose "Include in Project".
A solution contains one or several projects and no solution-wide files (normally). Create a project, and then follow How do I add an existing directory tree to a project in Visual Studio? to add the files.
(It was a long time ago I did it this way, and with an earlier version of Visual Studio, so YMMV.)
I think that the best way to do it is to simply drag&drop desired folders with files between file explorer and solution explorer in VS. I've just tested it and that works the best for me.
You can place your files in the Solution folder and refresh the solution explorer :) It'll automatically add your files, I do it for 2010 and think it'll work for 2012 as well
In solution Explorer top toggle,You can find few icons, Find Show all files and click on it.Navigate to the folder exactly matching the same address in your visual studio and you can see a folder which is newly added into your project,Which is displayed as a dotted folder and right click on it and include it into project.
Don't forget to convert the project into Web-Application.
Thanks.
I actually found the solution.
So in solution explorer there is a button "Solutions and Folders" screenshot
When you pressed it your project folder would be opened. You find the folder that you need to add, copy it (screenshot), return to project solution and past it

Visual Studio 2012 doesn't convert vs2010 solution?

I opened my vs2010 solution with vs2012 but it didn't make any conversion as from 2008 to 2010 was happening. So my solution still remains the same as 10 label on it. when I make a new solution of course it has 11 label on it. I haven't got any problem running like that but I am curious. Is there any difference? if yes, how to convert into vs2012 solution?
I managed to 'convert' the solution file to change the line containing '# Visual Studio 2010' to '# Visual Studio 2012' in the .SLN file.
Manual editing of the solution file is not necessary, or recommended. Simply open the VS2010 solution in VS2012, left-click the solution (at the very top of the Solution Explorer), then use File | Save As to overwrite the original file. This will effectively convert the VS2010 solution file to a VS2012 solution file.
There are some exceptions, but mostly you'll be able to open the same project and solution files files in both VS2012 and VS2010 SP1.
VS2012 may convert projects when you first open them, but the changes are (except noted in the document linked) backward compatible with VS2010 (ie using conditionals where needed to only apply to either version when loaded) Most project types will be left entirely untouched though.
It is about Visual Studio 2012 Compatibility
If you created your assets in Visual Studio 2010 with Service Pack 1 (SP1), many of them will load and run in Visual Studio 2012 without any further action on your part.
Many assets will also open again in Visual Studio 2010 with SP1 without any issues, even after you open those assets in Visual Studio 2012
For C++ projects it makes a difference, as the 2012 compiler (VC11) will only be used on projects that are explicitly 2012, not on 2010 projects opened in VS 2012. Some C++11 improvements are available with the VC11 compiler but not with VC10 (see this SO Answer for a summary), including:
Range based for-loops
New standard library headers (atomic, mutex, thread,...)
Smaller standard library container sizes
(And more to follow when the Nov 2012 CTP is delivered to VS 2012)
In order to convert from VS 2010 project to VS2012 there is no need to manually edit the solution file or 'Save As' over the existing project. Instead:
If you decline the update when first prompted, you can update the project later by opening the Project menu and choosing Update VC++ projects... [at the top of the menu options]
From MSDN's "How to: Upgrade Visual C++ Projects to Visual Studio 2012"
(This page was linked from #Joachim's MSDN link, but I wanted to have the answer here on SO since a number of other answers suggested manual workarounds instead of this VS 2012 feature)
In my case, I had some Visual Source Safe stuff (my project was created with Visual Studio 2003/2005, yes, very old!)
Once I manually removed the VSS stuff, the conversion succeeded.
PS: I know it's about VS2010, but maybe this helps others.
You can convert a project from VS2010 to VS2012 by doing the following:
Add the 2010 project to your VS2012 solution by right-click on your solution in the Solution Explorer and Select Add --> Existing Project...
The project will appear in the solution and will have (Visual Studio 2010) appended to its name.
Right-click on the added project and select Properties.
In the Configuration Properties --> General pane, change the setting in Platform Toolset field to Visual Studio 2012 (v110)
Repeat for each configuration type, e.g. Release and Debug.
I came across this question while googling for a solution to a specific problem: MSBuild was failing to execute the Publish target against a VS2012 solution that had started life in VS2010 when called from the command line (specifically through TeamCity):
error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
MSBuild was looking for the Azure SDK 2.3 targets in the VS10 location (C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v10.0\Windows Azure Tools\2.3\Microsoft.WindowsAzure.targets). The cause is explained by Sayed Ibrahim Hashimi in a blog post and, as I understood it, boils down to some decisions they made while enabling cross-version compatibility for solution files. The solution was simple: add the VisualStudioVersion property to the MSBuild invocation, something like this:
msbuild.exe MyAwesomeWeb.sln /p:VisualStudioVersion=11.0
Practically speaking, this overrides the following in each csproj file:
<VisualStudioVersion Condition="'$(VisualStudioVersion)' == ''">10.0</VisualStudioVersion>
Presumably you could get the same result by editing all of these by hand to replace 10.0 with 11.0 but that might break backwards-compatibility -- I haven't tried it. I also haven't tried an update to VS2013 to see if the problem persists.
So to wrap this up by answering the question: yes, there are some differences before you "convert" (using any of the methods offered by other answerers) and some differences remain afterwards.
This is slightly different, but along the same lines so in case it helps anyone:
I was loading a project where it looked like it was loading and then kept showing all projects as unavailable. No errors were on the migration report. I tried reloading the solution and projects many times, using various methods including suggestions here.
Finally I found a "Resolve Errors" option when right clicking on the solution in the Solution Explorer. VS went through a load process again and it worked; no problems.
I don't know what it did differently that time, but apparently it made a difference.
it's to simple just edit the .sol file
change the version to 11
like this
Microsoft Visual Studio Solution File, Format Version 12.00
Visual Studio 2012

Is it possible to download source tree from TFS Azure without using Visual Studio?

I'm looking around mysite.tfspreview.com and I can view individual files, but I couldnt find a download all or get solution option.
So if a colleague doesnt have Visual Studio 2010 available and they wish to download a solution from TFS Azure preview what are the available options?
You should be able to use the command line client in the Microsoft Team Explorer Everywhere 11 Beta. It's not a big download (11MB), but I don't think there is a way to download a source tree directly from tfspreview without a client unless a zip has been added. Other source control services work this way (github, jira etc)
You don't need visual studio, but you need Team Explore which is add-on for Visual Studio or can be stand alone, it exists on the TFS media (DVD) or ISO, once you install Team Explore, you can access TFS Preview using GUI or Command line, you can also install TFS Power Tool 11 Beta, that will give you windows shell integration, so the context menu of the windows (when right click) it will has command to interact with TFS, as #Simon said, you can install Team Explorer Everywhere 11 Beta, but this for none windows OS or for add-on for other IDEs
Visual Studio Online has provided a means to do this (partly). On the website, navigate to your project's 'CODE/Explorer' tab. Right-click on whatever source directory/branch you wish and click the Download as ZIP menu item.
This will download a snapshot of whatever it is you selected. While extracting this won't "magically" link the files back to Visual Studio Online (ie, changes made will not be able to be committed directly from Windows Explorer, etc) or give you direct access to history; it will retain any source control bindings in any Visual Studio projects. This may be a good or a bad thing, depending on your circumstances.

Resources