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

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

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.

VS2015: Xamarin license file is invalid

I'm using Xamarin with Visual Studio 2015. After a recent upgrade of the Xamarin plugin, I'm getting an error the first time I try to "Clean Solution" or "Build Solution" after launching Visual Studio:
The Xamarin license file is invalid and could not be recovered. You will still be able to access the Xamarin features that are included in Visual Studio Professional.
The error dialog offers a single option: "Use Visual Studio Professional". If I choose that option, I can re-try whatever operation I was using and it will work fine, and continue to work fine until I exit and re-launch Visual Studio.
I have found some older threads where people mention what seem like similar problems, but the solutions refer to using Tools->Xamarin Account, which does not appear anywhere in my Visual Studio "Tools" menu.
Specific versions in play:
Microsoft Visual Studio Professional 2015 14.0.25431.01 Update 3
Xamarin 4.8.0.754
Xamarin.Android 8.1.0.13
I have this same problem with a couple of different, unconnected solutions (one of which is using Xamarin.Android, another of which uses Xamarin.Forms).

Can I use Visual Studio Community 2015 without .NET?

I'm looking for a new html/jquery/css IDE to edit and publish existing websites. Can I use Visual Studio Community 2015 to edit a website that doesn't use .NET and publish it to a server using ftp?
Yes you can use Visual Studio as your main editor. Select any ASP.NET project as your starting point, delete everything in the project and you're good to go. You can add a Publish Profile to enable web deployment (which supports FTP).
It will require the concept of a "Project File" for most features to work well. There is the old Web Site project which just works on any folder, but that hasn't seen much love in the past years. It's new cousin is being introduced with Visual Studio 15 (which will likely be Visual Studio 2016 or 2017).
As an alternative you may want to look at Visual Studio Code as well, it's the light weight cousin of Visual Studio Community Edition and is suited perfectly for the kind of work you're planning it seems.

TFS Windows Explorer Integration - Getting version history outside of VS

I worked for year using CVS source control with Windows Explorer integration using TortoiseCVS which enabled me to view the history of my files in a graphical way and allow me to compare any 2 versions of the file without the need to open IDEs.
Lately I started working in a new place that uses TFS which require me to open Visual Studio every time I want to see the file history.
It would be great to have this level of integration between TFS and Windows Explorer. I wonder if any third party has developed such functionality?
Currently I use C# with Visual Studio 2013.
This is what I see when I choose Revision Graph:
Shell integration can be installed as part of the Visual Studio Power Tools for Team Foundation Server 2013. Make sure you check the "Windows Shell Extensions" option.
To see the revision graph, I am afraid you still need to open Visual Studio and use the Track Changeset feature which seems the closest as far as I can tell.
That and the "Incoming Changes" codelens that was added to Visual Studio 2013 Ultimate and which is going to be part of Visual Studio 2015 Professional and up.

TFS Build notification options not populating build definitions

downMy gated checkin reconcile message has stopped working. To troubleshoot I opened up Build Notifications options and see that the "Build notifications to monitor" list is blank.I restarted Visual studio, connected to the project server again in the IDE, rebooted the machine but still Build notification options are blank.
I have also deleted the Team Foundation local cache from %localappdata%/Microsoft/Team Foundation/5.0/Cache but to no result.
From what i understand the Build notification desktop tray app gets the connection to the server from the Connect option in Visual Studio IDE. All the settings look right but the problem persists. Any suggestions?
P.S : I have recently downgraded from Visual Studio 2013 Ultimate to Visual studio 2013 Pro.
Each version of Visual Studio (2010, 2012, 2013, 2015 etc) installs its own newer version of this tool. Each under a different path that contains the Visual Studio version.
Make sure you're launching the correct one, or register your TFS version inside the latest version of Visual Studio installed and use that (since it will be able to connect to any and all versions of TFS).

Resources