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...).
Related
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.
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.
I have a custom language and debug editor extension for Visual studio, that I'd like to be able to distribute using the visual studio integrated shell.
However, I am unable to open the custom project files using the integrated shell application:
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.
- scripts, "F:\path\to\example.myproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- scripts, "F:\path\to\example.Example_sln"
Everything works fine when the extension is loaded as part of visual studio 2015 directly.
The custom project type was created using The Visual Studio Common Project System
Thanks to user rodya0 on Github, I have an answer:
Add the following:
$ShellFolder$\Common7\IDE\CommonExtensions\Microsoft\Project; \
to the PkgDefSearchPath section of the .pkgdef file in your isolated shell project
I have written an outlook add-in VSTO in Visual Studio Pro 2017 (VB.NET). I have published it which creates a setup.exe which is OK but I would like to create a proper installer that copies the files locally and can be run silently etc.
How do I go about doing this? When I go to create new project there is no installer project option.
You need to install this extension to Visual Studio 2017/2019 in order to get access to the Installer Projects.
According to the page:
This extension provides the same functionality that currently exists in Visual Studio 2015 for Visual Studio Installer projects. To use this extension, you can either open the Extensions and Updates dialog, select the online node, and search for "Visual Studio Installer Projects Extension," or you can download directly from this page.
Once you have finished installing the extension and restarted Visual Studio, you will be able to open existing Visual Studio Installer projects, or create new ones.
Other answers posted here for this question did not work for me using the latest Visual Studio 2017 Enterprise edition (as of 2018-09-18).
Instead, I used this method:
Close all but one instance of Visual Studio.
In the running instance, access the menu Tools->Extensions and Updates.
In that dialog, choose Online->Visual Studio Marketplace->Tools->Setup & Deployment.
From the list that appears, select Microsoft Visual Studio 2017 Installer Projects.
Once installed, close and restart Visual Studio. Go to File->New Project and search for the word Installer. You'll know you have the correct templates installed if you see a list that looks something like this:
I created a Visual Studio 2013 MVC project in Visual Studio 2013 Ultimate using Visual Studio Team Services through visualstudio.com. I have since reinstalled Windows and Visual Studio 2013 and have reopened the solution and receive error:
The solution you have loaded is bound to the source control server at https://{myaccount}.visualstudio.com/defaultcollection, but no workspace on that server could be located. If you do have a workspace on this server, and you want this solution to be opened under source control,
connect to that server using Team Explorer and then re-open the solution.
I am having difficulty locating how to setup and manage workspaces on my local machine and Team Services.
If you open visual studio and connect to your team project you should then be able to open the solution explorer. Once open you should see your project grated or as It is not maped locally.
Right click on your desired mapping folder level and map it to your local disk.
Note: You will need to map it to another location and pull across any uncommitted changes.