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".
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.
Given a working Internet application written in classic ASP (with some VBScript) and an IIS 8.
Now I have to debug that application probably in VS2012 or VS2010.
I hear about some rumors, that I can configure the IIS to do that.
Furthermore when I write STOP keyword to the code file (in text editor) then the visual Studio will be triggered to attaching the actual debugger.
Please help me with these IIS or other settings, and ask if the situation is unclear.
What are tried:
in your iis in the asp section set under debug properties "serverside debugging" to "true".
I had to attach to the IIS working process w3wp.exe in Visual Studio manually. Somewhy that wasn't automatical but i saw cases on other computers when it was...
I have a classic ASP website deployed over IIS.
I am opening that website from the same location in visual studio 2010 (in order to debug, as per the steps mentioned here
The problem is that, when I hit F5 in visual studio it is giving me an error saying "your server does not support debugging of asp net or atl..."
I am able to browse the site from IIS, but I want to open it in Visual Studio in order to debug it.
What could be the possible reason and solution of this issue?
F5 doesn't do anything good for classic ASP sites (f5 will try to compile a .NET site and then access it).
I will assume that you are trying to debug the site on the same machine where it's running. The way you debug "classic" ASP using Visual Studio.NET is by attaching to the process running the site. The easiest way to do this is to use the Just In Time (JIT) feature: insert a stop statement in the code (debugger in jscript) - hitting that line should initiate a server-side "Error of type "Script Debugging" was encountered. Do you want to debug?" dialog, with suggestions of available debuggers to use.
Try this and report what happens - there might be some extra steps needed to configure that machine.
Are you using IIS 7?
If so you should the server option "Enable server side debugging"... It should be in the properties window of the site, using IIS Management Console.
Once you do that, when you run the server through Visual Studio, it should open another solution on debugging mode with the relevant 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'm running Visual Studio 2010 Premium on a Vista 32-bit machine and I've noticed that sometimes when I'm debugging a website project I can't edit an aspx file. If I close the file and open it again then I can edit it. Has anyone else encountered this problem? The only extensions I have installed are the VS Productivity Power Tools and Power Commands.
I also experience this problem (using Windows 7 or XP). This happens when:
I don't already have the .aspx file open in Visual Studio 2010
I am running the web app in debug mode
The file lock happens when I open and then try to edit an .aspx page (e.g. to tweak a bit of HTML) that I am currently viewing via a web browser when running the app in debug mode.
I've yet to find a solution for this problem however as a workaround I use "Browse With..." (Right click in Solution Explorer) to load and view the page(s) when I'm making HTML refinements. You can't debug code but it doesn't lock the files.