How can I preview Classic ASP in the browser when using Microsoft Expression Web with XP Pro

The content must be parsed by IIS. So, you must ensure the site is saved into C:\Inetpub\wwwroot (and then perhaps a sub-folder - "MySite"). Then, open your browser and type http://localhost/mysite/page.asp. That string will be passed to IIS, which will execute the ASP in the page before it outputs the result.

With any type of server-side scripting it is not possible for you to run the files directly from the file system, otherwise you get the issue you are seeing.

-tigermatt

Thanks - I do have the sites in the wwwroot folder
Calling the page up by your method (the localhost path)  works  perfectly and the page comes up without a problem.
The trouble (or inconvenience) comes when developing sites in Expression.
Previously I could work on an ASP page - click on "preview in Browser" to check the result - now I can't.
The fact that your solution above works means that all the necessary ingredients are there, but for some reason they will not work within the Microsoft Expression application whereas when used with Server 2003 they will.
Any idea how I can overcome this?
kind regards

Just been researching this and it looks like Microsoft Expression Web has a built-in mini web server which can be used for testing ASP sites. Perhaps you have a problem with this instead.

I wonder, would a reinstall or repair install of Expression Web help?

-tigermatt

Thanks for the effort. I have tried that a few times.
In fact I first ame across the problem when I had Vists on my laptop and made many attempts to get it to work. I then assumed that the problem lay with Vista and downgraded to XP Professional - the problem is still there.

I can preview HTM, HR+TML, ASPX, but not ASP.

kind regards

I think that it does that anyway, because you can still preview the other files - HTM and ASPX - with the browser.

rgds

OK I've got it - thanks for your guidance.
Expressions will "default" new web site to "My Websites" within "My Documents" and in that case the ASP page cannot be previewed in the Browser.
If you set the new website to http://computername/websitename the whole thing works well.

I am sure that there is probably a better way of doing it but this "workaround" will do for me.

Thanks for your help

Many thanks for your help - you may not have come up with the complete solution but your input helped me to solve it and that was very valuable.

rgds

Good you sorted it - that was the route I was thinking you would need to take. It is very similar to the way dreamweaver configures it!

Thanks very much :-)