G
Guest
I have a ASP.NET app that my users would like to be able to access remotely
while out of the office (i.e. where they will have no internet connection).
Rather than rewrite the whole thing as a traditional windows forms app, I'd
like to deploy the actual web project.
All my users have good laptops, and I've been able to install MSDE and IIS
on them, deploy the project, and everything runs fine. Only one person will
ever hit the localized IIS at one point in time, and performance is
acceptable (but not as good as I'd like).
My question is, is there a better way to deploy a ASP.NET web project in a
scenario like this without using IIS? We're a small shop (2 developers) and
the bulk of our time will always be spent working on the "main server"
website, we'll probably never have time to write and maintain a second UI,
even though the bulk of our logic is in class files.
while out of the office (i.e. where they will have no internet connection).
Rather than rewrite the whole thing as a traditional windows forms app, I'd
like to deploy the actual web project.
All my users have good laptops, and I've been able to install MSDE and IIS
on them, deploy the project, and everything runs fine. Only one person will
ever hit the localized IIS at one point in time, and performance is
acceptable (but not as good as I'd like).
My question is, is there a better way to deploy a ASP.NET web project in a
scenario like this without using IIS? We're a small shop (2 developers) and
the bulk of our time will always be spent working on the "main server"
website, we'll probably never have time to write and maintain a second UI,
even though the bulk of our logic is in class files.