How do application pages compare to ASP.NET web forms?

Question

We are considering moving from an ASP.NET Web forms model to SharePoint 2010 Application Pages. The main reason for this is so we can utilise the SharePoint Foundation solutions framework rather than maintaining Web forms separately.

The reason we have used Web forms in the past are as follows:

1. Integration with third party components (such as K2 Blackpearl) via .NET libraries.
2. Process isolation from SharePoint content application pools.
3. Capability to connect to custom databases (we have used SQL authentication but are looking to move away from that approach for security reasons).

My two queries around this are:

1. Are there any limitations around third party libraries that can be utilised in Application Pages?
2. Does SharePoint offer any capabilities to ensure that our Application Pages won't impact application pool availability?

I have looked around for an explanation of the limitations and benefits associated with Application Pages, but have only found comparisons with Site Pages.

Answer 1

As far as I know:

1. Only the normal ones for an ASP.NET application - e.g. Framework version, CAS policy, etc..
2. Yes... but it's the application pool itself! If you want to isolate your code, you're looking at having to put it into it's own application pool. There's no reason not to do that - it's a configuration I use sometimes with custom code that is 'risky' - though obviously there's an overhead to it.