Upgrading WebMatrix to V3 - upgrade

Just upgraded WebMatrix this morning to WebMatrix V3, but now when I open the solution in Visual Studio, it displays the error "the selected file is not a valid solution file".
Everything was working fine before the upgrade!
Has anyone else seen this?

Related

Can not change .Net Framework to 6.0 in Visual Studio 2022

Hey so I have Visual Studio 2022, I installed the .NET Framework 6.0.1 SDK manually from the microsoft website, If I check the Visual Studio Installer the .NET 6.0 Runtime is checked (means it is installed).
But I am neither able to retarget my existing Projects to 6.0, neither create a new Project for 6.0. The .NET Framework 6.0 simply doesn't appear in the dropdown selection.
I found another thread which had the same issue but nothing worked for me.
I've read that you can change the Targetframework editing the .csproj file with Notepad, I tried that but at start it told me I don't have the framework installed and either need to downgrade to 4.8 or install 6.0.1.
I've restarted and reinstalled Visual Studio several times now, same with my Computer.
What the heck is wrong here?

correct way to install latest VS Code + .Net SDK + Omnisharp ext, and avoid error: "Attempted to update project that is not loaded"

I have a clean install of Ubuntu 20.04 LTS. I want to install Visual Studio Code, .NET SDK 5.0, and what seems to be the best suggested C# extension, this, the OmniSharp one.
I first tried to install with the Ubuntu Software app. In Visual Studio Code I installed the suggested OmniSharp extension. When trying to build a project, I got the mentioned error.
I tried installing using the terminal with this tutorial which seems good and straighforward - same error, when at the console app example stage after running dotnet new console.
This SO question has three proper suggestions, though I would like to use the latest SDK, and I do not have Mono installed, also I want to use Visual Studio Code, as far as I know, that is a newer approach than Mono.
The omnisharp.path": "latest solution does not work.
i faced the same problem and in the end i find the solution here
https://medium.com/#stnlyli/visual-studio-code-failed-to-load-c-extension-on-ubuntu-5cc56dd1cdb7
prefix:
file->preferences->settings-> search for "Omnisharp: Use Global Mono" and make it never

Visual Studio 2019 regularly loses the ability to open Unity projects (unsupported)

Nothing was changed when all of a sudden Visual Studio 2019 suddenly couldn't open Unity 2019.2.4f1 projects.
Once it happened several months ago. That time it was cured by itself when I downloaded a clean Unity project from my repository. Just yesterday it happened again. I spend the whole day surfing forums and trying to fix but nothing helped until I decided to completely reinstall Visual Studio. Today everything was fine until suddenly it started again.
I didn't change anything, just was working with code.
External tools settings are set as they were.
Any ideas why it could happen and how to fix it without reinstalling VS?
Is it possible to somehow find out what exactly the VS can't understand in the project files?
In VS2019 go to Extensions -> Manage Extensions and check that "Visual Studio 2019 Tools for Unity" extension is installed, and enabled.

Unity 2018.3.X problem with autocompletion

Using Unity 2018.3.X just installed does not let you use Visual Studio Code nor MonoDevelop to code right.
Precompile is disabled
No debugger
No autocompletion
Errors everywhere
I solved it myself with some hours dedicated to this thing.
I was installing Visual Code as usual on a new computer but when trying to edit code the autocompletion did not work, also tons of errors popped.
When I installed I added the normal plugins for Unity in Visual Code
C#
Unity debugger
When reloading Visual Code, the Omnisharp log said that the compiler did not find the .NET Framework 4.5 and anything works within your C# scripts.
When looking into it I found this folder in Windows.
(If someone knows where it is in iOS share it please)
C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework
That folder showed folders with the versions of the frameworks installed.
In my case, those were 3.0 and 4.5.2.
The problem is that for some reason it does not detects the version 4.5.2 as 4.5 so to fix it normally you should install version 4.5, the problem is that you cant get it anymore.
To solve this, look at the Omnisharp log and change the folder name to the one your Omnisharp says, in my case I changed the name of 4.5.2 to 4.5 and my problem was solved.
I have seen more cases where the version the Omnisharp wants is different, just download the 4.X version you want from this link and change the folder name if you need.
https://dotnet.microsoft.com/download/visual-studio-sdks
Keep you .NET Core updated too to avoid more problems.

Hololens device build fails to not finding Assembly-CSharp-firstpass.dll

I'm trying to build Unity application for Hololens device on Visual Studio 2017 and I'm getting the following errors:
Metadata file '...\GeneratedProjects\UWP\Assembly-CSharp-firstpass\bin\x86\Release\Assembly-CSharp-firstpass.dll' could not be found
Metadata file '...\GeneratedProjects\UWP\Assembly-CSharp\bin\x86\Release\Assembly-CSharp.dll'
I'm aware of the similar question here but uninstalling and installing the latest versions of both Unity and VS did not help. Neither did starting a completely new project. I'm using now the latest versions of Unity (2017.1.0f3) and Visual Studio 2017 (15.3.0).
I've tried uninstalling both applications. Everything was working fine yesterday but then I downloaded additional components to Visual Studio (ASP.NET) and the Hololens build stopped working. Any idea how I could fix the issue?
I can see the Assembly-CSharp-firstpass.dll in Unprocessed folder under the path it's searching for it and even tried to copy it to the correct path but it did not help. I have also tried to build the project without ticking the Unity C# Projects but I get a different error then.
Update
I found this post on Unity forums and I think it's the same issue I have: https://forum.unity3d.com/threads/net-scripting-backend-and-visual-studio-2017-3-incompatibility.487833/
A workaround for this issue is to manually modifiying The "UAP,Version=v10.0.xxx" to "UAP,Version=v10.0" In the project.lock.json files of the GeneratedProjects.
Other solutions to this problem include a downgrade to Visual Studio 2015, or using the patch that the link you provided has.