visual-studio-projects | Holds all simple Visual Studio programs

When I wanted multiple projects in a solution to share the same assembly informations (mainly AssemblyVersion), I used to use the tecnique explained here: https://blogs.msdn.microsoft.com/jjameson/2009/04/03/shared-assembly-info-in-visual-studio-projects/

Now we're working on a solution of .net core and asp.net core projects and we want all projects to share the same AssemblyVersion, but now each project's version is stored inside it's .csproj file (we're using vs2017)

I tried with generating info with true but the new file is created at build-time

Is there a way to centralize this information like in the "old" SharedAssemblyInfo.cs way?

I wrote a python script to run my vb.net project executable. The problem I ran into is when I read the lines and then use a for loop to use the individual line (IP) as an argument to my application, this does not work. However when I use any other String it does work. So it does not read the IP from ipaddress.txt but it does take an IP if entered manual as the argument instead of 'line'.

I am trying to open a Xamarin project in Visual Studio 2017 version 15.8.4, But it's not opening, It shows (needs migration).

When I try to reload it gives this popup.

When I click the Ok button, it redirects me to this page.

When I click on the link, it redirects me to this page.

https://docs.microsoft.com/en-us/visualstudio/porting/porting-migrating-and-upgrading-visual-studio-projects?view=vs-2015.

I have gone through the above link, but I am not able to solve the issue.

I am able to open this project in Visual Studio 2015.

Visual Studio 2017 About window.

csproj file

I have migrated a windows service developed in .Net 2.0 using VS 2010 to .Net 4.7.2 on VS 2017. There is a setup project which failed migration because VS 2017 does not support this project type. As Microsoft suggests here I am creating setup project using wix and have downloaded and installed wix toolset 3.11.1, Wix Extension for Visual Studio 2017 and wix VS Designer in this order and followed the tutorials to create the set up project. But I am getting the error Could not load file or assembly 'wix, Version=4.0.0.0, Culture=neutral, PublicKeyToken=c9acf360d0e036e3' or one of its dependencies.

The wix target file has the following code:

I had a few minutes this morning to try to figure out why Visual Studio 2017 rebuild all of my projects in the solution every time I try to run the project. I think I know why this is happening but I'm not sure how to fix it.

I saw these articles:

http://michaelscodingspot.com/2017/04/28/visual-studio-keeps-rebuilding-projects-no-good-reason/

https://ofekshilon.com/2015/08/16/visual-studio-projects-that-just-keep-rebuilding-or-how-quantum-mechanics-mess-up-your-build/

Which got me to turn up build logging.

I now see that VS is looking for PDB files in the OBJ directory and since they are not there(1), VS thinks the project needs to be rebuilt.

I have a .NET 4.5.2 WPF solution containing an InstallShield 2016 Express project. I'm using Visual Studio 2017. Everything was working until I updated Visual Studio to 15.3. Now the InstallShield project fails to load when I open the solution. I get this message:

These projects are either not supported or need project behavior impacting modifications to open in this version of Visual Studio. Projects not displayed either require no changes or will automatically be modified such that behavior is not impacted. For details, see More information.

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. - Setup, "C:\Develop\DxImporter\DesktopWebUiV2\Setup\Setup.isproj"

The "More information" link suggested installing the Wix Toolset Visual Studio 2017 Extension, so I did, but it didn't help.

Has anyone else had this problem, and if so, have you found a solution?