I've installed Visual Studio 2013 a few weeks ago. I played around with making some C# applications. But today when I tried to open up Visual Studio, I got the following error message: The operation could not be completed. No such interface supported.
I have tried to run it as administrator, same problem. This is the only version that's installed on my computer. I have Win 7 64 bit. Could anyone help please?
I had this problem too on VS12. There are probably more solutions but the simplest one is to clear VisualStudio's temporary data. You can find that in C:\Users\_name\AppData\Local\Microsoft\VisualStudio\_version. Just delete entire version folder and it will be regenerated when you open VS.
Try Repairing VS2013 and see if that helps.
I had the same problem and none of the other solutions fixed it for me. I needed to repair .Net 4.5.2 before it would work again.
I had this issue after a hard reboot (pulled plug). I repaired VS - did not help.
I also noticed that some other programs also had the same problem.
I repaired .net Framework 4.5.2 - after that it seems fine...
Related
I am trying to develop a UWP app for Windows desktop machines. Everything has been going well, but within the last few days I've lost the ability to build a release version (building a debug version still works fine).
I get the following error messages:
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(2810,5): error APPX0002: Task 'ValidateAppxManifest' failed. Unspecified error
1>C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(2810,5): error APPX0002: [My App] violates pattern constraint of '\bms-resource:.{1,256}'.
I've tried a number of "fixes" that worked for people over the last few years. Some people report the problem fixed itself in the latest version of Visual Studio. Unfortunately, the versions they mention are older than the version I'm using, which is
Microsoft Visual Studio Community 2019
Version 16.6.3
Many fixes from the net are similar to the ones below, from the URL
https://social.msdn.microsoft.com/Forums/en-US/4cc2cbfb-fa0d-4f12-a0a1-9072d78e26d6/vs2019-error-task-validateappxmanifest-failed-unspecified-error-again-and-again?forum=msbuild
One fix was:
Clear nuget packages,
Clean solution
Close VS
Delete bin & obj folders of the main (startup) project
Open VS - solution
Restore solution nuget packages
Rebuild 'n go
Another fix was:
uninstalling vs & sdks,
removing every nuget folder,
clean the registry and restart the system,
the last step once more,
reinstall vs.
I have tried all of these (several times) except for "clean registry." I'm not sure what part of the registry we're talking about.
So, has anyone overcome this problem in a different way, or know what the registry idea is?
Oh, some other data is
Maybe my machine is too old (about 6 years old). I’m speculating that even if my machine seems to have the latest version of Windows an Visual Studio, maybe it doesn’t have exactly the latest code.
Things went bad while I was adding two new features. The first was to ask the user for a rating, via _storeContext.RequestRateAndReviewAppAsync(); The second was allowing the user to share some data via DataTransferManager.ShowShareUI();
I was thinking maybe these APIs might require some declarations in the manifest that I don't have, but I don't see from the documentation that they do.
Any ideas would be greatly appreciated. I’m out of ideas at the moment.
Dan
Here is the answer, for me. I’m not confident that this as the answer for all cases, but all is good now.
You may remember that I said I had the latest version of Windows, and I did. However, when I checked with Windows Update last night, it confirmed I was “up to date” but it offered me a “Feature update” to Windows 10, version 2004. I decided to go for it.
The update took hours to complete, and this morning it was still only 94% complete when Nico Zhu suggested to try using Visual Studio 2017. I figured I’d install VS 2017 after the update, but when it was finally complete, I decided to try VS 2019 one more time with my fresh new version of Windows. Amazingly, it worked the first time.
I should mention that my new procedure for making an app package now includes
close VS 2019
delete the project’s obj folder
delete the project’s bin folder (I used to just delete the obj folder, but after seeing others suggestions I’ve added this step)
launch VS 2019
create the App Package
I wanted to do another build/package so I fixed a couple of cosmetic bugs and tried again. On the second try I fell back into my old pattern and I did NOT delete the bin folder. Immediately VS 2019 popped up with an error message something like “Cannot complete build. Fix problem with your app manifest.” Rather than pouring over the manifest file as I’ve been doing for the last couple of days, I deleted both the obj and bin folders and tried again. The build/package process then worked perfectly.
So, I want to say that the app manifest file was not the culprit (in this case anyway) and I’m now a fan of deleting both the obj and bin folders, and having Win 10 version 2014, before attempting a release build with VS 2019.
Dan
Since I installed Visual Studio 2015 Update 2 I can't create any app packages for the Windows Store anymore. The apps are linked to the store and compile without any mistakes, however every time I try to create a store package it fails because "C:\Program Files (x86)\MSBuild\Microsoft.NetNative\x86\ilc\Tools\nutc_driver.exe" returns exit code -1073740791. I've already tried both repairing and reinstalling Visual Studio, I've also reinstalled every single Windows 10 SDK package (10240 as well as 10586.212), but none of these attempts fixed my problem. It doesn't even work with a completely new, empty project.
The weird thing is that I can create packages not linked to the store without any problems, the problem only occurs when I try to create the actual store packages.
I'm running the latest stable release of Windows 10 Pro x64 (10586.212) and never tried the Preview SDK or other sorts of pre-release things with these packages. Also, they're all located on my main partition (C:).
The next thing I'd do is to reinstall Windows 10, however that can't be the only option to fix this issue (supposing it would do). So is there anybody who knows what exactly causes Visual Studio to fail at this point?
Thanks!
Edit: The error is also specified as "ILT0005".
So I've figured out what had caused Visual Studio to fail. Believe it or not - the display language of Visual Studio was the problem. I changed the language from German into English and everything worked just fine afterwards.
However, thanks anyway. And maybe I can reach and help some other people who are struggling with the same bug.
I have some Solutions, which are very old and everybody who worked on them is gone.
So far so funny, my first problem: Which VS Version to use.
In the csproj-Files I found this entry (Since you cant see it, its a PropertyGroup followed by VisiualStudioVersion == 10):
10.0
Wouldnt the 10.0 mean, in fact it is Visual Studio 2010? According f.e. to the Installation-Path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE, which opens the VS 2010?
Another Property I can't understand is the TargetFrameWorkVersion:
v4.5
This Project was not changed since early 2012, and according to http://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_4.5 4.5 was first released at 01.07.2012.
Am I doing something horribly wrong? I keep getting the following Error:
The project type is not supported by this installation.
I have definitely no MVC-Project (which seems to cause troubles and shoot this error), but it's a SharePoint project, could that be the problem?
Thanks in advance
Matthias
I've accidentally broken visual studio:
I have two different versions: VS express and ultimate.
I installed an add-on a month ago, and were working for some project.
Now I working for same project almost two weeks, and it's now acting strange.
After some writing I tried to debug it, it was successfully built, but after launch VS crashed.
Here is a list of things I've tried:
Safe mode - works
Reseting to default - not work
Reinstalling - not work
Try in express - works
Google doesn't help me. I'm writing an c# console app and I don't have any idea what the problem is.
If anyone knows where is the problem or has experienced something similar, please help me (:
P.S. Sorry my bad english
If safe mode works then I'd say its probably the addon's fault... I'd remove the addon.
Problem was with achivments extensions. When the add tryes to generate achivement by going to one of the lines, it makes the addon crushes all VS. and i learned that addons not deleting by deliting the VS studio. Thanks for all, who tryed to help (:
Good morning, i'm trying to import the DLL of the Firebird.Client to use with the VS2008 but everytime i add the reference to the dll i get the message:
Warning 1 The referenced component 'FirebirdSql.Data.FirebirdClient' could not be found.
I've tryied to add the reference path to the project, but it doesn't solve the problem.
Is there anything else i can do?
Thanks in advance
Link to where i've download cliente:
http://sourceforge.net/projects/firebird/files/firebird-net-provider/2.6.5/NETProvider-2.6.5.zip/download
I ran into this same problem when I received a new Windows 7 workstation -- it seems to affect Visual Studio 2008 on Windows 7. Everything worked fine in VS2008 on my old Windows XP machine. Unfortunately the ultimate solution for me was to migrate everything to Visual Studio 2010.
Found the problem, to use Firebird with VS2008 i had to use a older version of the Firebird client, that worked just fine. Awsome? Not that much, but if you have no choice like me you can try it too, just use:
Version 2.5.2 for .NET 3.5/2.0 with Entity Framework support