i have followed this http://www.falconwebtech.com/post/2010/12/28/Debugging-Classic-ASP-in-IIS7-and-VS2010.aspx article to set my laptop to run classic ASP website via visual studio 2010.
However the page i run supplier.asp is not being rendered for some reason.
I can run the custom server alright, but in Google Chrome nothing is showing up.
The server is just not rendering classic VB script, i opened the source file in Google Chrome but there is no html code.
What could be wrong?
Related
I'm trying to debug an old asp web site on a windows server.
actualy I don't have any project files (there is no visual studio project file), what I have is only web pages in a directory ... I can run this latter on a IIS6 and everything works fine, the problem is that when I try to run those pages in a debugging mode nothing happens!
I enbabled the debugging mode on the IIS and I attached this latter's process to the visual studio (I'm using VS2005) I set the breack points... but nothing happens even if I ran those pages code the compile doesn't stop!!
I saw several pages talking about this topic... but I wasn't able to find a solution... do you have any idea?
(I want to add that the web pages, the IIS and the Visual studio ide are on the same server and I'm connected with the administrator session)
Make sure you when attach to set it to attach to Script code only and the break points must be within server-side code.
With Visual Studio 2005, 2008, and 2010 you can debug Classic ASP by attaching the debugger to the w3wp.exe process. This is very buggy and crashes often in 2005 and 2008, but works well in 2010. The only problem is that, as far as I can tell, VS2010 does not support Classic ASP code highlighting or code completion. HTML looks fine, but any Classic ASP code is just plain black-on-white.
I can't add <%#Script="VBScript"%> to the top of each page because of the site architecture, and even after testing that - it doesn't do anything.
This whole issue is highly confusing because with Visual Studio 2010 Express, the aforementioned Classic ASP support comes out of the box (minus debugging).
I can get alternating HTML and VBScript highlighting by switching between the following modes (but never both). I have tried the following: Tools > Options > Text Editor > File Extensions > Adding an "ASP" extension with the following Editors:
Automatic Editor Selector (XML) - gets the HTML right, but no dice on
the ASP
Microsoft Visual Basic - gets the ASP mostly right (lots of
underlined errors even though code is up to ASP standard), but no
HTML highlighting
Script Editor - HTML but no ASP
Web Form Editor - HTML but no ASP
I have considered extending the Editor, my thoughts being to try and mix the markup for the Web Form Editor and the Microsoft Visual Basic editor, but am unsure if this is a reasonable course of action.
How can I get code highlighting and intellisense for Classic ASP in Visual Studio 2010?
Solved!
TL;dr: Install Service Pack 1
Walk you through the troubleshooting process:
Uninstalled VS2010 Ultimate completely on machine with problems
Installed VS2010 Professional as per comments. This did not solve the
issue. Same problems as before.
On a new computer with a fresh install of Windows 7 I installed VS2010 Professional.
This time it asked me to install Service Pack 1 after installing
(http://www.microsoft.com/download/en/confirmation.aspx?id=23691).
Went into the asp code and it was highlighting and code suggesting
perfectly. Debugging worked flawlessly as well.
Returned to original (faulty) computer and manually installed SP1 and the problem went
away.
I have developed a website using Asp.Net MVC which uses a SQL CE database in the App_Data. The website when run in Visual Studio, runs fine. But, when i opened it as 'site from folder' in Microsoft WebMatix. It doesn't show anything. In IE it says "Internet Explorer cannot display the webpage" and in chrome it says " Chrome could not connect to localhost:49742".
This happens on the url, where database access is performed. Basic pages work.
I tried opening other website(MvcMusicStore) using 'site from folder' and it works fine. Why does it happen in the above case when everything is similar. I cannot do the debugging since it is not happening in visual studio
It probably doesn't work because you don't have configured your site with IIS (or another webserver like Cassini).
Probably while in visual studio you have configured your project to use "visual studio development server" with "Auto-assign port". If yes, it's visual studio that starts your web server every time you press F5.
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)
I'm using visual studio 2008 for a classic asp application. Will I be able to upgrade to visual studio 2010?
Yes, classic ASP can be developed just fine in VS2010 as it does in VS2008 SP1.
I've found this msdn page
http://msdn.microsoft.com/en-us/library/ms241740.aspx
it says:
Although the primary focus of Web debugging in Visual Studio 2010 is ASP.NET, you can also debug legacy ASP Web applications.
ASP Web applications consist of scripts, which run on the client in .htm files and on the server in .asp files; the Global.asa file; and .cdf files. Scripts can be in VBScript, JScript, or a mix of VBScript and JScript. They may also be mixed with HTML code and COM objects. You can debug ASP Web applications containing all of these elements.
Right now I'm working on classic asp pages with visual studio 2008 an everything works fine, I can even debug classic asp...
Still couldn't try it with vs 2010, but the page above gives me some hope...
Usually you can manually deploy an asp web site direclty to the inetpub\wwwroot folder (just paste all of your required web page files to the wwwroot directory), where your default.asp page should reside at the root of wwwroot, if that makes any sense.
Then you can create an empty web site with a single project, start your web site by entering http:\localhost in to a new browser window, and you should see your default page displayed.
You can add all of the extermely old asp files to your new fangeled visual studio 2010 application directly from the wwwroot directory.
You should be able to compile your application but you won't be able to debug it at this point.
To debug the ancient application, simply attach to the internet explorer process with the title of your outdated web application (or the wp3p process....), and you will then have debugging functionality.
Or, you can wait for the old yet useful app to throw an error and then use visual studio 2010 as the J.I.T.debugger.
Hope this helps as well.
Happy coding! (if that is possible in classic asp, thank GOD for visual studio)
(-:
To get VS2010 to support .inc files as well as .asp files, see the related question Can Visual Studio 2010 do ".inc" file syntax highlighting?
VS2010 syntax highlighting for .inc files isn't very good even with the Web Form Editor in use; the HTML shows up fine but the VBScript looks like plain text.
I updated my project from VS2008 to VS2010 and everything has been going alright.
In order to get debugging to work with javascript in a script block I have to add a debugger; statement to get it to break. If you have the javascript in a seperate file you can debug with just a break point. The Classic asp will still debug if I attach to the w3wp process.
The javascript intellisense has been working better for me in VS2010 than in VS2008. In VS2008 I had issues with it crashing when I stopped debugging classic ASP. In VS2010 I don't have that problem any more.
Overall I'd say VS2010 does classic ASP development better than VS2008.
For anyone who wants Syntax Highlighting in VS 2010 and can't get it working. I think this works.
Tools>Options>TextEditor>FileExtension
Add the extension ASP and it should be attached to "HTML Editor with Encoding".