Whenever we create a new “Web Application” in SharePoint few things are created in background. What I mean to say that creation/provisioning of a web application leads to creation of a few things in background
- An IIS Site
- A content database
- A virtual directory
Today, I am going to focus on the “virtual directory” and it’s significance.
“Virtual Directory” is just a container of files. It’s just a logical way to organize your web-site and physical directories . Typically the virtual directory for SharePoint web application is created at the following location
If you have a look at this directory it typically has the following files and folders. Let’s have a look at each of them and their significance
||The _app_bin folder was designed to hold application assemblies which were previously installed in _layouts/bin. Web Part assemblies are *not* supposed to be installed in this folder. Put your assemblies in GAC or the bin, but not the _app_bin.
||This folder is used by FrontPage Extensions/SharePoint Designer. It contains Legacy FrontPage Server Extensions files/folders. The reason for having these folders is that they provide the underlying infrastructure files for the many features SharePoint Designer provides.
||Contains compiled assemblies (.dll files) for controls, components, or other code that you want to reference in your application. Any classes represented by code in the Bin folder are automatically referenced in your application.
||Contains browser definitions (.browser files) that ASP.NET uses to identify individual browsers and determine their capabilities.
||Contains resources (.resx and .resources files) that are compiled into assemblies with global scope. Resources in the App_GlobalResources folder are strongly typed and can be accessed programmatically.
||Contains configuration file for Web Parts
||The Global.asax file, also known as the ASP.NET application file, is an optional file that contains code for responding to application-level events raised by ASP.NET or by HttpModules.
||The Web.config file is the primary configuration file having all the configuration details for the web application (IIS site)