I have seen several posts regarding this same issue. None have solved my problem. I have recently downloaded VS2015, I had been using VS2012. I open the same project in both, 2015 does not load the symbols and 2012 does. If I open it in 2012 and build it, then open it in 2015 it will load the symbols until I rebuild it. Anyone have any ideas?
One other thing that I thought interesting. I have a Winforms app that I did the exact same process with and the Winforms app works great
This was a bug with Telerik Data Access. They stopped supporting their visual designer. In order to fix the issue you have to get the updated Data Access from a NuGet package Telerik.DataAccess
The installation of the new data access should give you the Q2 2015 DLLs. It will also add a packages file to your project. You also need to open that and change the line
<UseXmlMapping Condition="'$(UseXmlMapping)'==''">false</UseXmlMapping>
to
<UseXmlMapping Condition="'$(UseXmlMapping)'==''">true</UseXmlMapping>
And also add the following code at the end of your property groups and before item groups
<PropertyGroup>
<UseXmlMapping>true</UseXmlMapping>
</PropertyGroup>
Related
I'm trying to use WinUI (3) for the first time.
I've followed the instructions at https://learn.microsoft.com/en-us/windows/apps/winui/winui3/#install-winui-3-preview-4 so installed vs 2019 preview (Professional Version 16.9.0 Preview 4.0) and installed the "WinUI 3 Project Templates via the Manage Extensions option.
Created a new solution, added project type "Blank app, Packaged (WinUI in desktop)" (C#) and this is the result:
I can start debugging and the window opens and can click the example button without any issues.
But when I open the xaml I have this issue:
And the intellisense doesn't give options like for example grid.
The imported namespaces in the code behind:
So all the basics of a new WINUI project on a clean vs 2019 preview installation. I've only installed Resharper and imported my settings from my regular vs 2019 installation (which I reset but to no avail).
When I choose for Microsoft.UI.Xaml.Window he changes the xaml to
And gives following errors:
When choosing ABI.Microsoft.UI.Xaml.Window the xaml changes in the same way as before but also gives exceptions on other properties like "The property 'HorizontalAlignment' was not found in type 'StackPanel'".
No idea if this matters but as I've never worked with WPF I don't have experience with xaml (always worked with winforms as frontend). So I also added a WPF project to this solution and this worked without any issue.
I can't find anything regarding this so please help me set my first steps in WINUI.
I've notificed it worked for a few seconds after reopening my solution. So prime suspect was Resharper. Disabled it, and problem is solved. Re-enabled it, updated to 2020.3.2 and it worked.
So lesson here: It's not because you just installed Resharper, that it also downloads the latest version ...
I have a Windows Forms Project that I have been working on for the last several months.
In this solution, I have about 10 custom user controls. A few days ago I was working on the common library that is shared across all of the forms in the application, and then when I went to open the form none of my controls were recognized.
I reverted my changes to the library and the issue persisted. Soon I got to the point where even opening the form crashed VS.
I can compile the solution fine, but I cannot use the visual editor.
None of my custom controls will show up anymore in the toolbox either. However, I can open them just fine.
After 2 days of looking online, I have tried the following, to no avail.
Dynamically reallocated my computer's memory (rebooted)
Close the solution and reopen it
Cleaned and rebuilt solution
Downloaded last release version from source control to a new directory and opened it.
Removing the controls from the project and readded them
Deleted the bin and obj folders
Deleted the .vs folder (stopped VS from crashing as soon as I opened the solution)
Followed this MSDN Article
Refreshed toolbox
Repaired the Visual Studio Installation
Uninstalled and Reinstalled Visual Studio
Copied the solution files from one directory to another
Reverted my project to an earlier commit from my source control solution
Removed all NuGet packages
Removed controls one by one
The only thing that has changed since the last time I was working on this project was that Visual Studio 2017 had recently installed a new update.
I am at a complete loss, I even resorted to going to page 4 on google.
UPDATE
This issue becomes intermittent when I run it on a fresh installation of VS within a Virtual Machine.
I had a separate DLL file that I was calling from my project for EMGU.CV. Once I removed that reference it worked fine. I created my own DLL wrapper for grabbing a Bitmap Image from the EMGU.CV library and the issue have since been resolved.
This makes sense as after I had deleted the NuGet packages, the DLL still remained, but once removed the designer resumed working.
I've been trying to load a project from a SourceGear Vault Client that has a plug-in for Visual Studio 2010. After selecting the solution file, the solution explorer populates with the associated projects but appends (unavailable) to the end of each project name.
The usual remedy is to reload each unavailable project but in doing so briefly reveals all files within each project but then VS quickly hides them and makes the project unavailable again.
So far, I have tried opening the code in VS2015, removing all related source control information from the .csproj and .sln files, and deleting the associated .suo file. Nothing has worked yet and I have exhausted all the known fixes.
Thanks for your help.
For clarity, I'm copying #PeterRitchie solution that worked for me, below.
You could try running Visual Studio in safe mode to see if a 3rd party plugin is to blame: devenv.exe /SafeMode – Peter Ritchie
I'm using Visual Studio 2015 with Xamarin 4.1.2.18 and CocosSharp PCL 1.6.2.
When I try to access the Properties of the Android project by clicking on the "Properties" item in the Solution Explorer, this error pops up:
If I also right click on the project itself and select "Properties", it displays "This item does not support previewing".
It should be opening up to this page:
I have (supposedly) the latest build and Update 3. I have reinstalled it 3 times now.
Normal uninstaller. Reinstalled... nothing, still broken.
Uninstall again with cmd: /uninstall /force, use registry cleaners, manually uninstall components from Control Panel, manually delete folders. Reinstall... still broken.
Finally, I searched around and found this: Microsoft Visual Studio Uninstaller. After I, again, performed all the steps of 2, I used this tool and it found 52 additional things to clean up. I thought I finally had fixed it. Nope. The properties thing is still broken.
I have tried running as administrator. Nope.
I have deleted the ComponentModelCache in local AppData. Nope.
I have deleted the .suo file. Nope.
I know it has nothing to do with the project files because we have all the files synced with Git and my friend can view the properties page fine on his computer.
Does anybody know how I can fix this?
Is there some way to gather more information on the error?
Any Visual Studio error logs?
Also, on an semi-unrelated note:
When I try to build the Android project, I get errors saying that the $(TargetFrameworkVersion) for my references/dependencies is v4.2 and the $(TargetFrameworkVersion) of my project is v2.3. I checked my TargetFrameworkVersion property in the .csproj file and it's v6.0!
So, something is seriously wrong with this build of Visual Studio or something.
I've been considering just installing Visual Studio on a VM just to be sure.
Solution:
In the Android SDK manager, I had Android 4.0 (API 14) downloaded. Once I switched to Android 4.2.2 (API 17) everything started working.
I just gotta say, the error that it gave me is the most convoluted error message that I've ever received in the history of my programming career.
I am getting this error when I try to open the solution file of my project. The solution is 2012 file (checked using notepad).
If I click on Ok, The solution opens up except for one csproject which does not load.
I get a migration report in UpgradeLog.htm file, with the following error for the project which failed to load. Could not figure out much from it.
Error:
The application which this project type is based on was not found.
Please try this link for further information:
http://go.microsoft.com/fwlink/?prd=12395&pver=11&sbp=ProjectTypeDeprecated&plcid=0x409&clcid=0x409&ar=MSDN&sar=ProjectCompatibility&o1=82b43b9b-a64c-4715-b499-d71e9ca2bd60
Does the upgrade report mean that it is a project from previous version of Visual studio? It does not open in Visual Studio 2010 either.
The error doesn't say that Visual Studio doesn't support .csproj files at all, it says it doesn't support a specific project type in that particular project file. This means this either isn't your project as you claim, or you are trying to build it on a different machine from the one used to create the project.
Visual Studio uses various elements in a .csproj file to determine its project type. See How do you tell the Visual Studio project type from an existing Visual Studio project and What is the significance of ProjectTypeGuids tag in the visual studio project file. It does this so it knows how to compile your project, what properties tabs to show, what context menu options should be available and so on.
Certain project types can cause this error. Usually they require some kind of SDK to be installed on the machine used to open or build the project.
You should search the web for the GUID mentioned in the error message you show (the value after o1=). You can also open the project file in a text editor and find the <ProjectTypeGuids> elements, which contains comma-separated project type GUIDs.
Then search the web for those GUIDs to find out which SDK or tool you need to install in order to be able to open or build the project.
If you paste the specific GUID from your error message in your favorite web search engine, you'll find Problem solved: Visual Studio / There is a missing project subtype. Subtype: '{82b43b9b-a64c-4715-b499-d71e9ca2bd60}' is unsupported by this installation., where it is mentioned you'll need to install the Visual Studio 2013 SDK. This means that in this case, your project is a Visual Studio 2013 extension.
This is what documentation is for. You should at least put a ReadMe.txt file in your project directory, explaining what the prerequisites for building a project are, especially when it won't open or build with Visual Studio out of the box.
I had this issue when I used Update 5 for VS 2013.
For me I had to click ok and read the next few steps, that popped up. I was initially clicking cancel.
On mine the project was missing Web Tools, so had to reinstall those and once done it was working.
Hope that helps someone.
This issue also appears when trying to import an ASP.Net project into Visual Studio 2015 Express for Desktop, and can be solved by simply downloading and installing Express 2015 for Web - or by using Visual Studio Community/Standard.
I am currently using VS 2017 v 15.7.4. This error came out of no where without any updates on my part. Usually when I have errors like this I just delete the .vs folder in my solution and that clears the problem. In this case that is what I did and the problem was fixed.
Close VS
Delete .vs folder
Load VS
Note: This was for a Xamarin based solution.
I solved this problem by downloading and installing (Microsoft Visual Studio Installer Projects). Close the project then install. After the installation, open your project then reload .csproj file
I had the same issue with VS 2017.
Eventually i solved it by just enable the SSIS in the following way:
1. In VS 2017 - Click on Extensions and Updates in the Tools menu.
Locate the Microsoft Integration Services Projects.
if you can't find it then you will have to install it first.
Click on the Enable button.
Close VS and start it again and SSIS projects are now available.
enter image description here
This (the error that states "Visual studio doesn't support specific csproj file") also occurs when the .vs folder is removed; however, closing and reopening Visual Studio will resolve the error.