"The project does not know how to read the profile" in VS2022 - vb.net

I have a WinForms VB.NET application, which runs perfectly in VS2019. I need to create a menu bar (GUI editor not present in 2019).
When I run my application in VS2022, I get the error,
"This project does not know how to run the profile <projectname>"
(where <projectname> is the name of my project)
I've tried:
Repairing VS2022
Installing .NET Development Tools
Creating a new profile
How can I fix this?
EDIT: I have fixed this problem by reinstalling VS2022.

Related

Web Setup Project on Visual Studio 2022 - Unable to open project error

Good evening,
I have created a Web Form using Visual Studio 2022, and I have created a Web Setup project to help our customers to install the site on their server. I used the official extension that allows to create Setup projects in VS2022 (Microsoft Visual Studio Installer Projects); everything worked fine until some days ago, when VS2022 started to show the following error when trying to load the installer project:
"Unable to open project .../Setup.vdproj".
This is the error I am getting when I try to open/create a Web Setup project
I tried to open it also with VS2019, which I still had installed on my computer, but I got the same error.
At the beginning I thought it was an issue related to the project (maybe for some reasons some files had been corrrupted), so I tried to create a new Web Setup project, both on VS2022 and VS2019. Again, the same error appeared, on both versions of VS. At this point I tried to load the already existing project on another computer, and on the other computer everything worked perfectly, the project was loaded immediatly and no issues have been detected.
I tried to unistall and re-install the Microsoft Visual Studio Installer Projects extension, it didn't solve the problem; I tried to repair VS2022, it didn't solve the problem; I tried to completely uninstall VS2022 and VS2019 and re-install only VS2022, and guess what? It didn't solve the problem.
Does anyone know how to fix this problem, and what is the reason why I am unable to neither load nor create Web Setup projects?
Thank you,
Giacomo

Unable to start program "C:\Program Files\dotnet\dotnet.exe"

I've installed .NET Core 1.0.1 to use with VS 2015 Update 3 and I'm running as Administrator (on Windows 8.1 x64).
If I create any .NET Core project, be it console or web and attempt to run it Visual Studio then comes up with an error:
However I'm unable to ascertain why. VS builds it fine and I can run it from the CLI. I can also run Core fine through VSCode.
I've tried:
Deleting project.lock.json
Deleting the .vs folder
Repairing the .NET Core install
Repairing the VS 2015 install
Uninstalling and reinstalling .NET Core/SDK/Tooling & VS
Rebooting
And it still refuses to work!
I've raised this on the Core Tooling GitHub as well as can be seen here but as yet we're all a little stumped.
There are some people who have problems with Internet Explorer and Visual Studio.
Attempt to install Internet Explorer 9, or set a different default browser.
Other approaches:
Was the data path checked?
Perhaps there are wrong configured environment variables?
Are you sure that the configuration was reset by the installation?
Perhaps the path for the temporary data has been changed?
Try re-installing needed redistributables, as they are needed for executing .Net Core on Windows, as it is stated here :
https://learn.microsoft.com/en-us/dotnet/articles/core/windows-prerequisites
"NET Core requires the VC++ Redistributable when running on Windows"
If it don't work, add a try/catch at the highest level of your application and log all System.Exceptions that may occur. It may give you more informations about this error.
This error occurs if you change the name of the project. To work around this error You will have to delete all files under \object and \bin folders. After that rebuild application.
Restart the visual studio in administrator mode. This solved my problem.

Why did my VB.NET app solution break when I moved from VS2013 on Win8.1 to VS2015 on Win10?

My solution worked fine under Win8.1 using VS2013. Then I did a clean install of Win10. I ran the msi that was created back on XP some time ago, and it installed my VB app after asking for a .NET3 version. But then I started up VS2015 for the first time and loaded my VB app's solution. I get errors like this: BC30002 Type 'Excel.Workbook' is not defined.
I looked in Control Panel's Programs and Features and only see .NET 4.5 and 4.6 items (nothing for .NET 3).
My solution includes references to Microsoft.Office.Core and Microsoft.Office.Interop.Excel.
What do I need to do to fix this?
I solved this by going back to Control Panel/Programs and Features, selecting Microsoft Visual Studio Community 2015, clicking Uninstall or change a program. Then when the VS2015 installer opened, I selected Modify, then All (every installation option) and installed VS again. That solved the above problem.
But now I have a new error: BC30002 Type 'ExcelLateBind is not defined. How do I fix this?

System.NullReferenceException occurs in xaml designer

I've created a C++ UWP Windows 10 app using Visual Studio 2015. However, I'm not able to visualize any xaml in the designer because I'm always getting a System.NullReferenceException error. How can I fix this?
That's very odd but I solved following these steps:
Close any instance of Visual Studio
Open Visual studio and create a new C# UWP empty project (name it as you like, do not matter)
Run the "useless" created project then close it as Visual Studio
Open again your previous C++ UWP project
In my case everything started working!
Switching solution platform to x86 worked for me.
I'm experiencing exactly the same problem on my primary development machine but not on another. The reason is... I think... When I installed Visual Studio 2015 on the 2nd machine, the first time I created a Universal Solution (C#) I was shown a dialog asking me to OK "elevated permissions" (custom permissions) for the VS2015 installation folder. I OK'd it and Designer works on that machine in both Blend2015 and VS2015 (community edition)
On the other machine I was never shown the dialog asking me to confirm elevated permissions and Designer does NOT work on that machine (VS2015 Enterprise). This machine also has VS2013 update 5) on it.
I am thinking that I might have to completely wipe off VS2015 and try to clean the registry of all VS2105 references AND remove the VS2015 installation directories on C:\ AND when I reinstall, create a installation directory with a different name (if I can). What a PAIN though... I'm waiting to see if MS delivers a simple solution since I'm quite positive that this whole issue boils down to a bug (feature... grrr) having to do with custom permissions that can't be changed (or added) after installation.
Would be nice is MS would confirm this...
(please note, none of this involved c++... it was all C#)
Tom
this is the dialog I was shown on the machine where Designer works]1
Installing the Windows Software Development Kit (SDK) for Windows 10 solved the issue for me. It may ask to unistall the previous version of Windows 10 RTM SDK
https://developer.microsoft.com/en-us/windows/downloads/windows-10-sdk
This is fixed in Update 1 of Visual Studio 2015
https://www.microsoft.com/en-us/download/details.aspx?id=49989

The target "GetSolutionConfigurationContents" does not exist in the project

I have a Visual Studio 2013 solution that includes a Windows 8.1 WinJS app along with a MVC web application. When we build the solution locally in Visual Studio, it works fine, but building it on the build server fails with the following error:
"The target "GetSolutionConfigurationContents" does not exist in the project."
Could it be a software versioning issue between the local environment and what is installed on the build server? Any ideas would be helpful tracking this down.
Thanks.
The problem was in the package.appxmanifest file.
Under the Packaging tab, I had set the "Generate app bundle" option to "Always".
Setting it to "If needed" fixed the issue and the builds are now successful.
UPDATE:
The problem reoccurred when we targeted x64 builds only, so we had to keep this project setting:
<AppxBundlePlatforms>neutral</AppxBundlePlatforms>