This question already has answers here:
How do you debug classic ASP?
(7 answers)
Closed 3 years ago.
I've tried all possible ways but not able to debug the classic code. I tried attaching the process to IIS and enabled debug in IIS, tried several steps but still no luck, any help will be very much appreciated.
I've tried all the related articles still no luck so im posting this for more help.
1.Open Visual Studio 2010
2.Open your website in Visual Studio
3.Fire up your web site.
4.In Visual Studio, click ‘Debug’ Menu -> ‘Attach to process’
5.You may need to tick the box labelled ‘Show processes from all users’
6.‘Inetinfo.exe‘ if application protection is low or ”dllhost.exe‘ if application protection is higher. You may get an ‘Attach Security Warning’ popup. If so, continue On. It’s a bit scary at first, but if it’s your own app on your own PC, then you’ll be ok.
7.Add a breakpoint to your code, and navigate to a location where you will hit it.
Source: http://www.jameswiseman.com/blog/2010/10/12/debugging-classic-asp-from-visual-studio-2010/
Related
This question already has answers here:
Code editor appears blank
(10 answers)
Closed 6 years ago.
I have been using VS for many years. Today I have encountered a very strange problem with visual studio 2013. Suddenly for some reason I am unable to see any text in the editor window. I've tried reloading the files, redocking each window, restarting VS, restarting my machine and resetting all my settings in Tools -> Import and Export Settings. At present I'm completely stuck as I can't do anything. The tab for each opened file appears at the top as expected but just a blue pane. I'm hoping this is something daft!
I just had the same Problem. However MVVM Light is not installed. I deactivated all extensions that to my knowledge could interfere with the editor and restarted. Problem solved.
Then I reactivated the extensions bit by bit, now all are active again and the problem is still gone.
This was caused by the installation of MVVM Light via the extension manager. I uninstalled it and it went away. Installing the required dlls via nuget didn't have the same issue.
Im using VS express web developer, and attempting to create a new MVC project. The problem is, VS hangs when adding EntityFramework to the project. Its attempting to add EntityFramework 4.1.10331.0 to an MVC 3 project. Any ideas what might be going on?
It has been a while since you asked the question, but I recently stumbled across a similar issue except with MVC4 adding EntityFramework.5.0.0 in Visual Studio 2012 Ultimate.
The issue was that I was trying to create the project in a network folder (I run Windows 7 in a VM on top of OSX).
The problem appears to be that the network folder is not considered a Trusted Location. I had to go into Control Panel -> Internet Options, click "Security" tab, Click "Local Intranet" zone, then click Sites button.
In the "Local intranet" dialog which pops up, I un-checked "Automatically detect intranet network" and checked "Include all network paths (UNCs)"
Now I guess Visual Studio and/or nuGet see the network folder as a trusted location, and EntityFramework.5.0.0 is installed along with everything else a new MVC 4 project requires.
Credit goes to my colleague who referred me to this SuperUser post.
Bit of an old question, but it's still an issue today so this might help someone looking for a solution.
I don't have enough rep to comment on Chris Cameron's answer, so apologies for submitting it as a new answer - all credit should go to Chris. I found that to get it working I also needed to check "Include all local (intranet) sites not listed in other zones." Chris' solution then worked like a charm.
Im trying to step through a classic asp page which is hosted in iis7 in Visual Studio 2010. Ive followed a few blogs, mainly these ones:
"http://blogs.msdn.com/mikhailarkhipov/archive/2005/06/24/432308.aspx"
"http://social.msdn.microsoft.com/Forums/en/vsdebug/thread/eff76bd0-6421-4ba5-b063-a348eec27ebb"
It seems that the breakpoint I set is not hit when I browse to the page in question, I think this is because the application is all in frames. When monitoring the process in sql profiler it looks like all session information is gathered once the page starts up, having been browsed to from iis7, after I log in using the login page it doesnt actually get any more information.
Has anybody got any tips for debugging frames in classic asp with VS2010 and iis7?
UPDATE: Turns out there was a hidden setting in the database that meant when I ran the application up it was going to a different system.... which would explain why it wasnt hitting the code - Visual Studio 2008 actually told me in advance that the breakpoint wouldnt be hit.
i'm using the vbscript keyword "stop" in my source code. this is just like a breakpoint in visual studio. a window pops asking you which debugger you want to use, select visualsudio 2010 and you're fine...
you have to set server debugging to true in iis 7 (asp section)
Following my last question (see: Problem in hosting ActiveX on Vista (in a Visual Studio 6 C++ application)) I ran into a strange problem. I hope this’ll be a simpler issue to the experts here:
Each time I run certain application like iexplorer or firefox, the Visual Studio 6 suddenly opens up in debug mode with a message “User breakpoint called from code at 0xSOMETHING”.
I can press F5 to continue but the applications run slowly and needless to say I have no wish to debug these applications…
My guess is that when I worked on my VC++ application I placed breakpoints at windows methods like CAxDialogImpl::Create(), AtlAxCreateDialogA() etc’, and for some reason it was kept somewhere.
Of course I now removed all the breakpoints and re-compiled the project but still this keeps happening!
I checked in the tools->options but the “Just-in–time debugging” is not marked.
Any idea?
(I use Visual Studio 6 which I installed on Vista)
Thanks a lot,
Erik
Not sure this helps but anyways:
Try disbaling the default debugger option. (It says Dr. Watson but it depends what you have set as the default debugger)
http://www.bridgetonova.com/2007/09/how-to-disableenable-windows-default.html
Also as per this post Visual Studio 6 is not supported on Vista. Only Visual Basic is.
http://www.itwriting.com/blog/167-visual-studio-6-on-vista.html
You should probably re-ensure yourself that you have removed all calls to DebugBreak() and manual break-points. Also try to ensure that when you recompile you re-register everything to point to the right places (i.e. the activex pointed to by the guid in the registry is actually the latest recompile).
i try to debug a windows gadget. Just-In-Time debugging fires up and i can see an VS2010IDE attached to the sidebar process. But there is no source code to debug! Only a blank file with the yellow debug pointer. What is my problem?
Configuration of my system is based on this article:
Gadgets for Windows Sidebar Debugging (http://msdn.microsoft.com/en-us/library/bb456467(VS.85).aspx)
We have posted on the MSDN forum about this.
I think script debugging is broken in studio 2010 beta2.
I cannot get script debugging to work on my ASP.NET MVC project either.
We get a blank page, and the IDE cannot find the code to debug.
Trying to open files in the Internet Explorer tree in solution exlorer results in blank files being opened.
I think it's a bug - and afterall it is a beta.
I also had this problem, and for a while I was thinking it might have to do with my machine being 64-bit, or a permissions issue, but I have no way of confirming it.
However, I was able to solve it by using the template on this Code Project site:
http://www.codeproject.com/KB/gadgets/HeterodoxGadgetTemplate.aspx
The nice thing about the template is that it's setup as a Windows application. When you run the app it handles the local deployment of your gadget and starts the sidebar service (sidebar.exe). I believe this probably gets around a number of permissions issues.
After setting up a new project using this template, I was able to successfully debug the JavaScript using the "debugger" methods explained everywhere else (for example: http://msdn.microsoft.com/en-us/library/bb456467%28v=vs.85%29.aspx).