There is a very simple solution to this problem in order to enhance the effectiveness of ASP.NET Hosting UK. All you have to do is copy and paste the codes mentioned below to your page load event of your code that is present behind the master page file. You may have to copy it to every page in case you are not using the master page.

If you incorporate the code mentioned above, it will become possible for you to access the main menu control in the Google Chrome and Apple Safari browsers; this will enable higher efficiency of ASP.NET Hosting UK.

Insert the meta tags mentioned below into your page (notice the id and runat attribute):

In case you are using a master page, set up a ContentPlaceHolder within the master page as shown below:

Therefore in case you are using a master page, this is how your meta tags should look:

Now in the Page_Load sub of your .vb page, enter the code mentioned below:

If you have taken the meta tags from a database, the process mentioned below might help you out. However it maybe different for the type of meta tags used by you:

The way in which Windows Workflow communicates with ASP.NET

All the aspects of a Workflow are activities. An activity connects and communicates with the outside world through a Workflow Service. The activity intimates the service about its requirements. For instance, it might ask a service the details regarding the user’s name and email address, after which it response is awaited. The ASP.NET code responds to all the events fired from this service, this process redirects the user to an appropriate web page that includes the input fields for the name and address. When the user enters the appropriate information; the data is submitted back to the server. ASP.NET fires an event that intimates the Workflow service that a response is available. In this situation, the relevant data is stored in a simple dictionary and is passed between Windows Workflow, ASP.NET and the service layer in serialized format.

Let us have a look at the service layer first, as the code involved in it requires most work.

The Service Layer

The Workflow activities communicate with things outside the Workflow with the use of Workflow Services. A Workflow service is described by its interface. In this case, an interface is required that involves with one method and one event. The Workflow activities will connect with the interface method to request data, and subscribe to the interface event in order to know when data has been received.

Here’s an IGenericInformationService interface that resembles to a Workflow service. This interface provides most of the factors that are required by the Workflow for operating smoothly.

[ExternalDataExchange]
   public interface IGenericInformationService
   {
      string InformationName
      { get; set; }
   
      event EventHandler 
         InformationReceived;
   
      void RequestInformation( string informationName );
   }

The preceding interface is comprised of one event, one property and one method, that makes it a very simple yet efficient service that includes everything required to request and receive information. However you must note that this interface is used solely by the Workflow, the Workflow is not really aware about what happens within the implemented version of the RequestInformation method or what code fires the InformationReceived event.

It is important to supply an implementation of the above mentioned interface. In addition to the implementation of IGenericInformationService, the GenericInformationService class also adds another event, InformationRequested and another method called SubmitInformation. In this case, both Windows workflow and the ASP.NET code will use this class; the Workflow will call RequestInformation and then it will wait for the InformationReceived event. ASP.NET will also wait for the InformationRequested event and will call SubmitInformation when the user has filled in the information.

It is important to note that the InformationReceived event uses a GenericInformationEventArgs class, defined as:

[Serializable]
   public class GenericInformationEventArgs
      : ExternalDataEventArgs
   {
      Dictionary _propertyBag;
   
      public Dictionary PropertyBag
      {
         get { return _propertyBag; }
         set { _propertyBag = value; }
      }
   
      public GenericInformationEventArgs( Guid instanceId, 
         Dictionary propertyBag )
         : base( instanceId )
      {
         _propertyBag = propertyBag;
      }
   }

GenericInformationEventArgs is a simple class that exposes a property bag or Dictionary and extends the ExternalDataEventArgs class defined in System, Workflow, Activities.

The Workflow Side

Everything in a Workflow is based on activities. In order to control the page flow with Workforce it is possible to create activities that ask for information, activities that perform some logic based upon the returned data and activities that wait for data. The activities use a Workflow service to request and receive data. The Workflow navigates with an existing service called the ExternalDataExchangeService. This also contains other services, and one of them will be GenericInformationService described in the previous section.

The ASP.NET Side

The ASP.NET application will make the use of GenericInformationService to wait for an event (the InformationRequested event). This signifies that the Windows workforce is requesting information. On the basis of the InformationName, it will decide about the page that is to be displayed to the user. When the user has filled the appropriate information in the appropriate page, the information will be submitted back to the service through the SubmitInformation method.

Step 1:- You have to Login to your server with the help of Remote Desktop Publishing
Step 2:- Run the command line argumnet on the server
Step 3:- Make the necessary cd %plesk_bin%\mysql\bin
Step 4:- Add mysql -uadmin -psetup -P8306 psa;
Step 5:- You have to update the entire misc set val=”" where param =”mssql_data_source”;

To configure PEAR bundled with php you need to follow the steps below:

1. First of all the administrator has to edit the file named as “pws-php4cgi.reg” and “pws-php4isapi.reg” file which is located in %plesk_dir%\Additional\Php\sapi in the notepad according to the installation paths (substitute ‘[PATH HERE]‘ with the real ones)

2. Execute “%plesk_dir%\Additional\Php\go-pear.bat” and follow the on-screen instructions.

3. Include the path to the newly created pear.bat file into the ‘PATH’ system variable after installation and reboot the machine for changes to take effect.

You can add wizard => click add to add the IP filter => click next => check the check box mirrored, match packets with exact opposite source and destination address.  Select the source address as My IP Address  and add the destination address as a specific IP address(The IP address which you want to block on any of your hosting server, Any IP address(Will block all the IP addresses) , a subnet of IP. Address or a DNS name => Click next => Select protocol Type as Any and finish the IP filter wizard .

Now as you  select the IP filter which you have set and click the next for the filter action =>check the checkbox use add wizard => Click add => Click next and type the filter action name and Description => Click next => Select the ‘BLOCK’ action and click next => Click finish. Now select the filter action and click next and finish and click ok. To apply the policy right click on the policy Name and select Assign.

Now if you want to block a particular port such as 1433 which is MSSQL Port or any other port such as 21 (FTP) , 23(Telnet) , 3389(RDP) ,110 (POP3) please follow the steps described below.

Right click IP security policy which you have created from the above steps =>click properties => Select the IP security policy and click edit => Under the IP Filter list tab select IP filter => Edit => Add a new Filter =>Click next =>

Check the check box mirrored , Match packets with the exact opposite source and destination addresses Click next and type source address as My IP address as well as destination address as any IP address or a specific IP address or a specific subnet you can  go to next step => select a protocol type as TCP => select from this port and type the port number which you want to block and then select to any port => click next => Click Finish . You are done with all the procedure .

Type a mailbox name in the E-mail Address box and select a domain from the drop-down box.
Type password for the new mail account.
Limit the amount of disk space that this mailbox can use. To do this, in Mailbox Size limit box enter the size option
Fill in your personal information.
You can enable an Autoresponder for this email account and set Mail Forwarding from the next available options.
Click Save and your Mailbox is ready.

Go to Domains, click the Domain Name.
In the Web Site group click DNS Settings
Now in the record type column, locate MX record, and click the respective link in the Host column on the left.
Next, in the enter mail exchanger box, type the external mail server’s name and click OK.
Click Up Level to return to the Domain Management screen.
Now click Mail Accounts and Mail Settings.
Clear the Activate mail service on domain check box and click OK.

Your domain will now use an external mail server.

Now input a Username and password into the respective fields.
Click on the Home Folder box. This will bring up a pop up menu from where you can select the folder that the FTP account will have access to.
Make sure “Read” and “Write” are selected under Access Rights Options.
Now click Save and your FTP account is ready.

Next, click on Front Page Tab.
Type the name and password of FrontPage account in the FrontPage Account and FrontPage Password boxes.
Click Install button.
FrontPage status will now be changed to Installed.