Queu-ing build opens up browser - visual-studio

I am building with TFS2017 and VS2017 but when I queue the build inside Visual Studio the browser opens up to the tfs site instead of showing the queue within VS. Is this configurable?

vNext builds can only see the build details through the TFS site, so no ability to configure this.
The old XAML builds opens directly in Visual Studio 2017 and to my knowledge you cannot configure this. VS 2015 had one update where it was changed to the TFS site, but this was reverted in the next update.

Related

visual studio 2019 open solution file incompatible

I think I was using visual studio 2017 and wrote a SSIS package. Now I installed visual studio 2019 and can't open the solution file. Error:
Unsupported This version of Visual Studio is unable to open the
following projects. The project types may not be installed or this
version of Visual Studio may not support them. For more information
on enabling these project types or otherwise migrating your assets,
please see the details in the "Migration Report" displayed after
clicking OK.
- ABC, "C:\Users\XYZ\ABC.dtproj"
Non-functional changes required Visual Studio will automatically make
non-functional changes to the following projects in order to enable
them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio
2012, and Visual Studio 2010 SP1. Project behavior will not be
impacted.
- ABC_SSIS, "C:\Users\XYZ\ABC_SSIS.sln"
I tried "Right-click on the project and reload" - didn't work.
I tried to confirm SSDT is installed:
it is installed at the installation interface, but doesn't exist in extension manager:
SSIS is a seperate extension now in Visual Studio 2019. You can install that extension in Visual Studio market place. Choose Online tab and search for "SQL Server Integration Services Projects".Hope it can help your problem
1.Extensions -> Microsoft Reporting Service Project
2.and then close visual studio
3.VSIX installer will complete automatically
4.If your project unloaded, right click on project and reload
Today I faced this issue,
Cause
The reason for issue is,
I saw a yellow bg notification at the top of IDE showing performance issue , with option to "disable this" to improve the performance.
I chose disable, later next day when I opened the project, It showed the project is not compatible.
I did Repair SSIS, Uninstall and Reinstall SSIS, and also updated the SSIS to latest version. None of these 3 ways resolved the issue.
Solution
But, I found Manage Extension submenu item under Extension menu, Under installed tab, SSIS extension was in disabled status. I reverted to Enabled status. Sample screenshot of the same for reference is here. If it disabled, simply enable it. Then restart VS with SSIS project.
Enabling the SSIS in manage extensions solved this for me.
Extensions ... Manage Extensions
Online ... Visual Studio Marketplace
SQL Server Integration Services Projects
Download
Close Visual Studio and then run the download
When finished, open your existing SSIS project and right-click the project and select "Reload" or "Reload with dependancies"
You can also now start a new Integration Services project.

Azure DevOps 2019 view build process inside Visual Studio

I have upgraded our build server into Azure DevOps 2019 and since we are more used to viewing our build process within Visual Studio I wanted to check if this is possible.
When the user right clicks the build definition in Visual Studio that the build process web view would appear as a tab inside Visual Studio instead of opening in the browser?
This is not possible.
From VS 2015 you can't open the new build system (vNext) in the VS, but only to open it in the browser.
The old XAML build still can be viewed in the VS (but is not recommended to use them...).

Why won't the "Configure Continuous Delivery" option appear?

I'm trying to set up continuous deployment in Visual Studio 2017 and got stuck on step one. I installed the Continuous Delivery Tools for Visual Studio. It appears under the Installed list in Extensions and Updates, and it has a Disable button next to it, so I assume it is enabled. From everything I've read, there's supposed to be an option labeled "Configure Continuous Delivery" when I right-click the project. Nothing new appears for me. I've tried restarting Visual Studio and rebooting my computer.
I thought that maybe it wasn't supported because it wasn't a .NET Core application, or because I'm using TFS and not VSTS. So I created a new .NET Core web application and pushed it to VSTS, and still do not have any new menu options on the project. For both projects, the repo is Git.
Which version of Visual Studio do you use? The extension Continuous Delivery Tools for Visual Studio only supports Visual Studio 2017 for now.
I tested the extension with VS 2017 (Microsoft Visual Studio Enterprise 2017 Version 15.4.4). Then option "Configure Continuous Delivery to Azure" displayed there as expected.
Please note that, you need to right click on the Solution but not the project.
Reference this article : TFVC support and other enhancements hit Continuous Delivery Tools for Visual Studio

Visual Studio 2013 Crashing When Opening Team Explorer

After opening Visual Studio 2013 successfully, I switch to the Team Explorer tab and consistently get a popup error dialog saying that, "Microsoft Visual Studio 2013 has stopped working" and "Windows is checking for a solution to the problem".
This seems to be directly related to TFS (2013 Update 4) since other tools that access TFS (like Source Control Explorer > Workspaces...) also cause the crash.
Edit: I have already tried a VS 2013 Repair. This took all morning with no different results.
This is frustrating because I cannot use TFS outside of the command-line tools. Any help would be greatly appreciated. Thank you.
Credit to Tuğrul Emre Atalay for the post: Visual Studio Crashing When Checking In.
His issue was checking in changes and having Visual Studio crash. In my case, just using the TFS tools was consistently causing a crash.
The fix for me was to only clear out the local cache and not both the server and local caches.
Clean the Cache folder on client computer. The folder path is: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache.
I cleared this folder and I was able to use all of the TFS tools without any further issues.
I then realized that this happened since migrating to a new user name. I had copied many of my settings over from my old account folder and it must have corrupted the cache area.
I had the same issue with Visual Studio 2015 Enterprises. When i open it, VS wasn't able to connect to TFS and it crashed when i clicked on "manage connections"
The issue was not about the cache (I cleared the cache, made a repair of VS and nothing changed) but about the fact that we are currently migrating our projects from perforce to Git with Team Foundation Server.
When Visual Studio starts, it seems VS is trying to connect to TFS with linked Git repositories, but since the plugin currently used is perforce, it causes an exception somehow.
The solution is to set your source control plugin to Microsoft Git Provider (or Visual Studio Team Foundation Server if you are using it)
Here's two screen shots I took. Right after I selected the Microsoft Git Provider, the Team Explorer tab automatically refreshed and I am now able to connect to my projects.
Go to Tools -> Extensions and Updates Look for Github Extension for Visual Studio and Uninstall it
Never Mind as you can still work with Github
Now Restart Visual Studio.
Enjoy working on Team Explorer.

Umbraco Development Setup Visual Studio

I am a new developer for Umbraco. I am having problem setting up my Visual Studio 2010 as a developer platform for umbraco 4.5.x with TFS and between remote teams.
My current setup is to open the whole umbraco site in Visual studio and tideup with TFS. Obeviusly this means that some of the files and folders gets locked up when commiting to Source control. Problem is this causes the problem when running umbraco as umbraco tried to write to certain files.
Any idea what type of typical setup would be like for VS 2010 and umbraco?
thanks,
Preyash
This should solve your problem =)
EDIT: Link updated
http://our.umbraco.org/wiki/codegarden-2009/open-space-minutes/working-in-visual-studio-when-developing-umbraco-solutions
I made a VS2010 umbraco project template, that configures the commands used to copy files to the umbraco folder on build, like described in the above link.
http://our.umbraco.org/projects/developer-tools/visual-studio-2010-project-template
Is it mandatory to use TFS as your version control?
We have used Mercurial and Visual svn server as version controls in our projects.
In this i feel Mercurial as more comfortable for Umbraco projects.

Resources