J
JezB
I kind of understand the ASP.NET architecture in terms of building web pages
with embedded server controls, where the .aspx is run on the client and the
..aspx.cs runs on the server.
But what if I want to build an ASP.NET based application that is to be run
entirely on a client (all files hosted on the client and run on the same
client)? What would that client need to run it?
I want to write an application that can be run standalone on a PC (not
hosted on a web server and accessed from a PC), which uses web technology
like javascript and Ajax, while also being able to code the primary logic in
C#. I have the choice of a windows forms rich client application which uses
a WebBrowser control, or a native ASP.NET application. But I'm not sure the
latter is even feasible for being deployed and run standalone on a PC -
would it need IIS and .NET framework installed, and even more?
with embedded server controls, where the .aspx is run on the client and the
..aspx.cs runs on the server.
But what if I want to build an ASP.NET based application that is to be run
entirely on a client (all files hosted on the client and run on the same
client)? What would that client need to run it?
I want to write an application that can be run standalone on a PC (not
hosted on a web server and accessed from a PC), which uses web technology
like javascript and Ajax, while also being able to code the primary logic in
C#. I have the choice of a windows forms rich client application which uses
a WebBrowser control, or a native ASP.NET application. But I'm not sure the
latter is even feasible for being deployed and run standalone on a PC -
would it need IIS and .NET framework installed, and even more?