how do you know if page is asp or asp dot net

[goodweb171]

how do you know if page is asp or asp dot net ?


is the page ext of dot net generally thepage.aspx

and classic asp just plain thepage.asp ?

 

[JEdge]

ASP.net = .aspx
asp = .asp
php = .php

However some hosts have it in their .htaccess that file extensions are hidden, but there are other ways of scanning and finding out.

 

[DesignerNick]

Will Built With tell you?

I am not sure if it will though, but try it.

 

[DotNetWebs]

ASP.net = .aspx

Unless it's built with ASP.NET MVC and then it is likely to have no extensions at all.

Regards

Dotty

 

[Astaroth]

To know for certain you need to look at the source files.

File extenstion is a reasonable clue but these can be remapped.

You can also look at the HTML code it is outputing and look for a few of the hidden fields that .Net produces as standard but again this doesn't give certainty as these can be manipulated.

 

[DotNetWebs]

..You can also look at the HTML code it is outputing and look for a few of the hidden fields that .Net produces as standard...

Again unless it's MVC

Regards

Dotty

 

[Astaroth]

Again unless it's MVC

Hence the rest of my sentence that you cut off:

but again this doesn't give certainty as these can be manipulated

 

[DotNetWebs]

Hence the rest of my sentence that you cut off:

My response to your quote was correct because those fields are not produced "as standard" in MVC and therefore do not need to be "manipulated".

Regards

Dotty

 

[Astaroth]

They are on the basis that MVC is a framework that is layered over .Net. It is "manipulated" but that is done so by the framework itself rather than what you as the coder create.

 

[DotNetWebs]

They are on the basis that MVC is a framework that is layered over .Net. It is "manipulated" but that is done so by the framework itself rather than what you as the coder create.

So are you trying to say that when an MVC page is requested these fields are created and then somehow 'manipulated' out of view? :|

Regards

Dotty

 

[Astaroth]

No, I am not saying they are "manipulated out of view" but frameworks, like coders themselves, can change how .Net functions to either remove their need full stop, store the data "elsewhere" (eg database or cookies) rather than in the HTML, move their location within the page etc

 

[DotNetWebs]

No, I am not saying they are "manipulated out of view" but frameworks, like coders themselves, can change how .Net functions to either remove their need full stop, store the data "elsewhere" (eg database or cookies) rather than in the HTML, move their location within the page etc

So my initial point was correct - My response to your quote was correct because those fields are not produced "as standard" in MVC and therefore do not need to be "manipulated".

One of the main advantages of MVC is that it does not require all the unnecessary mark up that is inserted into 'classic' .net pages.

An MVC page [markup] may therefore give you no indication as to the origin of the platform behind it.

It's not a case that MVC has manipulated away the 'unnecessary' fields - they never existed in the first place.

Regards

Dotty

 

[Astaroth]

An MVC page [markup] may therefore give you no indication as to the origin of the platform behind it.

As may "classic" .Net but in both cases it is very rare to find someone that has created a complete site in such a way for the fact there is no trace of .Net at all in its outputs.

It's not a case that MVC has manipulated away the 'unnecessary' fields - they never existed in the first place.

Don't particularly want a long debate as it is mainly semantics.

 

[DotNetWebs]

As may "classic" .Net but in both cases it is very rare to find someone that has created a complete site in such a way for the fact there is no trace of .Net at all in its outputs.


Don't particularly want a long debate as it is mainly semantics.

I am happy to debate all day.

You picked me up for cutting off your sentence, that's the only reason I am forcing the issue.

As I said in reply:

My response to your quote was correct because those fields are not produced "as standard" in MVC and therefore do not need to be "manipulated".

It's nothing to do with 'semantic's - those fields do do exist in MVC, period.

Regards

Dotty

 

[stugster]

Guys, you're arguing over semantics.

 

[DotNetWebs]

... semantics.

There's the word again...

The two 'hidden' fields that are normally present on a 'classic' asp.net page are "__VIEWSTATE" and "__EVENTVALIDATION"

ASP.NET MVC does not create these fields. They are not present anywhere in the Application Execution Process. They are not 'manipulated' they simply do not exist.

The statement made was

It is "manipulated" but that is done so by the framework

Which is just wrong. Nothing 'semantic' about it.

Regards

Dotty

 

[stugster]

It's nothing to do with 'semantic's

Guys, you're arguing over semantics.

The message you have entered is too short. Please lengthen your message to at least 10 characters.

 

[DotNetWebs]

.

lol OK fair cop!

Regards

Dotty

 

[Cohesive Computing]

how do you know if page is asp or asp dot net ?

::

You could try using something like Fiddler and inspect the response. You should get something like 'X-AspNet-Version: nnnn' if using asp.net.

 

[DotNetWebs]

You could try using something like Fiddler and inspect the response...

Fiddler is a great tool. I make much use of it for debugging AJAX and Web Services etc.

Regards

Dotty

 

[stylistichosting]

There is not definitive way to see what a website is page up of without having the source files. You can do all sorts of trickery with htaccess that can change the look of the extension or even remove it all together.

However, as stated above .ASPX is usually the extension for ASP.Net