How to Compare Files in Visual Studio 2019 Horizontally? - visual-studio-2019

I was trying to use the built in file comparison tool in visual studio 2019 and I dont see an option to display the files horizontally vs side by side. Any way to change this ? Thanks in advance for any replies.

Related

Cannot find all SpecFlow Options in Add New Item in Visual Studio 2022

I am using SpecFlow in Visual Studio 2022. I have installed SpecFlow for Visual Studio 2022 extension. But I cannot find all SpecFlow templates when I want to Add New Item. I can find only three of them.
Can anyone help?
They are not there, because we didn't implement them for Visual Studio 2022.
This issue is https://github.com/SpecFlowOSS/SpecFlow.VS/issues/73
We are happy to add additional ones, but nobody yet answered me which of the missing ones you need.

C# & Visual Studio : storage issue

I have a problem with Visual Studio.
When I create a new project and start programming and in between I save, at some point when I want to run it, Visual Studio does not accept my new code. It always executes the old code although I have overwritten it.
I have already re-downloaded Visual Studio 2 times but that didn't help. I use Visual Studio Community 2019
Try using Ctrl+shift+B to build it, and then running with F5, instead of Ctrl+B or F7.

How to open Work Item in browser using VS 2019 Team Explorer?

I have installed Visual Studio 2019 to do some testing on our code base ready for migrating from Visual Studio 2017, I am also testing to ensure it plays nicely with our TFS system (currently TFS 2018 on premises).
It looks as though the Visual Studio Work Item Form is back! (VS 2017 dropped support for this in favour of opening Work Items in a web browser). I've not managed to find any information on this. I like the fact that we might have the option to work with Work Items in the VS IDE as well as the web browser, however its return introduces a few issues:
We use a custom MultiValue control that does have support for the VS 2019 Team Explorer (it last worked in VS 2015). Do you know where I can get hold of a MultiValue control that will work on the Work Item form in the VS 2019 Team Explorer?
Given that the MultiValue control isn't working I would like to continue working with Work Items in a browser. The VS 2019 Team Explorer seems to favour opening Work Items within the IDE, how can I open them in a browser from within the VS 2019 Team Explorer? Better still, how can I configure it to open in a browser by default?
Is there a better place for me to ask these questions?
Work Items should default to opening in the web in Visual Studio 2019. That behavior has not changed from Visual Studio 2017.
There is an option under "Tools->Options->Work Items" to enable the "Legacy experience (compatibility mode)". It sounds like that option has somehow gotten enabled in your installation. If you switch that back to "Default experience", work items should open in the web.
Hope this helps.
Sorry for the inconvenience. This is a designed behavior right now.
Please take a look at this similar issue: TFS work items opened inside Visual Study no longer open in the web browser, they always open in the Visual Studio editor
According to the response from MSFT:
We have re-design the default landing page for work items in Visual
Studio 2019 which only works with server >= 2019. If server is <
2019, work items will be open in Visual Studio only.
Since you are using TFS 2018 with VS2019, you may have to open work item in web portal from browser directly right now. Otherwise, you have to upgrade your TFS version from 2018 to Azure DevOps 2019, if you insist on opening the work item in Visual Studio.

How can i add Jenkinsfile support to visual studio 2017

I am using Visual Studio 2017 Pro, and i am being driven crazy by the lack of syntax highlighting for the Jenkinsfile in my project. I am using the Declarative Syntax, but i just cant seem to find anything on getting this to work. My research says that its based on groovy, but i dont see a way to map it to that language either. Any help is appreciated.
This might not be a solution for everyone, but for me, it worked:
Jenkinsfiles are the only files without extension I am working with, therefore I opened
Tools -> Options -> Text Editor -> File Extensions
and then, I checked "Map extensionless files to:" and selected "Javascript Editor"
This does not require to install any extension and the display is great
I am in the same boat. Using Visual Studio 2017 Enterprise.
I found this extension recently for Visual Studio Code and this extension for Visual Studio.

migrate a asp.net mvc solution file from 2010 back to 2008

i did an upgrade and it caused lots of problems. unfortunately i didn't back it up. Is there anyway i can convert a 2010 solution file back into asp.net mvc 2008?
Make a backup of what's left of what you currently have before doing this ...
Create a new solution in Visual Studio 2008. Create new projects for the 2008 solution. Use the project menu or right-click the project and choose "Add Existing Items..." Choose all the code files .cs .vb, etc from your 2010 structure and include them in the 2008 structure.
Basically you're copying all the code back into a 2008 structure with the 2008 formatted project and solution files. The code shouldn't be substantially changed beyond repair. You might have to manually address some issues in the converted code but once you know what they are it will be a repetitive process more than anything.
If you are writing code of any importance you should be using a version control system like as SVN. I haven't tried Visual Studio 2010 yet, but can tell you from experience that the differences between 2005 and 2008 are laughably small. You can down convert a 2008 solution file by manually changing the first two lines from:
Microsoft Visual Studio Solution File, Format Version 10.00
Visual Studio 2008
to
Microsoft Visual Studio Solution File, Format Version 9.00
Visual Studio 2005
the project files are fairly trivial as well with the product tag changing from:
9.0.21022
to
8.0.50727
Please note the changes I have listed for project files may not be 100% accurate and I have not tested for differences between service pack releases. However, creating a new project in an earlier version of Visual studio, making a copy and then doing an upgrade should allow you to run a diff and provide a better answer than what is currently accepted.

Resources