If I were you I would see what could be salvaged. Can you rescue a bunch of business objects, data access code, etc.?
If the code was written in a half-way competent manner, it shouldn't be too tightly coupled to ASP.NET.
If there is a substantial amount of boilerplate code already written that you don't have to rewrite, I would suggest not rewriting it.
I too would like to know what you are considering for the server-side end of things.
The nice thing about ASP.NET is you can strip it down to the absolute basics. Remember that you have complete access to the request/response model. You don't have to render HTML at all. You can deal entirely in JSON if you are looking to build this into an API.
You don't necessarily need to rewrite all the components. If it's possible, hammer and chisel the existing code into something that's not so dependent on ASP.NET (e.g. move code out of .aspx/.ascx components). You can build a web app and an API at the same time, especially if you treat ASP.NET simply as a presentation layer.
If the code was written in a half-way competent manner, it shouldn't be too tightly coupled to ASP.NET.
If there is a substantial amount of boilerplate code already written that you don't have to rewrite, I would suggest not rewriting it.
I too would like to know what you are considering for the server-side end of things.
The nice thing about ASP.NET is you can strip it down to the absolute basics. Remember that you have complete access to the request/response model. You don't have to render HTML at all. You can deal entirely in JSON if you are looking to build this into an API.
You don't necessarily need to rewrite all the components. If it's possible, hammer and chisel the existing code into something that's not so dependent on ASP.NET (e.g. move code out of .aspx/.ascx components). You can build a web app and an API at the same time, especially if you treat ASP.NET simply as a presentation layer.