Unexpectedly stopped working for me debugging classic ASP in Visual Studio 2015.
I have enabled Server-Side Debugging and on error and trying to lunch VS (and break app) I got error that I need to find file to view source. When I trying to browse for it I got another error with "Unable to open script document".
Also when I set breakpoints in code and app reach this places I got this same message: "Unable to open script document".
I tried to:
uninstall/install VS
reset all VS settings
remove/add IIS
After day of searching solutions I found cause of the problem..
Yesterday I added prefered editor to .asp files in Tools -> Options -> Text Editor -> File Extension. After removing .asp extension from list Debugging start working.
I had this same issue but off of a fresh upgrade to Visual Studio 2017. It was my exception settings catching 3rd party java script libraries being loaded in. I fixed this by turning off JavaScript Runtime Exceptions and WebKitJavaScript Exceptions.
Related
I have an ASP.NET Core application which was running fine but while developing (and after the Windows 10 April update, most likely just a coincidence) suddenly, I got two messages:
This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed,
create an association in the Default Apps Settings page.
Unable to start program 'programName' Invalid pointer
Result: I cannot debug/ run my application anymore. (Start Debugging/ Start Without Debugging)
I found some scary search results talking about a corrupt file system but I don't think that it is something like that in my case...
I checked my startup projects, restarted Visual Studio, restarted the whole system... nothing helped.
Update: After installing the latest Visual Studio update (15.7.1), the message I get when I activate the JavaScript debugging again has changed. Now it states:
Cannot connect to runtime process, timeout after 10000 ms - (reason:
Cannot connect to the target: connect ECONNREFUSED 123.0.0.0.1:53232)
Result: Still the same. Only the error message changed.
Any hints, ideas about that one? Thank you!
If not an answer at least a workaround. I can work again if I tweak the debug options
Debug -> Options -> General -> Enable JavaScript debugging for ASP.NET
(Chrome and IE)
If I disable this feature, I can debug and run my application again. But I still don't understand why this is happening now nor how to use JavaScript debugging now...
I had this problem with Visual Studio 2017. It was caused by my antivirus (bitdefender) blocking a chrome temp file. I set it to ignore that file and that fixed my debug issues.
The file was C:\Users\[username]\AppData\Local\Temp\vschrome_diag.lnk
According to this, re-installing chrome may fix the problem.
Error launching vschrome_diag when Visual Studio 2017 starts debug on Chrome
When I start a newly created Typescript Project in Visual Studio 2017 theres some strange behaviour going on.
-The debugger breaks on the very first line
-The output shows:
code:-32000
message:Debugger agent is not enabled
-Many scripts in solution explorer (see screenshot)
-Node output:
Debugger listening on wb://127.0.0.1:5858/03dde2a0-7ae8-44fc-8b29-53b99c072de7
For help see https://nodejs.org/en/docs/inspector
Debugger attached.
Screenshot:
Edit: Seems to be a problem with the new node version. If I switch back to 5.4.1.0 (included in VS2017) everything works fine. I read that there has been a change in debugger protocol maybe it has something to do with that... gotta wait for an update.
To show the Console, we can use: Debug -> Windows -> JavaScript Console.
Michael Braude showed two suggestions for the similar issue:
1.Use JavaScript Console of Visual Studio. Frankly, this way is OK for me when I am developing on PC with two displays (I runs emulator on
one screen and debug with Visual Studio on another), but a bit
uncomfortable when I am developing on Notebook with one screen.
2.Run a solution without debugging (CTRL+F5), in this case VS's debugger isn't attached to browser. This looks as simple solution, but
you need to be aware that in this case breakpoints don't stop run-time
and you have to use debugger; keyword.
For detailed information:
Visual Studio Tools for Apache Cordova stops work correct after update
I got it working again by using the included node version of VS2017. There seems to be a problem with the new version <8.
You can choose which version to use by putting the path to the exe folder on top of the list here: Tools > Options > Projects and Solutions > Web Package Management > External Web Tools
When i try to access my solution Properties, i get the following error:
Object reference not set to an instance of an object
I am using VS 2012. What could be the cause of this?
Some extensions may cause this.
Try disabling extensions and restarting Visual Studio.
Quite often error will be gone even if you re-enable extensions after this.
There's a bug report on Microsoft Connect (link).
It is marked there as "Closed as External", but it seems that it may occur randomly with any extension, so would be worth voting it there to bring it to Microsofts attention.
In my case, the problem was solution-specific. NuGet was causing this error, but not the extension itself but a NuGet package that generated an error on VS load. When I opened NuGet Package Manager Console I saw a big red text with a description of the error. In my case it was T4Scaffolding.Core package, which in turn is a dependency of MVCMailer.
If this is your case, you will probably see what package generates an error in PM Console.
I faced this dialog too and i'm not sure what exactly causes this as i couldn't even open the NuGet console to see detailed error messages.
Closing Visual Studio, deleting %AppData%\Microsoft\VisualStudio and restarting Visual Studio worked for me as it causes a reset of various things like window configurations.
I think if this dialog is displayed some files may be corrupt in %AppData%\Microsoft\VisualStudio and by deleting that folder Visual Studio can start normally again.
Update:
The issue arises on my machine when i start Visual Studio by using "run as administator" whereas Visual Studio has been started before without that option and %AppData%\Microsoft\VisualStudio had been created without the administator association.
Visual Studio 2013: I had this issue when I tried opening TOOLS -> Extensions and Updates.
I used #ViRuSTriNiTy idea, but only cleaned the files from:
C:\Users[myUserName]\AppData\Local\Microsoft\VisualStudio\12.0\Extensions
There are 2 cache files over there.
Deleted them and restarted VS2013 and it was fixed
The way it was happening for me might be unique to me/my setup, but I'd love to know if anyone else has this happen, and if they find out why:
If I launch an .sln file by double-clicking it, it will load VS and I can right-click the Solution and get Properties to come up no problem.
If I go to "Open Project" on the Visual Studio welcome page or from File > Open > Project/Solution, navigate to the .sln file and launch it by selecting it and clicking "Open" in the File dialog, that's when I have this issue.
I'm going to just always launch the .sln file from now on, but I'd love to know why this happens when using "Open Project" from the welcome page or from File > Open > Project/Solution! I tried going into Tools > NuGet Package Manager > General and I unchecked the options for allowing NuGet to download missing packages and Skip applying binding redirects, and under Package Sources I de-selected the checkboxes (my dev machine does not connect to the internet). Environment > Extensions and Updates: I tried it with and without "Load per user extensions when running as administrator" and running it as an Admin and without running as Admin. Also tried just deleting everything at C:\Users\me\AppData\Local\Microsoft\VisualStudio. No change from those 2 bullets above.
I'm trying to compile a project I have in Visual Studio 2010. It has built fine on 2 other computers with Visual Studio, but on this computer, it will not compile, and returns:
"The property could not be read/written because the language service returned an unknown error"
Obviously, I have tried googling, and nothing of any use came up, so some help would be great.
Additional Information:
Project is an XNA 4.0 Project
Trying to deploy the solution to a Windows phone. The phone is plugged in, unlocked, etc. and other projects will deploy successfully to it.
I've run into the exact same error message when I tried editing the AssemblyInfo.cs using VS 2010's Assembly Information dialog from within the project properties (open Properties -> Application from below the given project).
As this thread suggests, I deleted the AssemblyInfo.cs file and filled in the values I wanted in the dialog box which created a new and working AssemblyInfo.cs. Maybe this would help/would have helped in your scenario as well.
Note, that you'll get a fresh and valid GUID if you simply click save after opening the dialog.
I encountered this today in VS 2017. It went away as soon as I performed a build which fetched all my references.
I'm building a project in Visual Studio 2010 and the build fails because it cannot copy the assemblyname.dll file from obj to bin folder. The exact error message is:
Error 7
Unable to copy file "obj\Debug\AssemblyName.dll" to "bin\AssemblyName.dll". The requested operation cannot be performed on a file with a user-mapped section open.
I think this is because the previous file in bin-folder is not accessible. When I try to delete the file manually, I get an error "The action can't be completed because the file is open in another program". If I try to see what application locks the file with Unlocker, I don't get any results (No Locking handle found).
If I restart Visual Studio, the error goes away but happens again after a build or two. Goes without saying that this is seriously slowing me down. Any advice how to start solving this?
VIsual Studio 2012 on Windows 8. I was receiving the same error message on my project. Restarting Visual Studio or cleaning the obj folder manually did not help. Finally I closed all open files (Windows -> Close All Documents) and the problem went away.
This behavior was due to a newly installed Visual Studio extension called Visual Studio Achievements (http://visualstudiogallery.msdn.microsoft.com/bc7a433b-b594-48d4-bba2-a2f24774d02f)
I noticed that the .pdb file was locked by FxCop (using Unlocker) and I think that the Achievements -extension uses it. After disabling the extension I've no longer got the error mentioned above.
This bug has been fixed in recent versions of the extension (>1.7). It was released as a beta, btw...
This behavior of VS happen very often even on my computer (and on computers of my coworkers).
In my experience it happen more frequently when:
I have some form opened in design when i compile
I stop the execution od the application by pressing the "stop" button
in VS instead of exiting the application
So, closing the form in design before compile, and exiting the application instead of stopping it, somewhat mitigate the issue... but it still happen :-|
My computer is Win 7 x64 SP1 with VS 2010 SP1, 8Gb ram, and no swap file
Platform: Windows 8 Pro, Visual Studio 2012
I found that I receive this error when I am accessing the folder in Windows Explorer.
I was creating PDF documents with Visual Studio 2012. To review the sample document I would right click in Solution Explorer and use Open Folder in File Explorer.
On Windows 7 I would get a SYSTEM.IO error if the actual PDF document was open in Adobe Reader which is expected. With Windows 8 I found that I receive the above error if I have the folder open. I suspect there is a conflict with the Windows 8 preview.
If I close the folder and run the program it works fine.
Check if you open the dll in visual studio.
I open the dll in visual studio and this error happen!!