I am trying to check for my build definition under team explorer build option. I am not getting any options. It is blank.
Any idea how I can get my Build definitions.
I am working in VS 2013
If you are using the same user account on another system in VS2013, this issue seems only related to your local VS 2013.
Try to close the VS, clear both TFS and VS cache, then reopen it.
Related
I have a WebJobs project that I've been working on in Visual Studio 2017 for some time. The solution is also checked into a repository on VSTS.
I also have Visual Studio 2017 Preview version installed on my computer and I mistakenly opened my WebJobs projects in this version.
First, I noticed that my solution was no longer bound to the repository and I could not check my code in.
I then opened the solution in stable version of Visual Studio 2017 and click "Add solution to source control". When I look at the binding, it seems to be pointing to the right repository but under "Pending Changes", I don't see all the changes I've made to the project.
Is there a clean fix to this? Otherwise, I'll kill the repository on VSTS, create a new one and do a clean check-in. I'd hate to go through that process though if I can fix the problem.
UPDATE:
When I click "Workspaces", I see my computer's name and "Workspaces..." options and if I select "Workspaces...", I can see all them on my computer. In the "Edit" view, they even seem mapped correctly. But as you can see in the image below, it shows the "Local Path: Not Mapped".
I've been working with several projects I have hosted on GitHub, but recently I haven't been able to check in any changes. Every time I save a file, VS treats the file as if it's checked in, lock icon and all. I can't make any commits because of this. I've had this occur in VS2013 Community, VS2013 Pro, and VS2015 Ultimate CTP. While restarting VS works in the 2013 versions, it does not work in 2015.
While searching for an answer, I came across this SO question. The answer did not work for me, as I am using GitHub, not TFS with a Git project ("Connect To" wouldn't show my project). In addition, I have not renamed any of the projects that have had this glitch. Is there anything I can do besides report the bug to MS?
To all the people which have this kind of problem using Visual Studios Git Source control.
One solution which worked for me since all other i found failed was to create a .gitignore file via Visual Studio. This somehow stopped the automatic check in which happened during a filesave.
Team Explorer -> Settings -> Repository Settings -> Ignore & Attributes section -> Ignore File -> Add
I am currently using Visual Studio 2015 update 1.
Every time I try to build my solution in VS2013, nothing builds, no errors - But in the status bar it says: "This item does not support previewing"
I googled around a bit but have come up empty.
But if I right click on each project and select build it works fine.
Any ideas?
Perhaps this message is totally unrelated... Post hoc ergo propter hoc
Steps to reproduce on my machine:
Right Click any project in solution: select build
Status bar displays Build successful
Right click solution select build
Status bar displays : "This item does not support previewing"
Perhaps it isnt related, but it sure does appear to be.
I was able to fix this... Somehow nothing was selected to build in the solution configuration. I right clicked on the solution, went to properties and then selected COnfiguration Properties and clicked the Build box for all the projects...
I have no idea how they became unchecked, only thing I can think of is a co-worker was trolling me.....
I've had this problem (i.e. debug not starting, and no error message) with Visual Studio 2015 in the following two cases:
after loading a solution that had previously been built with Visual Studio 2010
and also after using the "save as" function in Visual Studio 2015 to update a solution that had been started with Visual Studio 2010 (using Save as updates the solution file and sets the active Visual Studio version to 14 - i.e. VS 2015).
In both cases, deleting the bin and obj directories under the startup project fixed the problem. It's also worth closing visual studio and making sure that there are no {yourprojectname}.vshost.exe processes still running - if there are then kill them before running visual studio again. On that note, if you have multiple versions of visual studio on your machine, you should also check that you don't have the same solution open in the other version of visual studio at the same time (I've done that one myself).
One of the comments here suggests disabling the "enable visual studio hosted process" option. Don't do that if you can at all avoid it: you'll lose lots of debugging functionality (particularly in the area of being able to edit code while your solution is running).
Hope that helps someone out there.
Solution for VS2015
"this item does not support previewing" vs2015 (Visual Studio 2015/2016)
Step 1. Go to Control Panel -> Programs and Features
Step 2. Uninstall all: Windows Software Development Kit - Windows 10.0.10586.15 (maybe you have diff ver)
Step 3. Download new latest Windows Software Development Kit
https://go.microsoft.com/fwlink/p/?LinkId=619296
Install & Create new project, Done!
Dclick on MainPage.xaml and you will see Loading designer...
1: Add below lines in App.conf
<specFlow>
<unitTestProvider name="MSTest"></unitTestProvider>
</specFlow>
2: add a reference to Microsoft.VisualStudio.QualityTestTools.UnitTestFramework.dll
right click on your project and select: Add Reference
3: add using Microsoft.VisualStudio.TestTools.UnitTesting; in Step Defination
4: goto feature file and run it. This is what solve my problem on vs2013
I faced same issue with .aspx file. I just right click on the .aspx file and select open with (HTML Editor). You can choose any form the list.
I have come across the same issue for me, I have opened a project in VS 2010 and then when I open the same in VS 2015 then his error has occurred.
Solution:
By Closing the VS2010 project solution fixed the issue.
I'm trying to open a TFS Build Process Template (DefaultTemplate.11.1.xaml) file, incorporating an activity from Community TFS Build Extensions. I'm following instractions from here, section Get the custom activities into Visual Studio. I had no problems with that back in the RC version of Visual Studio 2012 but now, after upgrading to the release version, an attempt to open the file ends up in an error:
System.Xaml.XamlException: 'The type ‘InArgument(mtbwa:BuildSettings)’ of property ‘BuildSettings’ could not be resolved.'
TFS itself doesn't seem to have any problems running builds based on this template.
I am able to open the file without the trick, but then of course the custom activities are not displayed properly.
Check this out:
http://blogs.blackmarble.co.uk/blogs/rfennell/post/2012/08/30/Type-InArgument(mtbwaBuildSettings)-of-property-BuildSettings-errors-in-TFS-2012-RTM-builds.aspx
Quote:
"if the Visual Studio class library project you were using to manage the process template editing was targeting .NET 4.5, it needed to be 4.0. Well with Visual Studio 2012 RTM this is no longer the case, in fact it is the other way around."
I don't really think this is a great answer but I don't have enough rep to comment...
Build action on the xaml file is set to None?
I had a similar issue when opening build templates in VS 2012 RTM, but I was able to open the xaml "a little," meaning that I could open it in the workflow designer, but a lot of it was just the error activity. I found some errors to the effect that I should add references which I had not needed before (neither in VS 2010 or VS 11), such as PresentationCore and PresentationFramework. I wish I remembered more detail to pass on to you on this point.
I have a problem that is described here: TFS: cannot set up new build
I use Visual Studio 2008. Unfortunately, the solution provided there, didn't help.
I tried to remove and add again my TFS server - no help. Also, it's not a problem with security policies or lack of proper right, because I can initiate a new build, with the same user through Visual Studio 2005, also installed on my computer.
In addition my colleagues have no problems at all.
If someone else have experienced similar problem - I will appreciate any help !
If your getting the red cross it is likely that it is a permissions problem. From the 'Team Explorer' window within VS2008, right-click on your project node and select the 'Team Project Settings->Group Membership' menu option. From there trace down the group that your user belongs to.
Next, again right-click on your project node in the 'Team Explorer' window, this time selecting the 'Team Project Settings->Security' option. Within this dialog, find the security settings for your user group. Ensure that the 'Allow' checkbox is set for the 'Start a build' property. Confirm any changes and exit.
I have found that it is best to restart IIS on the TFS server to ensure that the chances are picked up.
Good luck !
Here is what I did. I don't know why the problem is fixed, but it's ok ... for now.
I installed the Microsoft Team Foundation Server 2008 Power Tools and exclusively installed the integration of the tools with Visual Studio. Then I did the following instructions again:
I decided to add my user (just me, not from some domain group) in to the permission menu options ... Then, from security option menu I checked the 'start a build' option at my user and restarted the Visual Studio.
After restarting the Source control menu is a little bit different from what it was before, but at least I can start builds now. Hope It's forever :)
Is the server running TFS 2005 or 2008?
Have you tried running the diagnostics in the BPA Tool?
EDIT:
Team Build had many breaking changes between 2005 and 2008. VS 2008 cannot create new build definitions on a 2005 server. Details: http://blogs.msdn.com/buckh/archive/2007/07/27/team-build-compatibility-between-2005-and-2008.aspx