I am trying to learn ASP.
I set up IIS on my Windows 7 machine and now I am trying to write some simple code.
C:\inetpub\wwwroot\iisstart.htm
displays fine, but when I request
C:\inetpub\wwwroot\MyWeb\test1.asp
the browser prompts to download the file instead of displaying "Hello World"
This is the code I used:
<html>
<body>
<%
response.write("Hello World!")
%>
</body>
</html>
I don't think there is something wrong with the code.. Could have I messed up some configurations?
Thanks in advance.
Sounds like when you installed IIS you did not tick the optional extras that include asp, for example, when you tick "Internet Information Services", it does not select ASP etc unless you drill down into "Application Development Features" and tick them manually:
Also, to be clear, if you want to develop in classic asp (.asp files), you only need ASP, but if you want to start serving ASP.net (.aspx) files tick ASP.net.
Strictly speaking, there is no harm installing all of the Application Development Features.
Related
We're trying to show a web page on pepper's tablet, but something goes wrong. How can we get the browser's error messages to debug the web page?
We know js 1.5 is implemented, so we installed all kind of polyfills for Promises, forEach, etc. But no luck. How can we get meaningful debugging info?
thx
Sven
I create a git for showing a web page and send event with the module ALMemory ( see it for an example). For debugging, it is more complicated but you can also try this. You can create a template for showing web page and connect directly it to your robot. For example, you install it on your pc and create a web-page template with python jumpstart.py service-tabletpage my-package-name MyServiceName. A package will be create in a file output. Open this app on choregraphe and install it on the robot. You can after that launch on your computer the web page (double click on index.html, name by default) and just adding at the end of the url ?robot=ip_of_the_robot. You can now debug your code.
Iam working for a new client and It has a very old web app with some pages on asp (render as quirks mode IE 5.5) and some in aspx (render as IE7), the app only works on IE.
Iam the only fonrt end developer in teh company and I would like to use new techniques like bootstramp and SASS but the site suses a framset with different frmaes inside.
Would you recommend me any adivce of how to start imprroving the web app?
Thanks, (Iam not sure where to start specially beacuse the frames are not allowing me to have a one page where to call evrything they are include libraries like Jquery on all the frames)
Any idea would help.. any advice
Thanks!
It looks like my server has ASP disabled because when trying to view an ASP file its source code is shown in the browser. After doing some research I've heard I can enable ASP on my server using IIS - is this correct? I've set up my website in IIS as far as I could; it's not asked me for FTP details or anything so I don't know how it's going to 'install ASP'... I've enabled ASP via the Control Panel so it appears within IIS, but don't know where to go next. Am I headed in the right direction?, could anyone give me some advice as I'm not sure if I'm barking up the right tree. Many thanks in advance.
I just tried this on my Windows 7 Professional box. Once I added the feature using "Add Windows Features", and refreshed IIS Manager, Classic ASP just showed up in the handler mappings.
Make sure Enable Parent Path = true in behavior Section of ASP in IIS.
Go into your programs > windows features. Find IIS, and go to www services. You should see ASP there. You may have to enable it in IIS as well - you haven't mentioned what version of IIS you're using (or OS), so I'll leave that up to you.
I have created a stock Web App in VS2010. In Cassini the web-app is rendered normally, but in IIS no styles are shown. I am using IIS 7 in Win7
Probably a security issue with the folder that the css is stored in. Easiest way to debug (imo) is using Fiddler or Firebug and seeing what is happening to the request for the css files.
Trying to copy a website to a new server as the old one is dying. :(
I tried copying over the files and setting it up manually, but some specific user accounts needed to be used and the guy who set all this up left the company nearly 5 years ago. And is even worse at documentation than I am.
Anyway, at that point the ASP pages were serving, but getting errors. Ok, fine... I went back and exported the configuration from the old server (lucky that worked at all) and created a new website from that config on the new server. On the new website, from the config file, the ASP pages are giving 404 errors.
The Active Server Pages extension is enabled, and I can actually get the asp pages to serve from another website on the server... so I'm thinking it's something at the website level. No idea what though.
Any ideas?
Back when I was doing classic ASP development we used Parent Paths. This is at the top of your ASP file you'll see something like;
<!--#include file="../../resource/includes/MSSQLconnection.asp"-->
This isn't enabled by default in IIS. It may not be answer but worth looking at. But was a long time ago now.
Hope this helps,
Mike
404 is a file not found error.
Start by checking you can access a 'hello world' HTML file in the folder using http: //localhost/path/toyour/HelloWorldFile.htm
Hello World
is all you need in the file = you don't need to bother with any HTML markup to test what we're interested in.
This will check that your virtual directories, application settings etc are correct before you move on to the Active Server Page settings.
Once you've got your paths sorted out and you know you are looking for your application in the correct place move on to a 'hello world' ASP file
<%="Hello World"%>
is all you need in that file!
You ask about settings in IIS which will stop ASP from working. These come to mind as the most obvious.
Depending on the OS (or more specifically the IIS version) you may also need to activate ASP pages.
These instructions from msdn cover Windows 2003 (IIS6) and Windows 2008(IIS 7.x)
If you can get your hello world script working you can move on to debugging your application.
It will be a great help when debugging the application if you can see what's going wrong so I recommend that you turn off friendly error messages if you are using Internet Explorer. Also set IIS to pass error messages on to the browser
see:
http: //learn.iis.net/page.aspx/564/classic-asp-script-error-messages-no-longer-shown-in-web-browser-by-default/ --excuse the link formatting but SO's newbies can't post more than 2 hyperlinks in a message was getting in the way of me trying to be helpful and earning enough rep to post more!
(that may only be relevant to IIS 7.x I don't have an IIS6 installation lying around to refresh my memory.
Make sure you are browsing your application on the server using http: //localhost - this should ensure you see any errors
Good luck