How to "execute" aspx file in OWN server?

Question

0.00/5 (No votes)

See more:

Hi,

I have my own server written in C#, but it can't "execute"(hope it's the correct word :) ) .aspx.

When I visit aspx page, it gives:

http://i.stack.imgur.com/iUcR0.jpg[^]

But it's supposed to return this:

http://i.stack.imgur.com/dWndH.jpg[^]

I'm out of ideas...what should I do. Must server "re-render" the page? Or is it even possible to run aspx pages in other servers? or aspx only for IIS?

Posted 3-Aug-13 13:45pm

atunahkur

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Ron Beyer · Accepted Answer · 2013-08-03T13:49:00

Can you do it? Maybe, but its a LOT of work. You have to write your own script interpreter, to intercept the page and interpret the values in the ASPX before you send the data to the client.

What your server does is just sends the raw page to the client, which is pretty basic. You would have to expand on that when the page is requested to read the page on the server side first, then run the scripts on the page, and then send the rendered data to the client. Prepare to spend significant (year+) time on that. You have to get into state management, hosting the .NET runtime, etc.