Develop Reference

Synchronizing configuration between versions of visual studio

I have coworkers, who work on Visual Studio 2015, I have VS2019 and we share code through TFS.
When I make some changes everything works, but when I push code to server my coworkers cannot build the project because they have errors resulting from the fact that VS allows me new C# functionalities like internal functions, inline declarations etc. Is there a way to configure my VS so that it only lets me do the things it allows them to do? I honestly don't have any point where I can start looking into this topic.

You can choose the language version, it may solve some of your issues
I believe 20127 will be locked at C# 7.3, as shown here C Sharp (programming language)
To choose the C# language version for your projects, in the Solution Explorer
right-click on the project and select Properties
Select Build Tab
Then Select Advanced button.
This will bring up the Advanced Build Settings windows, where you can check the drop-down option for “Language Version” of your choice
Usually, you would set this to latest major or minor, though you your case you would likely choose C# 7 - 7.3, which would be compatible with 2017.
Image is for illustrative purpose only
Very relevant comments by JonasH
The langversion will be saved in the csproj file, so it should be
sufficient if it is done once. Also, the language selection dropdown
is disabled in the latest version of vs2019, but you may still edit
the csproj by hand to add it.

Using VS2017 and VS2015 C# projects in the same location, side-by-side

Is anyone out there using Visual Studio 2015 and 2017 .CSPROJ files alongside each other in the same folder? Are there any other incompatibilites, besides the solution and project files that I should worry about?
Basically what I want to do is allow our developers to continue to use VS2015 and those projects -- just for a while -- while all still working on exact same set of same code files. I don't want to move/change anything else.
I've already created all the new project files and solution file. But 'm wondering if I can just put them in the same physical disk folder alongside each other and have everyone go merrily about their development tasks with either VS2015 or VS2017.
The duplication of work synchronizing the project files themselves is not a concern. I just want to make sure there aren't any OTHER format differences that might cause some sort of build/run problem for me.
Is anyone else out out there doing this? Is this workable?

There is not any incompatibility, but you should check when you are creating a new project in VS2017 the kind of project, you should have two things in mind, first, when you are creating .net projects, you have to keep using the old .net framework instead of .net core, and second (only if you are going to create desktop/libraries/console projects), you need to use the Common option instead the new option (check on the dropdown to select the .net framework version that allows you to select versions lower than 4.5), cause if not, then you have the incorrect kind of project selected and this kind of project doesn't work in VS2015 as they change the structure of the .csproj file. Hope this little explanation helps you.
Update
What I wanted to say with this explanation is that every projects that comes from VS2015 or 2017 if they have the same structure (same old kind of .net framework), then you can do what you want to do, but if for some reason you need to make a .net core, then this will not work.
Cheers.

Just be aware that VS2017 supports C# language version features that 2015 does not. If anyone uses those features you will not be able to build the projects in VS 2015.
You can enforce language version in the .csproj files but this is done per BuildConfiguration and can be tedious to configure for larger solutions with many projects.
To make the changes
Right click the Project and select Properties
Then Build Then
Advanced (Bottom Right corner) General > Language Version
Change to C#6.0
Overall it is possible but you may need to retain VS2015 if you have any SSIS or SSRS packages as the tooling is still not available for general release (Oct 17) and is still in preview.

You should be able to run Visual Studio 2015 and Visual Studio 2017 side by side without any issues. Our application ran on both Visual Studio 2015 and Visual Studio 2017 before every developer migrated to VS 2017.
You do need to keep in mind few things though:
Visual Studio 2017 by supports C# 7.0. Make sure that you use same language version in both the IDEs.
VS 2017 also supports stuff like editor.config. I would suggest to avoid using it (though I feel it should not be an issue)
If you are using on .NET Core project without csproj. Do not think you would be able to upgrade it.

WIX Template project Cannot be found

Im working on Windows Service Project using VS2012, and when im trying to Add a Setup Project to complete my Solution
I found that I cannot add This Template to the Solution i Donno why!
I just Get this Error message
I Just Dont know why they suddenly decide to remove Setup project template away from VS2012
Does this depends on current framework used 4.0 ?
I'm working on 64bit System.

Those templates are not from the WiX toolset. They were created by someone that used our icons to make them look like officially supported templates. I asked that the author make it clearer that they are not part of the WiX toolset so there was no confusion aobut who supports them. I've had reports that those templates are high quality.

Analog of Visual Studio Solution for my application

I would like to make an analog of Visual Studio Solution for my application.
I mean to make a file similar to Microsoft Visual Studio Solution file (.sln), which includes links to all the other solution files.
Can anyone link to an article on this topic? I could not find anything about it.

If you need to build a series of Visual Studio solutions, then you need a build tool.
The two most commonly used in the .NET world are
MSBuild (reference: http://msdn.microsoft.com/en-us/library/dd393574.aspx)
Nant (reference: http://nant.sourceforge.net/)
(It's not clear what you're asking, you may wish to clarify or give an example.)

I didn't really understand what you mean, but it seems that you need a building system, like CMake (www.cmake.org).

How to create an installer and uninstaller for a Windows Forms application

I created an installer for my Windows Forms application and I added the project output to programs menu. But now what I want is 'I should have a folder in programs menu in that it should contain both install and uninstall options'.
Please help me. Thanks in advance.

The easiest way is to create a Setup and Deployment project in Visual Studio.

I have to agree with Sir Richard's answer, but I wanted to add the instructions on how add an uninstaller using the Setup and Deployment project found in Visual Studio.
Here's a useful link you can work on: How to add a Uninstall option in Visual Studio Setup project without writing code

If you have advanced scenarios that the Setup and Deployment project can't handle, I'd advise looking into WiX.
WiX is an extremely mature Microsoft opensource project, having first launched in 2004 and is still active today. It even provides a VS extension to assist you with getting started and intellisense for the configuration.
Be warned though: WiX primarily uses XML files that use MSI's domain language. It's certainly not a tool you use if "create an installer" wasn't allocated specifically in your project plan.

You can try with NSIS, is open source and very easy...
"NSIS (Nullsoft Scriptable Install System) is a professional open source system to create Windows installers. It is designed to be as small and flexible as possible and is therefore very suitable for internet distribution."
in his website you can find tutorials and examples, the link is: http://nsis.sourceforge.net/Main_Page
I hope this help you!