My website was designed without any backend in mind. Facebox was the chosen plugin for the screen pops for features like logging in, registering, searching, etc. What is the easiest way to convert this to .NET? I don't care if it's web forms or MVC (I suppose I would prefer MVC). Most of the Facebox div's are in separate .html files. For example, the register feature has a separate .html file with only the div's for the screen pops (and some script for the relative elements). This would loosely translate to a partial view in my mind, but I don't really care--I just need it to postback so I can handle the form in a controller or codebehind file, and I can't seem to make it work.
Some areas of concern:
- No files currently have page directives (what should they look like if converted?)
- The "child" pages currently start with
<script>...</script><div>...</div>(how do I handle these? separate .aspx page or partial view or something else?) - Does everything really have to be "converted" to .aspx?
- Where does any jQuery go? Some functions seem to be "undefined" when located in a "child" page. When I move them to the parent page, a form element then won't be able to find the jQuery.validate
.valid()function
These are just some examples of problems I've been having.
Even if I have to convert each page to .aspx by hand, I just need to know what I'm missing.