For some reason when I try to open a solution the project says "load failed." When I try reload the project I get the following error:
Creation of the virtual directory //localhost:xxxx/ failed with the error: Unable to access the IIS metabase. You do not have sufficient privilege to access IIS web sites on your machine.
I've run into this error on at least three different occasions and each time I fixed the problem by reinstalling Visual Studio and .NET Framework 4.5.1. However, reinstalling is not working this time. Here are the things I've already tried:
Reinstalled Visual Studio and .NET Framework 4.5.1
Ran Visual Studio as Administrator
Turn IIS features off and on
Unfortunately, none of these things have worked and I really need to resolve this problem
Any suggestions are welcome!
Thank you.
Right click on the project and select 'Reload Project'
Try this trick, Maybe it will work for you.
Go to My document Folder. It's like C:/Users/Username/My Documents
Here is a folder called IISExpress Delete this folder after uninstall IIS express. When it's goes deleted then install the IIS express again and it will surely work.
I had that problem after installing Visual Studio 2013 update 4. I occurs that I have to uninstall IIS express for sure, but also it was needed to change in csproj file one of the line:
<UseIISExpress>true</UseIISExpress>
into
<UseIISExpress>false</UseIISExpress>
and that helped a lot in my case.
After this I've just installed IIS express once again.
I have the same problem. Try to run Visual Studio like administrator. This fix problem in my case.
In my case, I have to reopen the project as an administrator and then configure it to use IISExpress instead of IIS. Then close and reopen as normal user.
I also have to reset my VS environment.
Hope this help.
Go to Tools->extensions and updates in VS
and check installed plugins and uninstall all
That works
thanks for the suggestions everyone.
It turns out this problem was easily solved; all I had to do was go back to work. The computer I'm working on is a work computer, and the IISExpress folder (usually located in C:/Users/Username/My Documents) was stored on a network drive. All I had to do was connect to the network drive and everything now works.
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 yesterday I am getting a weird error when I try to create a new .Net Core Web project. The error I am getting:
It seems this is only the case for .Net Core projects (Console application .Net core also doesn't work but a regular .Net web project does work...
I looked online but it seems there is no documentation about this error whatsoever.
Some things I tried already:
Repairing Visual Studio 2017
Checked the log by running Devenv /log (Warning :
Performance warning: String load failed. Pkg:{D15F5C78-D04F-45FD-AEA2-D7982D8FA429} (VisualBasicProjectSystemPackage) LANG:0409 ID:2
)
UPDATE
I think I know what caused the problem. Prior to the problem I deleted my old user account (migrated the account so everything copied to a new user account), my guess is that Visual Studio also installs templates on my user account and with the removal of my old user account I also deleted some templates. The question however is, why is the .Net Core template the only one not working then?
Anyone know what causes this problem and how to fix it?
Removing Visual Studio and reinstalling it seems to fix the issue. Before reinstalling, make screenshots of all your settings and (manually) downloaded components.
Same problem here, I tried to repair (multiple times) the installation but the problem wasn't solved.
In my case I didn't change user accounts.. I just uninstalled VS 2013 Ultimate, Unistalled VS 2015 (with some difficulty) and then installed VS2017..
Recently, Visual Studio 2013 started hanging again when trying to debug/trace an ASP.NET web site. The site was created with WebMatrix 3 but I don't think that is relevant.
VS2013 opens the web site Solution. It takes a really long time to load up. Once it does load up and I run the project, it hits my first breakpoint and then the IDE Window quickly shows "(not responding)" in the title bar and the IDE is now hung.
This happened to me a long time ago and the root cause was needing to set the "use 64-bit IIS" option as indicated by this SO post:
Visual Studio 2013 crashes and restarts every time I run my test solution
But I triple-checked and I do have the 64-bit option checked. What can I do to fix this?
What worked for me was resetting visual studio. I got the suggestion from http://www.vosseburcht.com/?p=69
See this blog in the issue. It basiclly says to make sure "show all files" is selected in the solution and check for any folders that don't belong that are not part of your project/solution.
The problem resurfaced again a few days later and I finally figured out the problem with my uncooperative debugger. I have a folder containing approximately 20,000 images that are not included in the Visual Studio web project but are sitting in a directory in the web site. I had turned on "Show All Files" in Solution Explorer to add some script files into the project. When "Show All Files" is off, F5 (Start Debugging) works like champ. When "Show All Files" is on, Visual Studio becomes unresponsive. In reality it is not "frozen" but simply taking a very long time to process those 20,000 image files.
For me, it was a folder created called backup, which was a backup of the site (created by VS). I deleted the folder in question and the site loaded for debugging.
It might be caused be some extensions in Visual Studio, I was facing a similar problem when degbugging asp.net websites. Try running VS in Safemode: devenv.exe /Safemode. In my case it was caused by Multilingual App Toolkit extension, after uninstalling it, debugging ASP.NET websites works once again.
In my case, I was able to solve it by running it as an Administrator!
Don't know why, couple of days back it was working fine, suddenly it started to freeze when trying to debub web app!
Hope it helps someone!
BTW: I am running VS2013 Ultimate, with Update 4
In my case it's the IntelliTrace that causes problem. I need to disable it https://msdn.microsoft.com/en-us/library/dd264948(v=vs.100).aspx
I have the same situation and "solved it" in a very particular way: Rebuild the solution and run it without debugging (Control + F5), then go back and debug it the normal way.
I was having a similar issue, and I found the following error in Windows Application Event Log that corresponded to the problem:
Application: PowerShellToolsProcessHost.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.Serialization.InvalidDataContractException
...
So I removed PowerShell Tools for Visual Studio extension, and the issue went away. I am using Visual Studio Ultimate 2013 Update 5.
I had this problem while writing an Excel add-in.
Not being a web app I was pretty sure that checking the 64 bit IIS Express option would make no difference, but it did!
I have no idea why, but it runs in debug ok now :)
I had to install Windows Management Framework 4.0
My solution was to remove all the .bak backup files generated by DevExpress ProjectConverter when I had upgraded to the new DevExpress version.
First of all I would like to say that I already tried all the solutions I could find on the internet, including Unable to Activate Windows Store App
I recently upgraded my Windows 7 machine to Windows 8.1 to be capable of developing Windows Store apps using Visual Studio 2013. When I open a blank project (Windows Store -> Blank App) and run it I get this error:
Unable to activate Windows Store app 'Package Name'. The App1.exe
process started, but the activation request failed with error 'The app
didn't start'.
See help for advice on troubleshooting the issue.
I already tried:
Reinstalling Windows (Clean install)
Reinstalling Visual Studio 2013
Installing Visual Studio 2012 (same error)
Deleting "bin" and "obj" folder
Cleaning the solution
Uninstalling the app from start menu
Creating a new project
Acquiring the license multiple times (the license is valid)
Making sure that app.config doesn't exist
Investigating the Windows Event Log which says
Activation of the app 'Package Name' for the Windows.Launch contract failed with error: The app didn't start..
but found nothing useful
Adding a new Windows user
Run everything as administrator
and at last, changing the desktop background :)
None of this did bring a solution. Does anyone have an idea what else could be the reason for this error?
Thank you.
I found a solution. The problem was that the drive I was working on was encrypted (TrueCrypt). Moving the output folder to an unencrypted drive solved the problem.
If switching from x86 to x64, make sure your Project Properties Platform Target and Configuration Platform are BOTH set to X64.Hint you need to change to x64 debugging in the Build menu/Configuration Manager dialog to get the Configuration Platform in Project Properties to update.
This caused the activation error problem to be resolved for me
HTH
Robert
I had the same Error and tried after loading the SQLite Package for WP 8.1 some things above:
not working:
Clean and Rebuild
Restart Computer/Phone
what did the deal (for me)
I put Platform Target under Properties -> Build to ARM instead of x86
Hopefully this might help somebody else facing this ridiculously informative Errormessage.
I had the same problem with Visual Studio Community 2015 while trying to debug an Blank App (Universal Windows) using Visual C#.
Visual Studio was installed on Disk C:(SSD), and Project files were placed on D:(HDD). I´ve created a Folder on C: Drive and placed my test project there.
After that Error messages gone.
If you are receiving this error and are developing for Microsoft Hololens:
You are trying to build to a device that is asleep. To wake your device, tap on the button on the back (on/off button).
Good luck!
I've tried all the solutions found on the net and none applied to my case, not even this one.
The only way I could make it work was changing the Package Name in the appxmanifest.
This made me think there must be some leftovers somewhere around with the old package name, that are either corrupted or inaccessible because of some permissions issues.
It might be just a coincidence but the problem appeared twice after I tried using the app verifier (appverif.exe)
Now I reassociated my app to a store app package and things seem to continue working...
In my solution, I have a non-UWP project (Multiplatform development) that builds with a different Solution Platform.
I was attempting to run the UWP project in Debug, but as the wrong Solution Platform.
Edit:
I also get this when I build my project for Any-CPU, instead of x64.
Ensure that ALL APPLICATION PACKAGES has "read" permissions on C:\Windows.
My organization's group policy likes to strip all permissions from C:\Windows, including the ALL APPLICATION PACKAGES group . By adding it back in and setting Read & execute, List folder contents, and Read, I'm able to run the app from Visual Studio without any problems.
See What to do if your Windows 8 Modern App fails to start for more tips, including this one.
I had the same problem in Visual Studio 2015 Update 3, Windows 10 Build 10586.494.
The error came up when trying to start any UWP app that I compiled without .NET Native Toolchain. With Native Toolchain enabled, the apps would start.
Installing a new (blank) app manually fixed the error for me:
Start VS 2015
File > New > Project.
Blank App (Universal Windows) Visual C#. OK.
Make sure to be in Debug config
Right click on Project > Store > Create App Packages
No. Next.
Select Debug for all architectures.
Create
When packaging is finished, open Explorer to the project path / AppPackages / [...]_Debug_Test
Right-click on Add-AppDevPackage.ps1 > Run with PowerShell
Follow the instructions
Start the installed app from Start Menu
I had the same problem a couple of weeks ago. A simple restart helped me out.
Also tried this one?: http://irisclasson.com/2012/11/04/problem-unable-to-activate-windows-store-app-the-app1-exe-process-started-but-the-activation-request-failed-with-error-the-app-didnt-start/
Hope its usefull to you
I managed to fix the same problem by rebuilding the solution. (In Vis Studio 2012)
I have tried many solutions and nothing worked. At the end what worked for me was to change the startup project to windows phone 8.1 and after it runs OK I changed it back to windows 8.1 and it runs OK. It works for me as I am making a universal app. Hope it helps anyone else.
I had the same issue with a Windows Store App after moving some files around. I ended up opening an older file (as Admin) to see if it would run and found that it did. I then returned to the file that would not and it ran also. I believe opening the older file (as Admin) reset the paths for development and the permissions. Hope this helps.
Same problem - moved my project from the TrueCrypt Partition and all was fine.
I had a similar issue, solved by choosing a new publisher certificate. And of course restarting Windows
I had same issue. Selecting proper Platform solved my problem. i.e. My application was selected to run under x86 platform, while my OS & SDK supports x64. Selecting x64 solved my problem.
I had the same problem on a UWP app when creating a package for Testing, but not when runing directly from Visual Studio 2017.
The solution was to select only the architecture that I am using to Debug the App, Instead of all options (x86, x64, ARM).
Here is the option choosed on Visual Studio
There are can be a couple of things that might be causing this problem.
Here are the trouble shooting steps that helped me out:
Step 1 : Check to see if running visual studio in the elevated mode (Run as an Administrator) helped solve the problem. (Sometimes, your folder permissions might get mangled due to various softwares that you might have install)
Step 2 : Delete all the bin and obj folders in your project and rebuild the projects in your solution manually.
Step 3 : Do a quick check of your System Type (x64 or x86 etc) and see if your project is targeted for the same.
Here is how to do know your system type: Win + R > cmd > systeminfo
If it says x64, then make sure to select the Solution Platforms (In visual studios top action bar) as x64 or so forth depending on your architecture.
Thats all I did to solve my problem.
I had unticked an option while trying to get debugging working prior to this error, the fix for me was to re-check the "Compile with .NET Native tool chain"
A rather niche situation and solution...
I was remote debugging a UWP app for a while successfully. After some reworking, I ran into this issue. In the main app project I had set the windows version compatibility accordingly (I am running the app on a Windows 10 IoT Enterprise 2019 device) but had forgotten to match those windows target and minimum versions for the Library Project that was in my solution.
After cleaning and re-deploying the solution (first uninstalling the app from the remote device), the problem went away.
My Visual Studio seems to be freezing/lagging when I open a existing project. I have added NHibernate framework into my code and it seems to lag my computer (at least that's what I think). When I open other projects, I do not lag or freeze at all. The freeze is about 3- seconds to a minute, then it will open my project and it will just act very slowly, it might take 20+ seconds just to switch classes an 20+ more seconds just to type a single character into visual studios.
I was wondering if anyone has had this problem before. If so how did you fix it?
I can't really work on my code until this is fixed. Oh also, when is save the code, it freezes for a good minute or two also.
You can see exactly what VS is doing at any given moment, if you attach a debugger to the devenv.exe process and hit Break when it hangs. Then load the symbols from Microsoft Symbols server and show the call stack for the VS main thread.
I wrote a very detailed article about how to debug crashes and hangs here:
http://blogs.msdn.com/kirillosenkov/archive/2008/12/07/how-to-debug-crashes-and-hangs.aspx
From the call stack it should be obvious what is causing the delay.
For me, removing the suo file (from the v14 sub directory) solved the problem...
Had the same problem. Closed Visual Studio 2010, opened again Running as Administrator, went to Extension Manager, uninstalled Nuget Package Manager, restarted Visual Studio 2010 running as regular user, opened problem solution, solution opened fine.
Nuget Package Manager seems to be the cause. My problem solution is using EF 4.3 Code First which interacts heavily with the Package Manager Console, but that may just be a coincidence.
As answer by Visual Studio 2015 Freezing White Loading Solution delete the .vs hidden directory solved the issue for me.
I am using Visual Studio 2017 Community Edition.
I had a hunch that something had been corrupted with one of my NuGet packages, and completely deleted the \packages subfolder and its contents. When I reopened the solution, all projects loaded successfully without hanging.
From there, I restored the previously deleted packages from the NuGet Package Manager Console and I was back up and running.
What, if any Add-ins do you have installed?
Edit:
One suggestion I would have then is to systematically disable each of your add-ins and see if performance changes and if it does research the culprit and see if there any updates available.
Uninstall any MS Enterprise Framework addin's you may have.
Delete the VS temp directory (and the Windows one).
Do you use TFS? Perhaps the server is a bit sleepy, that will make it freeze for a few minutes, but is ok afterwards.
For me, a chkdsk /F /R (which will prompt you to restart) and about 30 minutes of company time fixed this issue.
I think a few improperly closed instances of Visual Studio may have attributed to the issue.
I had same problem. Delete following folder.
C:\Users\UserName\AppData\Local\Microsoft\VisualStudio
My local files somehow became corrupted for one project, fortunately I didn't have any pending changes so rather than run chkdsk I just deleted the folder and checked out the solution from source control again.