This one requires a lot of subjectivity.
I need to upgrade an app from "proof of concept" to "pilot". I wrote the site (45K lines of vb, 10K lines of JS); someone else will upgrade it, then I'll need to continue maintaining it.
I need to make a decision about converting from asp.net web site (which it is now) to asp.net web application.
> I've read a lot about the differences between asp.net web sites and web applications, in terms of sub-projects, standalone classes, compilation, edit-and-continue, deployment, working in teams, etc.
> I'm sensitive to the added cost of converting to a web application, unless there's a good reason (though the rewrite team may greatly prefer converting).
> I think I can deal with learning the compilation and deployment differences.
> I'm mostly concerned about added coding complexity in web applications vs web sites.
On balance, the main advantage of converting in this case seems to be having sub-projects and standalone classes, so that a) I can have some application admin functions that use the same code as the main project but that don't have to be deployed and b) I can have some added flexibility in how the workflow would operate (i.e. functions not requiring other functions to be "up"; but "b" is really a business benefit that I might be able to live without).
Also, with respect to a) above, as a web-site, I could compile the app admin functions in with the rest and not deploy the app admin forms
==> First question: maybe that's an additional security risk, however, much the same object code would be in the bin anyway. Any thoughts on the security issue there?
So, am I just being a big softie about coding differences between web sites and web applications? Are Namespaces not that big a deal? Are there other coding complexities in web applications vs web sites that go beyond Namespaces? Or, once I got past Namespaces would I basically stop noticing any differences?
Any thoughts on these questions in particular and this entire situation in general would be appreciated.