Deployment of web application with MailBee.NET.dll

To successfully deploy MailBee.NET based web application, you should follow the next steps:

MailBee.NET based web application requires MailBee.NET.dll. If MailBee.NET.dll is installed on the server using MailBee.NET Objects installer, you do not need to place MailBee.NET.dll in your web application folder, since MailBee.NET.dll is already installed in the GAC. Otherwise, you should check whether MailBee.NET.dll file exists in /bin folder under the root folder of your web application. If there is no MailBee.NET.dll file in /bin folder, you should manually upload it there.

Make sure your application directory is a virtual directory for Internet Information Services (IIS). To create the virtual directory in IIS, follow these steps:

1. Start Internet Services Manager.

2. Expand the server name.

3. In the left pane, right-click Default Web Site, point to New, and then click Virtual Directory.

4. On the initial dialog of the Virtual Directory Creation Wizard, type an alias or name for the virtual directory (such as MyWebData), and then click Next.

5. Then, click Browse. Locate the physical folder you want to create the virtual folder for. Click Next.

6. Now, make sure Read and Run scripts (such as ASP) checkbox is checked, and other checkboxes are cleared. Click Finish to complete the wizard.

7. Right-click the newly created virtual directory, and then click Properties.

8. On the Virtual Directory tab, make sure that the virtual directory name is listed in the Application Name box under Application Settings. If it is not, click Create.

9. Close the Properties dialog box.

The application security may need to be adjusted as well. If you're using SSL, S/MIME, or Windows Integrated Authentication features of MailBee.NET Objects, ASP.NET Trust Level should be set to Full because these features require access to the functions of the operating system.

By default, trustLevel parameter in machine.config file (located in %windir%\Microsoft.NET\Framework\{version}\CONFIG) is set to Full, as shown below:

  <location allowOverride="true">
	<system.web">
	  <!--  level="[Full|High|Medium|Low|Minimal]" --">
	  <trust level="Full" originUrl="" /">
	</system.web">
  </location">

Settings in Machine.config apply machine-level defaults for the server. If for some reasons ASP.NET Trust Level is not Full, developers can override aspects of machine policy in application-configuration files. For ASP.NET Web applications, it's a Web.config file (located in the application virtual root directory and optionally in subfolders of the virtual root).

Note: Overriding settings will work only if allowOverride parameter of tag is true.

If changing the entire trust level is not an option, you can manually set permissions for running native code in order to enable running functions of the operating system. See .NET Framework documentation for more information.