ASP & ASP.NET conflict

[lvlk]

Here's an interesting quirk I just discovered with a domain setup in Plesk:

In the Domain --> Setup, there are two check boxes for ASP support, one "ASP" and the other "ASP.NET". I have noticed that these should in fact be RADIO buttons.

Setting only ASP: asp file are ok, but aspx files will obviously not run.

Setting ASP & ASP.NET: only aspx files seem to execute. old school ASP files don't want to run.

Setting only ASP.NET: same as above.

Thought I'ld point that out. Not a big deal, since you can just add an "x" to a regular asp file and it'll be fine, or even rename .html files to .aspx (but why would ya want that?).

[charles]

Thanks for pointing this out. If they don't have this fixed in 7.5 I'll report it to SWSoft.

charles

[lmnop]

Hello,

It hasn't been solved?
Now on Plesk 7.5 could a user use ASP and ASP.net codes at a same time on a domain?

Regards

[charles]

Can someone who has plesk 7.5.3 please try this and let us know?

As far as I can tell from the description above it works fine as long as you name the files .aspx both will work.

charles

[Soul]

From my experience with iis, asp, and asp.net, IIS will properly support .asp files and .aspx files. The asp files will get parsed with the asp handler and the aspx files will be parsed with the asp.net handler. You do not have to rename any files from asp to aspx. These are different engines and a page written for asp may not work correctly in aspx. In general renaming a page from asp to aspx may cause it to work but some of the objects that maybe in a an asp file have been reworked into different objects in asp.net. Thus some minor updating could be required. I would test it on my plesk system but as I didnt say I was still using it, it has been reassigned to someone else. Too busy to really do any testing.

On a side note I would love for you guys to get this into production :D I am waiting for it before I start offering a new service that is built on an asp.net platform.

[charles]

Ok, we'll need someone who wants this to work to step up and try it then. Or if you have a couple test files to offer that will show that .asp is working for asp and .aspx are working for asp.net properly, we can try it.

We will be announcing the intention to go live with this August 1st **IFF** we find it is stable all of July. So if all goes well, the beta test will end August 1st. If not, we will extend as long as necessary. Just FYI, SWSoft has already made the product GA.

hth
charles

[Soul]

Create two files. asptest.aspx and asptest.asp

Place the following code into both the files

<%
dim x as string
for each x in Request.ServerVariables
response.write(x & "=" & Request.ServerVariables(x) & "<br />")
next
%>

The asptest.asp file should not run. It should generate an error on the "dim x as string" statement. If you delete that line from the asptest.asp file it should then run correctly. If your asp files are getting processed by the aspx handler then it will run correctly. But it should not. They should get processed by the asp handlerer (IMO).

[charles]

Ok, this works as you described

http://204.157.7.58/$sitepreview/test123.com/test.asp <-- no dim
http://204.157.7.58/$sitepreview/test123.com/test.aspx

How about an example to show when/if the asp files are being handled by the aspx handler instead? This seems to be what we want to prove correct?

charles

[Soul]

If you had to take out the dim statement then asp files are handled by the asp handler as they should be. They are not suppose to be handled by the asp.net handler. If they work when you have both the asp and asp.net checked then there is no problem with the vps. Thats my opinion.

EDIT: The original poster said that when the asp and asp.net options were checked the vps would still not deliver the asp files correctly. That you could rename then to aspx. Just renaming is not the recommanded path. You would need to possibly CONVERT your asp files into aspx format. Some might take more updating than others. Some may take no updating at all. If the vps will serve asp pages as is and aspx pages as is, when the asp and asp.net options are selected at the same time, then it IS working as intended, as it should have worked in option 2 of the original poster. Asp.net handler will not handle the asp pages.

http://aspnet.4guysfromrolla.com/articles/011404-1.aspx

The picture in the above article shows asp pages being handled by asp.dll

This is how it will work.

[charles]

Thanks!

There we have it then, it works as expected! :)

charles

[Soul]

Thanks!

There we have it then, it works as expected! :)

charles

How about a job where I work remotely? :D

EDIT:
I also have about 8 years experience in some for or another of VB, so I can also write windows executable code very easily :)

[charles]

We dont need any windows coders, but if you have experience doing support in a windows based hosting environment, please send us your resume to jobs@defenderhosting.com

thanks
charles