I have this error when I try to open a WPF file in the designer even with a new project. Everythings else works perfectly. If I try to compile the project it works nicely as well.
I have tried to uninstall visual studio 2015 and reinstall but nothing changed. On another computer I don't have any problem to open my projects.
Edit : Found this link still not working but not sure about the "Ensure your x86 platform has the correct values to target x86" meaning
It may sound like a silly question, but is Internet Explorer 10 (or later) installed? See https://support.microsoft.com/en-us/kb/2906882. I had different problems to Microsoft's when I uninstalled IE.
Otherwise, you might try to repair your installation. Go to Control Panel -> Programs and Features -> Microsoft Visual Studio and choose Repair.
Related
Yes, i've tried devenv/install, with no help.
So, I don't have the Console C# Project option when creating the project,
as shown here
Currently i have installed windows basic pack - there's my 'about' screen.
I have just reinstalled Windows because i was getting the same exact problem on old system, and because VS2015 had interface bugs and crashed consequently, but it didn`t help(as well as reinstalling both VS 2015 and 2017 numerous times)
Hope that you can guess whats wrong with my PC.
Visual Studio 2017 setup allows you to very fine-grainedly install various "components" separately, or groups of components delivered as "workloads".
You're missing the workload named ".NET desktop development", which contains among others these project templates. So re-run setup and install that workload.
You have a link, Open Visual Studio Installer in a New Project window that will allow you modify your installed components
Since updating to the most recent version of Unity 5.4.0f3, whenever I doubleclick on a script, it launches both Visual Studio and Monodevelop, but I get an error saying that the this version of VS (Community 2015) is unable to open my project. Monodevelop displays it's own, somewhat less clear error message. Please see the screen shots below.
I can still manually open my script using Visual Studio's file menu, but the intellisense code completion no longer works. Anyone know how to fix this? I have Visual Studio's Tools for Unity installed.
I was having similar issues when doing a clean download of an existing Unity project onto a fresh install of Visual Studio Community 2019.
In the end the issue for me was that, although the correct version of VS Tools for Unity was installed, it was 'Disabled' by default in VS's Manage Extensions dialog (Extensions -> Manage Extensions). Just had to click 'Enable', restart Visual Studio, and all worked as expected again.
Turns out it was an issue with my existing install of Visual Studio Tools for Unity (VSTU).
I found a thread where users had experienced similar problems due to an unsupported version of VSTU running on Unity5.2 and beyond. Unity 5.2+ requires VSTU 2.1 or later for VS to work correctly with Unity, more information for anyone interested is available in the documentation here.
I had VSTU 2.3 installed, but removing and reinstalling VSTU resolved the issue, so there must have been a problem with my install. If anyone else has this or a similar issue you can download the latest installer for VSTU here. Thanks to all who chimed in your responses helped me look in the right place!
Please try following steps:
Delete old *.csproj and *.sln files on project's root folder
Check "Edit > Preferences > External Tools" and make sure you've selected "Visual Studio"
Re-open solution by "Assets > Open C# Project" menu
For me it was enough to right click the solution in Solution Explorer and run "Resolve errors".
I will complete what is said above. I experienced this issue today and it took me a while. In my case it was relative to a new install of the Unity Editor.
For some unknown reason the unity tool used on VS (intellisense) was uninstalled. I had to reinstall this : open Visual Studio Installer, select your project and reach the Gaming section where reside the tool for Unity.
The extension "Visual Studio 2019 Tools for Unity" seems no longer available for download via the extension manager. Luckily I recalled that I saw some game development features in the Visual Studio installer, so I picked that one:
It works for VS 2019 (16.11.11) and VS 2022 (17.2.0 Preview 1).
When I create a Xamarin.Forms application using Visual Studio Community 2015 Community on Windows 8.1 it shows me this error on load:
A problem was encountered creating the sub project 'App1.WinPhone'. This project requires a Visual Studio update to load. Right-click on the project and choose 'Download Update'
I've installed all updates available and trying on a newly installed Windows.
Note: I had this error in Forms.
How can I fix this error?
Note: There isn't a Download Update option in Solution Explorer.
Navigate to where you saved the project files that you created in Visual Studio. Default location is C:\Users\PSDan\Documents\Visual Studio 2015\Projects.
Open the project folder that you are experiencing problems with and navigate to C:\Users\PSDan\Documents\Visual Studio 2015\Projects\test\test\test.Windows folder. Inside this folder is a file called test.Windows.csproj.
Right click on that file and open with... using Visual Studio, by doing this it should detect the missing package and in my case automatically prompted to install the missing package.
I've been seeing similar errors for .Window or .WindowPhone and what I've observed is that it is due to missing SDK. Same might be the case with you.
Do you see App1.Droid appearing in the solution? (I guess NO)
Go to file explorer and locate App1.Droid.csproj (..\App1\App1.Droid\App1.Droid.csproj) and open this in a new instance. There it will pop up "Install Missing Feature" dialog and you can follow the steps to install missing components.
If your issue is the same as here:
Project required a Visual Studio update
then you may try and see if this solution works:
[Cause is] a mismatch of the target framework version and profile in the .csproj file. Despite the target framework being correct in the project Properties, they were not being correctly saved for whatever reason. Thus, when trying to install a utility library from nuGet, it left my project in the state you described.
The solution was to go by this site:
Framework Profiles in .NET
and find the correct combination, then manually edit the .csproj file to adjust <TargetFrameworkProfile> and <TargetFrameworkVersion>.
Installing Visual Studio Update 3 with selected features "Windows 8.1 and Windows Phone 8.0/8.1" and "Cross Platform Mobile Development" solved the problem for me.
Uninstall Xamarin completely, and reinstall it. That happened to me as well. I would uninstall Visual studio too. Install that first, then install Xamarin.
Edit: I know this sucks to do, but it was what the Xamarin team had me do to resolve it. As far as I know this is the official fix as of last week.
I have an ASP.NET MVC application that I'm working on in Visual Studio 2013 Premium. I have three projects that are underneath my solution. If I right-click on any of the folders that are immediately under my solution and choose add, the flyout from the context menu displays fine and Visual Studio continues to function normally.
If I right click on any (I've tried a few but not all) folder underneath one particular project in Visual Studio, it freezes for about fifteen minutes. The cpu and memory usage when this is going on seem pretty normal.
If I right click on any of the folders underneath the other two projects and choose Add I get the flyout to appear showing the types of things I can add to the folder and everything works just fine.
What I've tried:
Disabling all Visual Studio Extensions that can be disabled. This didn't fix it.
Starting an instance of Visual Studio in Safe mode, this does fix it.
Any idea what I can try next? I'd hate to have to manually uninstall all of the Visual Studio extensions that can't be disabled, but this seems like the logical next course of action.
As far as Extensions I have:
Application Insights Behaviors SDK (XAML)
Bing Dev. Assistant (Disabled, installed after problem started)
Find in Solution Explorer (Disabled)
Company-created Build Tools (Disabled)
Company-created Core Tools
Company-created Scaffolding Tools (Disabled)
Microsoft Advertising pubCenter
Microsoft Advertising SDK for Win 8.1
Microsoft Advertising SDK for WP 8.1 XAML
Microsoft ASP.NET and Web Tools
Microsoft Visual Studio ASP.NET MVC 5 Scaffolding
Nuget Package Manager
Productivity Power Tools (Disabled)
Release Management for VS 2013
TFS Server Power Tools for VS 2013
TFS Sidekicks (Disabled)
TFS Process Template Editor
TFS Team Collab.
TFS Work Item Type Designer
Unit Test Generator (Disabled)
Visual F#
VS Extensions for Windows Library for JavaScript
WP 8.1 SDK Integration
Workflow Manager Activities
I don't need the WP 8.1 stuff here at work, but dabble with it at home. Since I'm logged into my MSDN account in Visual Studio at both places, would it uninstall it from my home PC if I uninstall it at work?
I'm doing a little further exploration. On the project that has the problem, when I try to do an add to a folder, I'm seeing Nuget.exe get fired off every six seconds over and over again. Where would I look to see where this is set up? I assume in the .csproj file.
Thanks
I disabled and uninstalled a bunch of Visual Studio extensions, which didn't help. I then cleared my nuget cache and that solved my problem.
I had exactly the same problem apparently, in my case it was a reference problem try deleting them one by one until the it starts responding in real time, i suggest starting with 3rd party dlls.
hey there. So, we have a VS2010 project and the VisualSVN server on one machine. We added a new machine with the client visual svn and the projected loaded in. except for the WCF service. i'm getting a...
" error : the project file c:/..../wcfProject.csproj cannot be opened.
The project type is not supported by this installation."
i've checked the directory, the files and file structure are there and the same as the main development machine. any tips/solutions?
thanks
David K.
I had a similar problem with some WCF solution which I downloaded from a blog.
The solutions of running deveng with the switches did not resolve my issues. After some more searching it turned out that the following clue in the answer of Ralph Willgoss lead to the solution of my problem:
I resolved it by installing the Visual Web Developer.
I also had to (manually) install the Web Platform Installer to (automatically) download the last requirements for the project to properly load.
I had a similar problem when trying to create a new project of the following types:
WCF Service Application
WCF Work Flow Service Application
Syndication Service Library
I was using Windows 7 Ultimate 64bit, with no other versions of Visual Studio installed.
I also had tried many other options, such as:
devenv /resetsettings
devenv /resetskippkgs
ensuring I had C++ option of VS2010 installed
VS2010 Service Pack 1
I resolved it by installing the Visual Web Developer.
There are a few things this could be so I can't give you one specific answer. However, here are a few things to try on your machine that is throwing the error:
First, verify which version of Visual Studio is set as the default for opening csproj files. It could be that you installed SQL or something else that uses an older version of Visual Studio. Sometimes that can give an error. Even if the default is the Visual Studio version selector I've seen it throw an error. Open up the correct version of Visual Studio (through the Programs menu) and then inside Visual Studio try to open the package. If that works, you know the issue is with which version is opening the file.
If that doesn't work, you could try resetting the Visual Studio settings. From the run menu type devenv /setup This should reset the Visual Studio environment and hopefully it will fix the issue. If this does not work, try running devenv /ResetSkipPkgs from the Run menu. This will try to load any packages that Visual Studio previously skipped.
If these steps don't work, let us know. Give us any further error messages that come up after attempting these steps.