Application pools are essentially URLS served by the same (group of) worker process(es). They set up boundaries between applications, which means an application running in an application pool cannot affect one that’s running in another. Also, a failure of an application won’t affect the apps hosted in other application pools. The third benefit of application pools is that you can achieve better performance by using them.
There are some guidelines you should be aware of when designing application pools:
- Create a unique application pool for each web site in a given server.
- Configure a unique user account with the least possible rights for each application pool.
- If you want to run an application with its unique properties, create its own application pool.
Also, you should not add applications that using different versions of the .NET Framework for the same application pool. It may cause errors.
There are four types of ASP.NET websites:
File-system based site:
- Benefits: testability in IIS environment, site is accessible from other computers
- Disadvantages: demands administrative rights, can be debugged only by one user
- Benefits: security, no IIS needed, no administrative rights needed, multiple users can debug it at the same time
- Disadvantages: cannot be tested in IIS environment
- Pros: site can be tested on the server where it will be used
- Cons: site exists only in the server; this project type cannot be created, only opened.
- Pros: testability, access for multiple developers
- Cons: debugging issues.
Hello, as I promised, here is a brief note about Windows Authentication in ASP.NET. I omitted the too advanced tools, which won’t be needed for this exam.
There are four types of authentication in ASP.NET:
– Windows authentication
– Forms authentication (used by the membership API)
– Passport authentication (mostly obsolete, consider Windows Live instead)
– Anonymous access
Use it when:
– Dealing with a smaller set of known users.
– Who have Windows user accounts.
– Potentially in intranet applications.
Windows authentication matches web users to the predefined Windows users (local or Active Directory). WA isn’t a built in feature of ASP.NET, IIS handles everything. To configure it, set authentication mode to Windows in the web.config.
I’m continuing the struggle with Silverlight, and I’d like to share my probably worst experience with you. I’d wanted to make a data-driven app in Silverlight recently, but it took a complete day. All I wanted was the binding of a MS SQL table to a Silverlight DataGrid. Because SL doesn’t support System.Data (which made me cry at the first place), I needed a workaround for this one. Then I found the template Silverlight-enabled WCF service, and it was love in the first sight, I thought. To bind a table (one-way binding, of course) in Silverlight is relatively easy. Create a service, set a reference on it, set it as the ItemSource property of the DataGrid. In code:
WebServiceSoapClient client = new WebServiceSoapClient();
client.GetCustomersCompleted += new EventHandler<GetCustomersCompletedEventArgs>(client_CustomersCompleted);
void client_CustomersCompleted(object sender, GetCustomersCompletedEventArgs e)
dataGrid1.ItemsSource = e.Result;
Easy as that.