I am trying to overcome this error in Designer Mode of any ASPX page,
for example, CS203100 out-of-box:
I am not sure when the error began, and not sure if this could be related to any recent Windows Update. I am working with AcumaticaERP version 18.1.102.0048 under VS2015 on Windows 10 Enterprise. The error occurs under TargetFramework 4.5.2 and also after updating to 4.7.1. Any help please would be great, thanks!
We ran into the same issue with a colleague and it turns out that Visual Studio was not running with administrative privileges. It looks like PXLicenseObserver tries to create a log file on initialization and it fails when Visual Studio is not running in Administrator mode.
Related
I am trying to open my Main.Storyboard in visual studio for mac, and i am getting 'System.AggregateException: One or more errors occurred'. Note that i happened after upgrading Visual Studio to 7.3, the latest up to now and X Code to 9.2, also the latest available to now.
I am getting the following error screen
As I commented above, I have been having exactly the same problem for a week or two.
Originally, Visual Studio was installed under a non-admin user account (using an administrator password where prompted).
I eventually did a complete uninstall using the script mentioned here, and then reinstalled from scratch using an administrator account. This seems to have fixed the problem.
It seems that something failed silently during the earlier installation. I was a bit suspicious because the Visual Studio app didn't have its own icon - it was using the standard MacOSX document icon. Having reinstalled, it has the correct purple icon.
When I am trying to run an ASP.Net Core project in Visual Studio 2015, a Microsoft Visual Studio dialog appears "The project doesn't know how to run the profile IIS Express".
Does anyone know anything about this message, or how to fix it? I've searched Google and the MSDN. There's nothing in the build logs, or the Windows event log.
This dialog showed up for me when I had migrated a project from dotnet RC1 to RC2.
Before the fix I could still run it using dotnet run and from Visual Studio choosing the profile other than "IIS Express".
I had misread this guide and forgot the .Web
\DNX\Microsoft.DNX.targets –> \DotNet.Web\Microsoft.DotNet.Web.targets
After fixing this and restarting Visual Studio(not sure if needed) I could run the project using the IIS Express profile.
Should also be noted that as per the comments, adding .Web in the top level node is required in the xproj. <Project Sdk="Microsoft.NET.Sdk"> should be <Project Sdk="Microsoft.NET.Sdk.Web">.
In my case the issue was solved after added the ASP.NET and web development tool extension to my VS instalation.
To clarify the answer from hultqvist, it is a problem with the xproj. To fix it, edit the xproj directly and change this
<Import Project="$(VSToolsPath)\DotNet\Microsoft.DotNet.targets"
Condition="'$(VSToolsPath)' != ''" />
to this
<Import Project="$(VSToolsPath)\DotNet.Web\Microsoft.DotNet.Web.targets"
Condition="'$(VSToolsPath)' != ''" />
That is, insert Web twice.
There is an associated issue in the aspnet tooling repo.
I had the same issue and found a very simple solution for Visual Studio 2017. In Visual Studio 2017 go to Solution Explorer then right click on your project file. In the menu you will see "Set as StartUp Project". If you can select it then select it. Now run your project again.
I had a similar issue but with "MyProjectName" instead of IIS Express.
In my case, I was trying to start as a standalone application, so I cleaned the launchSettings.json
I inadvertently changed the "commandName" parameter from "Project" to "MyProjectName" and that caused the popup to show up.
Resetting it back to "Project" solved my issue, silly me 😁
I had a similar issue, In my case ASP.NET and web development is enabled but Development time IIS support is not checked in the optional sections.
Once I enable the Development time IIS support solved my issue.
You can get this error with RTM if <BaseIntermediateOutputPath gets corrupted or is incorrect in your .xproj file.
I had this same issue and after digging around for a while I discovered that I had dotnet preview v1.0.0-preview2 installed under Programs Files (x86) and a non-preview version in x64. I think VS is launching the x86 (preview) version but expecting to see the full version. To fix this, I did the following.
from programs and feature uninstall every visible dotnet core. (note: this did not remove the x86 preview)
go to https://www.microsoft.com/net/download/core#/sdk and install BOTH x86 and x64 SDK packages
open command line and from the root directory check run: dotnet --version (at the time of writting it was 1.0.4
fire up .net core project in VS 2017 and run.
When I did all of the above, I was able to start up the site in IIS Express from VS.
This happened to me after a failed update of visual studio 2017 15.9.4
Setup completed with warnings and when I checked the problems saw that .NET core SDK 2.1 installation is failed.
I will try to install it manually.
Otherwise currently the only solution I found is to uninstall visual studio and re-install it.
In visual Studio 2017, i fixed this error by doing the following two steps.
I went to add or remove a program in windows, and deleted everything ending with ".net". I then reinstalled them in the visual studio installer. Then loading the project again produced a new error, which condiosluzverde provided the solution to here:
How Can I Fix the Microsoft Visual Studio Error: "Package Did Not Load Correctly"?
Same thing happened to me, my project was working fine. I didn't do any RC1 to RC2 update & this popup appeared from nowhere.
I fixed the problem by updating visual studio. You can also consider repairing VS.
My copy of Visual Studio 2012 is instable. It starts up and I can load projects, compile and run them. But from time to time it crashes randomly. It now also crashes when I try to add a new windows form to a project. But the crashes are independent from the project loaded.
My first idea was to install all new updates but if I go to the updates & extensions section it opens the dialog box and crashes 1 second afterwards. I then thought I might deinstall it and reinstall VS 2012 or 2013. But I also cannot deinstall it. If I go to windows programs to deinstall it I can click on the change button, but after this the installation program crashes. I also tried to download the VS 2013 preview and install it but this also crashes before showing a dialog box of window.
So I don't know how to proceed. Does anybody else have similar problems?
Try running Visual Studio in Safemode (devenv /safemode) or run it with logging turned on (devenv /log) the logs will be written to a folder in your user profile. Also check the Eventlog to see whether there's a error report. There should be 2 events logged when Visual Studio crashes. One "Application Error" and one ".NET Runtime Error". The latter will provide information about the stack trace that causes the crash:
When you try to uninstall Visual Studio, first remove update 1, 2 or 3, then repair or remove the whole thing. If uninstall fails, i'm afraid you'll need repave the machine to get it back in a supportable state. When you uninstall an update, you always need to repair Visual Studio itself before re-applying the updates.
Try removing all addins (Resharper, NDepend, etc) and extensions (either from the Visual Studio Updates and Extensions window or by deleting them from the Visual Studio or User profile folder).
Try resetting settings and add-in settings (devenv /ResetSettings) and (devenv /ResetSkipPkgs), try rebuilding all templates (devenv /setup).
You can even attach one Visual Studio instance as a debugger for the other to see where the exception occurs. Sometimes it can give you valuable information, sometimes the crash just doesn't happen because the actual issue is timing related.
If all else fails, open a support call with Microsoft, file a bug on Connect or do a clean re-install of your system.
Judging from you Error message you're running the Visual Studio 2012 Web Developer Express edition, instead of devenv, try wdexpress from a normal (windows) commandline window.
Another common issue that can make Visual Studio very unstable, is a corruption of the Add-in cache. Clearing it will trigger Visual Studio to rebuild it for you.
This is a general error with Visual Studio 2012 that has come up recently. While debugging any C++ application and after hitting a break-point, clicking "Go To Disassembly" will produce the following error dialog:
Disassembly cannot be displayed for the source location. Uncaught
exception thrown by method called through Reflection.
I've tried reinstalling and repairing VS2012 with no effect. Even the simplest console application will show the same error, so it's not specific to a project and has to be a problem with the system configuration. At this point I'm just clueless what module Visual Studio is failing to load - google hasn't provided any solutions either.
The only possible link could be my recent removal of older .NET Framework redistributable packages (since I've got .NET 4.5 SDK and multi-target pack, I figured the older ones weren't necessary).
I really need the disassembly view working (it worked quite well before) and I was hoping someone has come across this problem.
Solved: After downloading Visual Studio 2012 Update 2, the problem solved itself. I guess it was a bug with the vanilla release.
I am getting an Exception when I am trying debug my application on Emulator (Web Role).
you can see exception by clicking following link
Configuration which I am using Windows 7 pro, VS 2012 Pro, Azure SDK 1.8
Hope it might help others.
I Also had the similar problem and I restarted PC and **Run Visual Studio as Administrator**.
And let Visual Studio start the emulator with same privilege resolved the issue.
I was using Visual 2013 and Web API application under IIS Express.
Do you have IIS added? Most likely it's already installed but you've to enable it via Add Windows Compoenents on Control Panel...
I had this same issue all of a sudden, luckly I remember changing the ServiceDefinition.csdef file. I rolled this back to an earlier version and the debugger ran again correctly. The only thing I changed in the 'broken' version was instance size from small to medium.
Go to visual studio installer(search it from window's start)
and update the visual studio.
After updating, hit modify
button, after that on right side you will find a box named
debug (or something like that), select that box
Then hit install.
Restart your visual studio and debugger will start working.
In my case it worked perfectly.