I'm not getting any errors, I just can't for the life of me get CSS out of the LESS files in my solution on build or save. I've restarted everything and installed from scratch to no avail - it's just not working. What can I do to troubleshoot this?
I have uninstalled the Web Essentials Extension then installed the Version 2.5 for Update 4 at https://github.com/madskristensen/WebEssentials2013/releases
And it worked again.
Related
I have installed the Visual Studio 2019 community version 16.4.4 on a brand new laptop
OS:- Windows 10 Home Single Language
The following are the .NET Core SDKS installed in my laptop
The command dotnet --info gave me the following details
I created a Azure function with V3 template
The project settings are given below
When I try to debug , i get the following error
A fatal error has occurred and debugging needs to be terminated. The debugger was configured to use the Desktop CLR (.NETFramework) Managed debugger, but the target process loaded the CoreCLR (.Net Core) runtime. To debug this project, configure it to use the 'Managed (CoreCLR)' debugger."
Tried several options like the one mentioned in the link below
https://social.msdn.microsoft.com/Forums/en-US/59f880f7-ed60-4842-bc55-a9400971c58b/problem-debugging-net-core?forum=vsdebug
EDIT: This has been fixed in the latest release of Visual Studio v16.4.5
The problem seems to be a mismatch in the version of the Azure Functions CLI. As a workaround, you can do this:
Install the latest Azure Functions CLI, from the command line run:
npm i -g azure-functions-core-tools#3 --unsafe-perm true
or if you are using Chocolatey:
choco install azure-functions-core-tools
Restart Visual Studio.
I still have this issue after reinstalling my VS2019, downloading the latest sdk and downloading the core tools multiple times. Seems like the only way for now is to run without using the debugger (Ctrl + F5). Sometimes I downgrade the function to v2.1 for this only happens on v3 functions.
Edit: I got this fixed when I updated my VS to 16.5.1
It looks like one similar issue which has been reported to DC forum. However it works well in my side with same 16.4.4 version. Since I didn't reproduce same issue, I can't provide a direct answer.
Here're some possible workarounds which may help:
Repair VS and go Tools=>Import and Export Settings=>Reset all settings=>No,just reset, overwrite... (Since my same version works well)
Hint from this one, you may backup the launchsettings.json in project and then delete it, rebuild and debug(F5) it again.
And if the issue persists, you can try installing .net core 3.0 sdk and recreate a new project to check if it helps.(I have both .net core 3.0 and 3.1 installed, but by default it picks .net core 3.0 when I create the project, not sure if it makes any difference.)
Hope it helps :)
Update:
Sorry for not noticing that the solution will not work for you. Since the solution doesn't work, you can choose another way. As the error says, you need to
configure it to use the 'Managed (CoreCLR)' debugger."
So, try to configure on hand, Select 'Debug' above the VS 2019 tab, then
Original Answer:
I faced exactly the same error before and solved it with below solution, it works well.
Solution:
Just enable the native code debuging.
Right click your project > properties > Debug. Tick 'enable the native code debugging' like this:
I have the same issue, I have upgraded visual studio 2019 to 16.4.4 and it resolved my issue. that was the bug by visual studio 2019 in 16.3 versions. please upgrade visual studio. it will definitely resolve your issue.
Issue was resolved with the next upgrade of Visual Studio 2019
Trying Install the v3.x Core Tools package from the command line run npm install -g azure-functions-core-tools#3.
Reference: Use npm to install Core Tools on Windows
"...Please repair Visual Studio 2015 Update 3, then install this
product again."
I'm getting this when I try and update the ASP.NET Web Tools Extension in my version of VS 2015 which I installed only today. After I got this error I checked and my version was Update 3. I tried to install it regardless and got a message saying that I already had it.
Any ideas on how I can get around this issue?
Ok after some digging I got to the bottom of this. It seems that I need to have .Net Core Installed. However when I go to install that I get the same error. The workaround is to run the downloaded .exe from the command line with the added parameter:
DotNetCore.1.0.0-VS2015Tools.Preview2.exe SKIP_VSU_CHECK=1
This will install the latest version of Web Tools as well.
Instead of downloading it from VisualStudio tools update tab, just go to http://www.asp.net/core and download the latest dev tools DotNetCore.1.0.0-VS2015Tools.Preview2.0.1.exe.
Installed perfectly for me.
If I create a brand new Cordova project (JavaScript or TypeScript) and try to debug on Ripple or on the local machine I get an error during build that says "Could not locate the appxrecipe file."
I googled it and nothing comes up. What is this file and how does it get generated? Shouldn't it be generated when I create the project?
I've already lost an entire day to this, running repairs on visual studio and trying things that had no effect. Frustrating!
This took a while to figure out but it seems that the version of node.js that would get installed with Visual Studio was too old (0.10.x). When I installed the x64 version of node.js from the node website, it installed a 64 bit version which also wouldn't work with Cordova in Visual Studio.
The answer was to install the 32bit version of node.js (node-v5.1.0-x86.msi) available from their website. Now everything compiles correctly!
I was also stucked with the issue but my problem was little bit different. I wanted to build a project for Windows 10 Mobile platform.
It was really weird because everytime when I tried to build a project from CLI with ionic build windows, the build was successul. But it had been throwing the error about appxrecipe file while building with Visual Studio again and again.
Then I noticed that everytime I open a project in Visual Studio (2015, Community Edition) there is one change when you open your confix.xml file in Visual Studio editor - the change was that Windows Target Version was set to 8.1 again. I tried to change it to Windows 10 again, save it and build but the error was still there.
I have solved it with installation of Microsoft Emulator for Windows 10 Mobile and it works like a charm now. Maybe this information could be helpful for somebody...
I've recently upgraded my OS to Windows 10. I have a very basic Silverlight 5 application which gives me Unable to start Debugging. The Silverlight Developer Runtime Not Installed. Please Installed a matching version error in VS 2010 whenever I am trying to run the project.
I have :
Target Silverlight version is set to Silverlight 5 in web project.
I have installed Silverlight SDK, Silverlight5_Tools with SP1 installed & Silverlight Runtime which is 64-bit.
After doing all these steps and going through many online posts, still I'm unable to resolve this issue.
My Doubts are :
Do the Windows 10 upgrade has anything to do with this situation?
Windows 10 comes with a new browser Edge, is this because of this browser? Like Silverlight compability.
Again I am not sure but these are my doubt. Any suggestions?
Do you have a 64 bit OS ?
If so - uninstall Silverlight (developer!) and make sure you install the silverlight.exe (developer!) not the 64 bit version.
That worked for me.
HTH
Go to the properties of the Web folder start project. Click Web on the left tab. Unclick Silverlight in the debuggers.
Not a total solution but at least it allows you to debug other portions.
I had this issue and Uninstalling and Reinstalling didn't work.
Error in debug mode (F5 Debug solution configuration) was "Unable to start debugging. The Silverlight Developer Runtime is not installed"
In Debug configuration I would get the above error but finally I put the solution into release mode and it worked - then back to debug mode and everything worked without error.
Seems like a really odd fix but sure enough closing and re-opening the solution everything works now - Same install procedure as OP.
Another thing that's interesting is, the Debug only works in Chrome. If I target IE or edge I still get "Unable to start debugging. The Silverlight Developer Runtime is not installed"
I uninstalled Silverlight and then installed Silverlight_Developer.exe. I also switched default browser in Visual Studio to Internet Explorer (I have Edge otherwise which won't work...).
Nice to see some more people also using Silverlight these days, hehehe.
This is a really old thread, but I just ran into this issue with a project. I was getting the message that the Developer runtime was not installed, but in fact it was, and another similar project ran just fine on the same machine with the same version of VS 2015.
The fix was to ensure that the startup project is the WEB project, not the Silverlight project. Somehow, the default startup project got switched to the SL project. After I switched back, then it worked just fine.
Razor intellisense is not working for me. I do not have Resharper installed and I downloaded both the vs 2010 pro trial and asp.net mvc 3 release this week. Everything is working fine except I get no intellisense.
Is there something related to the trial or xp sp 3 that could be causing issues?
Is there a log or something I can look at to provide information to troubleshoot?
EDIT: I don't see a datetime anywhere on this so I wanted to emphasize this was installed 3/1/2011.
I have tried deleting the ReflectedSchemas folder and resetting my vs2010 settings.
I was able to solve this after a grueling 6 hours of uninstall issues.
I uninstalled all the MVC3 compnonents along with VS 2008 MVC2 tools which I did not realize I had.
I had a horrible time with the uninstall and reinstall. I had to constantly open Task Manager and stop the devenv.exe process as it would hang after uninstalls and installs would complete. Sometimes this would prevent the uninstall/install but eventually everything worked.
after spending hours of install/deinstall stuff to get the razor-editor installed on my production machine (that did not work) - I finally managed to get it going.
All I did was grab the VS2010 SP1 RTM, install it and then reinstall the latest ASP.NET MVC 3 package - no previous deinstall.
And finally I see the razor-editor .... now only if I could get a working Async CTP ;)
I Only had to uninstall MVC2 for vs.net 2010 and the intellisense started working again.