SLN Project File Shows As Incompatible

[Jamil Taylor]

I am not sure what introduced this issue, but this is recent. When I open a Visual Studio 2019 SLN project file, it shows as incompatible within the solution explorer. I have tried uninstalling PowerShell Pro Tools then reinstalling the latest version. This issue remains. I am not sure what changed to cause this. The SLN file is simply a text file. A fresh PowerShell Pro Tools install did not resolve.

The PowerShell script executes without issue within Windows. This is just a Visual Studio 2019 Enterprise issue it seems. I have version 16.6.1.

I have attached the SLN file that shows the issue if this helps.

Below is the solution explorer screenshot:

‌

[Jamil Taylor]

I am now attempting a full repair using the Visual Studio 2019 Installer. This will run for some time, and I will report back if this resolves the issue.

[Jamil Taylor]

I performed a full repair and rebooted afterward. incompatible still shows as per my screenshot above.

[Adam Driscoll]

Is there any way you can share your PSSProj file? The solution is loading but the project is not. You are running version 5.5.0 of PowerShell Tools for VS?

[Jamil Taylor]

I currently have version 5.5.1 installed. It was just updated today.

‌

[Adam Driscoll]

This is loading fine in my environment so there must be some sort of installation issue happening.

Can you please grab the ActivityLog.xml from %AppData%\Microsoft\VisualStudio\16?

‌

[Jamil Taylor]

I have %AppData%\Microsoft\VisualStudio but no 16 folder under that. I have a folder called 16.0_60e15ccb instead. This is after performing a full repair and reboot too. I attempted to rename the 16.0_60e15ccb folder to 16, but starting Visual Studio results in it creating a new 16.0_60e15ccb folder adding files to it.

Also, I have a lower .NET version than you do, because Windows Update has not been successful on my workstation starting in March 2020. It has been failing every monthly update since March. Microsoft is still working on Windows 10 update failures that have been plaguing many users.

This is my version:

‌

[Adam Driscoll]

That minor .NET version shouldn’t cause an issue with PoshTools. It targets 4.7.0. As for the ActivityLog.xml, can you check in your 16.0_60e15ccb  folder to see if there is an ActivityLog.xml?

If not, can you try running Visual Studio with the log switch? https://docs.microsoft.com/en-us/visualstudio/ide/reference/log-devenv-exe?view=vs-2019

‌

[Jamil Taylor]

I have an ActivityLog.Setup.xml file. I have attached it ZIP’d.

[Jamil Taylor]

I just executed devenv /log to generate an ActivityLog.xml file fresh. It is attached

‌

[Jamil Taylor]

I noticed errors in the AcitivityLog.xml related to an AutoSave extension I installed awhile back. I have uninstalled it to see if that helped. It did not. Attached is a second ActivityLog.xml without the AutoSave extension installed.

[Adam Driscoll]

I don’t see anything abnormal in those logs.

Can you let me know which Visual Studio workloads\features you have installed? You said this used to work and you upgraded and at some point, it stopped working. Is that correct?

[Jamil Taylor]

There were about two recent Visual Studio updates back-to-back. I noticed this issue only the day I opened this ticket.

I will attach screenshots of my currently installed options.

[Jamil Taylor]

The issue seems to be specific to PowerShell projects only in Visual Studio. I can create other projects without an issue (C++, C#, VB tried so far).

[Jamil Taylor]

There was another update for Visual Studio 2019 that I just installed today. I still do not know why I encountered the issue above, but I corrected just corrected it after installing this update:

‌

‌

I fixed this by moving the entire solution to a new location. I then used the latest Visual Studio to create a new PowerShell script solution with the same name as what I copied. This was created correctly as the screenshot above shows. Finally, I copied my single ps1 script file into this newly created solution.

This was a weird one, but this ticket may be closed now.

[Jamil Taylor]

I worked around this issue as I documented.