Archive for the ‘Web Development’

Huge organizations have many people working in the same organization in different regions across the globe having different languages for communication. In general scenario regional language is more in to preference. As internet facilities are now easily available, websites are the most favorable and less expensive equipment for marketing purpose. Websites should be capable enough to provide content suitable to their target audiences across the globe. But maintaining the different sites with different languages is very difficult for content redundancy point of view.

According to Microsoft, many fortune 500 Companies are using SharePoint for public facing sites and as intranet sites to manage their businesses. They have many offices in different regions of the world. These types of company’s needs websites that deliver customized content, to suit different cultures and different markets. It is very tedious and time-consuming task to maintain and manage data with different languages. They have to make sure that data must be redundant. Therefore, Microsoft SharePoint has provided below approaches to manage multi-lingual sites:

1. Install different language packs in SharePoint server: We can install different language packs in a SharePoint environment to support more than one language. But this will only affect the site administration pages and user interface but does not affect content created on site.
2. Use the variations feature to make publishing content available in different languages on different sites: Different sites will be created for different languages and content will be sync between these sites. Unlike the first option, this feature does not affect the administration pages and user interface, only affects the content.

   Today, we will discuss for SharePoint variation features to manage content in multi-lingual sites. Points are insight by the team of SharePoint developers taking into considerations the real-time scenarios faced while the development phases and client requirements.

   We can use SharePoint variation feature to support multi-lingual sites in SharePoint server and SharePoint Online. Using Variation feature in SharePoint development, site administrators can simplify the process of maintaining these sites with different languages. It automates the creation, synchronization, and translation of sites, lists, and pages in SharePoint sites.

   When the user visits the root site, they are redirected to the appropriate variation site according to language settings in their browser settings. Variations can be utilized only on sites that are built by utilizing one of the Publishing site templates, or on sites for which the SharePoint Server Publishing Infrastructure feature was initiated.

Scenarios for using variations

We can manage variations to build and design sites, lists, and page content for specific linguistics. For example, the content might be accessible in English and be synced to target variation sites for translation into other languages say for example Arabic, German, French, and Spanish.

We can also use variations to create content for specific locales. For example, the Arabic language might have target variation sites for the following locales: Arabic (Egypt), Arabic (Qatar), Arabic (Saudi Arabia) etc. While SharePoint consulting, this is the general scenario commonly we came across with the clients.

The largest part of the content is authored in English (United States) in the general scenario, and the variation feature syncs that available content to the target variation sites.

Content on the French (Canada) and Dutch (Mexico) site are translated into French and Dutch, whereas content for English is edited to account for regional differences in Egypt and Qatar Arabic. Other content that is individual to a specific region is built on the target variation sites for which it is required.

In SharePoint 2010, we are using variations to create sites in different mobile devices, or that used different branding. In SharePoint 2016 based application development, variations are used only for multilingual sites. To create sites for different mobile devices in SharePoint 2016, we can use Device Channels. To create sites with different branding, we can use cross-site publishing.

Elements used in Variation features

The variations feature consists of the following elements:

1. Variation Root Site: The variation root site is the source site of all the variation. Root site provides the URL for all source and target variation site and landing page URL to redirect in a specific variation site. Note: Variation root site is not the same as site collection root site, but we can set the site collection root site as a root site of variation hierarchy.
2. Variation labels: A variation label is an identifier of a new variation site. We can create a variation site by creating/configuring the Variation label. Note: SharePoint Server supports up to 209 variation labels. SharePoint Online supports up to 50 variation labels.
3.  Variations hierarchy: This is a hierarchy of all the Variations site with all variation label.
4. Variation lists: Variation lists are lists where we specifically target variation labels to receive/sync list items.
5. Variation pages: Variation pages are the publishing pages that are stored in the Pages library of the source variation site and the target variation sites. Important: Recommended that we do not add non-publishing pages to the Pages library of a site that uses variations. If we do that, the Variations Create Hierarchies Job Definition timer job might fail.
6. Variation sites: Variation sites are the sites that are created based on the variation labels. There are two types of variation sites:
   1. Source variation site:The source variation site is the site where shared content is available and published, and it is the site from where the shared content is synced with target variation sites. There is only one source variation site per one site collection. Once we created a source variation site, it cannot be changed later.
   2. Target variation sites:The target variation sites receive/synced most of their content from the source variation site. We can add/update new content on a target variation site. However, that content is not synced with other sites and is individual to the site on which it was built.

Let’s start by configuring variation feature in SharePoint server:

Here, I have used SharePoint 2013 enterprise server for illustration purpose.

Variation Feature Prerequisites

SharePoint Variation feature requires below prerequisites:.

1. Install required language packs on SharePoint server.
2. Configure Machine Translation service and make sure it is started in SharePoint Central Administration under “Application Management”.

   Manage services on server:

   

   Manage service applications:

   

3. Require SharePoint site created using “Publishing” site template or site with “SharePoint Server Publishing feature” features activated.

Configure Variations Settings

To Configure/Setup Variation in SharePoint site follow below settings:

1. Go to Site Settings.
2. Under “Site Collection Administration”, we can see the below variations settings are available:
   • Variations Settings
   • Variation labels
   • Variation logs
   • Translatable columns

   

3. Go to Variations Settings.
4. Here we have below self-explanatory settings are available, we can change these settings as per our requirements, else we can put these settings as it is.
   • Create Everywhere (Default): This option will propagate any content created in source label to all target variations.  Sync will happen automatically.
   • Create Selectively: This option will allow us to sync content to some but not for all target site. Variation should be triggered manually.
   • Recreate Deleted Target Page: This option will allow us to choose, whether a new target page should be recreated when the source page is republished, if the previous target page has been deleted.
   • Update Target Page Web Parts: This option will allow us to choose, whether Web Part changes from source page should be updated to existing target pages or not.  Note: Web Parts personalization will be lost when the update is made.
   • Notification: This option allows us to send an e-mail to the contact person of the welcome page of the target site when a new sub site or page is built, or the contact person of a page when a target page is refreshed with updates and alternatives from the source variation.

Create Variation Source Label

To create source variations site/label from where the content should be variant to the target site, follow the below steps:

1. Go to Site Settings >Variation labelsNote: The very first variation label which we are creating will be the “Source Variation” site.
2. Click on New Label.
3. Let’s create English as a source site.
   • Language: This setting defines SharePoint User interface elements of the variation site. Options look on the site template language drop-down depends on the language sets installed.
   • Locale: Locale determines the language site based on our browser settings. Automatically it redirects the browser from Variation home to target variation site. Locale helps in creating content in different languages.
   • Variation Home: Location where the source and target variations will be created.
   • Label Name and Description: This name will be used to create the variation site and will appear in the URL. The name cannot be changed once the label is created.
   • Display Name: User-friendly, locale-appropriate name for the variation label.
   • Publishing Site Template: Select the site template that will be used to create top-level source and target variation sites.
   • Label Contact: If email notifications are enabled in variation settings, label contacts will receive emails when this source variation site is created.

   

4. Click on “OK” to create source variation.

Create Variation Target Label(s)

To create target variations site/label, follow the below steps:

1. Go to Site Settings > Variation labels > New Label.
2. Let’s create Arabic as a first target variation site.
3. Select Language and Locale, I have selected Arabic and Arabic (Qatar) respectively. Click on Continue.
4. Enter appropriate variation Label Name, Description and Display Name. Select the portion of the source hierarchy we would like copied, this will be built label’s structure based on the source hierarchy during Hierarchy Creation. Click on Continue.
5. Select appropriate Translation options.
   • Create Translation Package: Enabling human translation on this target will allow users to export content to an XLIFF file. Users may then transfer the file to a translator for professional translation.
   • Machine Translation: Enabling machine translation on this target will allow users to send content online to Microsoft for translation. We may use content users send us to improve the quality of translations.

   

6. Click on Continue.
7. Select appropriate Page Update Behavior from below and label Contact as per the requirements and click on Continue.
   • Users can manually sync updates from source variation pages: If the user doesn’t want to sync content from the source variation to target variation in that this option will be useful. For Example, In Source label pushed the content first time and target label authors translated the content to the target site, then later if user change in the source site but user don’t want to translate the later changes in the target site.
   • Automatically update target variation pages: If the user wants to translate the content automatically when user publish the content in the source site, it will automatically translate the change in the target label.

   

8. Review and Click on Finish to complete target variation label creation.

Create Variation Hierarchy

Once we create a Label for source and target, each label should create a variation sub-site based on the scheduled timer job (i.e., Variations Create Hierarchies Job Definition) for the Variation.

Click on “Create Hierarchies” link from Variation labels page in site settings that will invoke the timer job “Variations Create Hierarchies Job Definition”. This timer job will get executed based on its schedule.

Once the hierarchies created successfully, “Hierarchy is Created” status on Variation Label page will change to “Yes” and sites are created successfully.

SharePoint 2013 Variation Timer Jobs

SharePoint 2013 Variation feature content synchronization is a unidirectional process, it synchronizes content from a source variation site to one or many target variation sites.

To see the Timer Job go to Central administration > Monitoring > Review Job Definitions.

Below are the list of timer jobs involved in variations feature in SharePoint:

• Variations Create Hierarchies Job Definition: Creates all variation sites, lists and pages from the source variation site. It runs hourly.
• Variations Propagate List Items Job Definition: Creates and updates list items on target variation Default, every 15 minutes.
• Variations Propagate Page Job Definition: Creates and updates pages on target variation after approved. Runs every 15 minutes.
• Variations Propagate Sites and List Job Definition: Implements or executes variation sites and lists when the “Create Everywhere” option is enabled.  The process executes every 30 minutes.

Above timer jobs are run automatically at above mentioned time interval.

If user want to run any Timer Job manually for specific requirements, then user can find above timer jobs from Central administration > Monitoring > Review Job Definitions.

Select “Web Application” from the View as shown in below screenshot.

Select our Web Application from Web Application Dropdown.

Click on the appropriate timer job to run it manually.

We can see the Edit Timer Job page, Click on “Run Now” to start the timer job manually.

Variation Logs

During the variation process, there are several timer jobs to execute for the task completion. All activities related to Variation process are logged and collected under Variation logs list to provide details and troubleshooting any variation related issue such as Hierarchy creation, Page propagation, etc.

Variation logs are positioned beneath root site collection’s settings page.

Site Settings > Site Collection Administration > Variation logs

Test Variation Features

Let’s test Variation feature by Syncing Custom list and Libraries in Variation:

1. Create new list and create one item on source English site.
2. Now open the Variations tab from ribbon. And click on “Settings”. Select the target label and click on continue. We will provide “Your new variations are on the way” message. Click on OK.

   



3. This list and list item will be created based on the Timer Job Scheduled. Once Timer Job Run this list will be created on the target Arabic site as shown below:Note: We can also manually run the below Timer jobs from central administration to propagate changes on target site.
   • Variations Propagate Sites and Lists Job Definition
   • Variations Propagate List Items Job Definition

   

Web Parts behavior with Variation features

Web Parts are synced with pages of variation sites. If “Update Target Page Web Parts” is allowed, web Parts are refreshed only on the target variation site if a page that incorporates that web part is synced to the target variation site.

If the web part seems on various target pages on many target variation sites, all instances of the web part are modernized when the page from the source variation site is synchronized to the target variation sites.

For illustration, if a page possesses a Media Web Part, and the web part is configured to point to “Video A” that is stored on a site outside the variations hierarchy when the page is declared on the source variation site, the page is synchronized to all target variation sites. The pages on the target variation sites exhibit “Video A” in the Media Web Part.

If the page on the source variation site is refreshed and the Media Web Part is modified to point to “Video B”, the pages on the target variation sites stretch to point to “Video A” until the page on the source variation site is declared and synchronized to the target variation sites. Also, if readers on the target variation sites do not have permission to view the video file that is stored outside the variations hierarchy, they can’t observe the video.

Limitations

There are few limitations with Variation features in SharePoint Development:

• We can use variation features only with the site(s) created using ‘Publishing site’ or ‘Publishing site with workflow’ templates. It is quite complicated to use feature stapling with OOTB site template for variation sites creation.
• There can be only one root site variation per site collection.
• There is only one way synchronization between the source language and target languages, we can synchronize content from source to target, but we cannot synchronize content from target to source.
• Pages do not get synchronized until they are published. Therefore one version of the page has to be ready in source variation site before the target version of the page can even get translated and worked on.

The scenario to deal with creating files in document libraries, adding/updating/deleting items in the SharePoint list, at times requirement emerges to perform some action on such events like sending notification, data manipulation on SharePoint lists or libraries, etc.

In SharePoint Development, there are two manners to achieve this – SharePoint Designer Workflow and Event Receivers. Of course we can use these techniques to achieve such requirement, but it runs on SharePoint server, i.e. business logic runs on the same server where SharePoint is installed, and event receivers do not support while working with Office 365 – SharePoint online. Few SharePoint programmers while consulting process may pitch to use different approaches like provider hosted-apps.

Cases where the business requirements are to keep business logic and SharePoint server segregated. Fortunately to deal with document libraries/lists on a host web (on which site we install application), it provides concept called Remote Event Receiver.If any list item is added/edited/deleted, and we want to perform any action like sending notification, we can use a remote event receiver.

So, let’s learn how to prepare provider hosted app and remote event receiver. We will host Provider Hosted application in Azure. Below are mentioned the steps to create remote event receiver.

Following are the tools to create remote Event Receiver:

1. Visual Studio 2015
2. SharePoint Online (Office 365)
3. Azure Portal (For Deployment)

Step 1 – To Create Provider Hosted Application

1. Open Visual studio
2. Click on File  New Project.
3. Dialog box will appear. Select Templates then Visual C# then Office/SharePoint.
4. Select “App for SharePoint”, make sure .Net framework 4.5 is selected, for more information review below screen shot and give application “HelloWorldProvider” name.



5. Then choose a SharePoint developer site and then choose Provider-hosted like below. You can see below article to know how we can create a developer site in SharePoint, for more information review below screen shot, for security reasons we have erased URL.



6. Then it will ask to give credentials for the developer site and then select SharePoint Online Version.
7. Then wizard will ask which type of provider application, we want to create either Asp.Net web forms or ASP.Net MVC application. Currently, we will select ASP.Net web forms.
8. On the next screen selection option “Use Windows Azure Access Control Service (for SharePoint cloud apps)”.
9. It will take some time and it will create two projects in one solution, one is for the SharePoint add-in and the other will be ASP.NET web forms project, review below image for more information:



10. We need to attach event receiver to the list of host web (where we install add-in), so to achieve this, select add-in project from the solution and from the properties of the project set “Handle App Installed” to ‘true’:



11. After setting “Handle App Installed” property to true, AppEventReceiver.svc will be added inside the Services folder like below: We are going to write code to attach remote event receiver to host web’s list.

Step 2 – To Add Remote Event Receiver to project

1. Add Remote Event Receiver. Right click on the Add-in project then Add then New Item.



2. Give it name “Validation”.



3. Select List Item Events, event source as Custom List and then event as “An Item was added”, which means some action on the host web’s list will be performed when an item is added in that list.



4. Validation.svc file will be added to add-in project as well as inside the service folder of the asp.net web forms project. Review below image:



Step 3 – To Generate Client ID & Client Secret

1. To establish trust with the provider hosted web, we need to generate the Client ID and Client Secret. So navigate to the _layouts/15/appregnew.aspx page

   Example: https://test.sharepoint.com/sites/devsite/_layouts/15/appregnew.aspx

2. Click on the Generate button for the Client Id and Client Secret fields to generate them respectively. Enter a title and in App Domain put the website that is created in azure (without https). Lastly, enter the Redirect URI which is the website URL, make sure to give in https.

   

3.  Open the web.config file and replace the Client Id and Client Secret which we have generated in the above page. Note: Before modifying the web.config file, take its backup.
4. On AppManifest.xml, Right Click then View Code and add following code:

   <AppPermissionRequests AllowAppOnlyPolicy="false"> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" /> </AppPermissionRequests>

   <AppPermissionRequests AllowAppOnlyPolicy="false"> <AppPermissionRequest Scope="http://sharepoint/content/sitecollection/web" Right="FullControl" /> </AppPermissionRequests>

   Also add client ID same as above

   Step 4 – To Add Code to AppEventReceiver

   In ASP.Net Web forms project inside the service folder’s AppEventReceiver.svc.cs file, we will add the code to attach the event receiver to the host list. The code will be added in the ProcessEvent event for the AppInstalled event.

   public SPRemoteEventResult ProcessEvent(SPRemoteEventProperties properties)   {   try   {   SPRemoteEventResult result = new SPRemoteEventResult();     using (ClientContext clientContext = TokenHelper.CreateAppEventClientContext(properties, useAppWeb: false))   {   if (clientContext != null)   {   clientContext.Load(clientContext.Web);   clientContext.ExecuteQuery();     if (properties.EventType == SPRemoteEventType.AppInstalled)   {   //Get reference to the host web list with name Feedback   var documentsList = clientContext.Web.Lists.GetByTitle("MDLIB");   clientContext.Load(documentsList);   clientContext.ExecuteQuery();   string remoteUrl = "https://customproviderhosted.azurewebsites.net/Services/Validation.svc";   //Create the remote event receiver definition   EventReceiverDefinitionCreationInformation remoteEventReceiver1ItemAdded = new EventReceiverDefinitionCreationInformation()   {   EventType = EventReceiverType.ItemUpdated,   ReceiverAssembly = Assembly.GetExecutingAssembly().FullName,   ReceiverName = "ValidationItemAdded",   ReceiverClass = "Validation",   ReceiverUrl = remoteUrl,   SequenceNumber = 10000,   };     //Add the remote event receiver to the host web list   documentsList.EventReceivers.Add(remoteEventReceiver1ItemAdded);   clientContext.ExecuteQuery();   }   }   }   }   catch (Exception ex) {   SPDiagnosticsService.Local.WriteTrace(0, new SPDiagnosticsCategory("Remote Event Receiver - Error Report", TraceSeverity.High, EventSeverity.ErrorCritical), TraceSeverity.High, ex.Message, string.Empty);   }   return result;   }

   public SPRemoteEventResult ProcessEvent(SPRemoteEventProperties properties) { try { SPRemoteEventResult result = new SPRemoteEventResult(); using (ClientContext clientContext = TokenHelper.CreateAppEventClientContext(properties, useAppWeb: false)) { if (clientContext != null) { clientContext.Load(clientContext.Web); clientContext.ExecuteQuery(); if (properties.EventType == SPRemoteEventType.AppInstalled) { //Get reference to the host web list with name Feedback var documentsList = clientContext.Web.Lists.GetByTitle("MDLIB"); clientContext.Load(documentsList); clientContext.ExecuteQuery(); string remoteUrl = "https://customproviderhosted.azurewebsites.net/Services/Validation.svc"; //Create the remote event receiver definition EventReceiverDefinitionCreationInformation remoteEventReceiver1ItemAdded = new EventReceiverDefinitionCreationInformation() { EventType = EventReceiverType.ItemUpdated, ReceiverAssembly = Assembly.GetExecutingAssembly().FullName, ReceiverName = "ValidationItemAdded", ReceiverClass = "Validation", ReceiverUrl = remoteUrl, SequenceNumber = 10000, }; //Add the remote event receiver to the host web list documentsList.EventReceivers.Add(remoteEventReceiver1ItemAdded); clientContext.ExecuteQuery(); } } } } catch (Exception ex) { SPDiagnosticsService.Local.WriteTrace(0, new SPDiagnosticsCategory("Remote Event Receiver - Error Report", TraceSeverity.High, EventSeverity.ErrorCritical), TraceSeverity.High, ex.Message, string.Empty); } return result; }

   Above code will attach remote event receiver to the list named “MDLIB” which will be in host web (i.e. where provider hosted app is going to be installed).

   Step 5 – To Add Code to Validation Remote Event Receiver

   In ASP.Net web forms project inside the service folder’s Validation.svc.cs file, we will add the code to instruct event receiver to updated description field of ‘MDLIB’ list when item added. The code will be added in the ProcessOneWayEvent event.

   public void ProcessOneWayEvent(SPRemoteEventProperties properties)   {   if (properties.EventType == SPRemoteEventType.ItemAdded)   {   using (ClientContext clientContext = TokenHelper.CreateRemoteEventReceiverClientContext(properties))   {   if (clientContext != null)   {   try   {     List lstDemoeventReceiver = clientContext.Web.Lists.GetByTitle(properties.ItemEventProperties.ListTitle);   ListItem itemDemoventReceiver = lstDemoeventReceiver.GetItemById(properties.ItemEventProperties.ListItemId);     itemDemoventReceiver["Description"] = " updated by remote event reciever =>; " + DateTime.Now.ToString();   itemDemoventReceiver.Update();   clientContext.ExecuteQuery();   }   catch (Exception ex) {   SPDiagnosticsService.Local.WriteTrace(0, new SPDiagnosticsCategory("Remote Event Receiver - Error Report", TraceSeverity.High, EventSeverity.ErrorCritical), TraceSeverity.High, ex.Message, string.Empty);   }   }   }   }   }

   public void ProcessOneWayEvent(SPRemoteEventProperties properties) { if (properties.EventType == SPRemoteEventType.ItemAdded) { using (ClientContext clientContext = TokenHelper.CreateRemoteEventReceiverClientContext(properties)) { if (clientContext != null) { try { List lstDemoeventReceiver = clientContext.Web.Lists.GetByTitle(properties.ItemEventProperties.ListTitle); ListItem itemDemoventReceiver = lstDemoeventReceiver.GetItemById(properties.ItemEventProperties.ListItemId); itemDemoventReceiver["Description"] = " updated by remote event reciever =>; " + DateTime.Now.ToString(); itemDemoventReceiver.Update(); clientContext.ExecuteQuery(); } catch (Exception ex) { SPDiagnosticsService.Local.WriteTrace(0, new SPDiagnosticsCategory("Remote Event Receiver - Error Report", TraceSeverity.High, EventSeverity.ErrorCritical), TraceSeverity.High, ex.Message, string.Empty); } } } } }

   Step 6 – To Deploy Provider Hosted App to Azure

   1. Right click on the asp.net forms web project and then click on Publish.

   

   2. Public web project dialog will appear, click on Microsoft Azure Web Apps.

   

   3. It will ask to login into azure account, it will display all the web apps. Choose the particular web apps like below:

   

   4. Publish method, Server, Site name, User name, Password and Destination URL will be appeared in next screen. Validate the connection and once it is successful.

   

   5. Click on the Next.

   

   6. To verify all the files, you can also click on the Start Preview button to see the preview.

   

   Step 7 – To Publish App Package

   Now asp.net web project is published to azure web portal, now it’s time to prepare package for the SharePoint add-in.

   1. Right-click on the Add-in Project and click on Publish.

   

   2. Publish your app page will appear, then click on the Edit button like below:

   

   3. It will ask Client ID & Client Secret, write down both the same as we replaced into the web.config file.

   

   4. Click on Package App, make sure that it is in release mode.

   

   5. Here the website and Client Id will be populated by default. Click on Finish button which will generate the .app

   

   6. It will open folder with package file (.app file).
   7. Open App Catalog site, go to Site Contents à Apps for SharePoint à Upload the .app file

   Reference Sites:

   1. App Catalog Site – https://docs.microsoft.com/en-us/sharepoint/use-app-catalog
   2. Create developer site – https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/create-a-developer-site-on-an-existing-office-365-subscription

   Step 8 – To Test Remote Event Receiver

   1. Go to site content of the developer site, and add an application.
   2. After the app is installed successfully, open the list and add an item to the list. Enter only Title and the Description will be added automatically by the remote event receiver like as shown below:

   .

   

   Conclusion

   For the challenges part, there are few of them if the development is done using SharePoint Designer Workflow, but for Provider Hosted app it is way easier and safer as the business logic is not disclosed openly because it is hosted on separate individual server. Though details of each log can’t be maintained on the server as it is an individual server, yet the process is more streamlined and robust.

The .NET framework powers numerous enterprise applications worldwide, like government, transit, hospital systems, flow of worldwide news and media and many other. If one’s focus is reliability and flexibility, then Microsoft’s .NET would give a site, product or application the portability desired. Most organizations and businesses, across the board, still are heavy users of Microsoft .NET Framework as a basis for most web-based software solution.

When it comes to using a technology, a software or a web application, most of the business owners are concerned about the increasing the organizational productivity by optimizing the right use of technology and decreasing the operational costs. This is the time when need for expert level web development services occurs. As every business has its own unique way to operate, it has its own unique requirements too, hence to find an ideal web development services provider becomes a challenging task. Web development services in Sydney, Australia have gained recognition in providing custom web application development that fulfills unique business requirements.

Regardless to business type almost every business or non-profit organization understands the importance and uses the service of web development company to have an online presence through a website, blog or ecommerce portal. Today web is widely used as a platform to market products and services to worldwide audience. The convenience to find, assess and purchase online has increased the dependency and reliance on web all across the world.

It is only a web development company which can give you a unique pulpit that is your very own website to make profits online. Without a website it is impossible to sell goods or services online and earn thousands of dollars as profits. Your website works as your online business stall displaying all the different things you have to offer to your customers.

If you are a novice and look at a website with highly interactive features you are sure to feel for at least once what technology is used by the web development company to develop the website. There is no limit to the type of languages, tools, IDEs, frameworks etc available for web development.

PHP is not uncommon to the web development niche and is useful to develop web pages which deliver much more than expected. It is often suggested to people looking for a web development company that they should hire a website development company which also uses PHP technologies for custom application development.

Agile means swift and this holds true for, Agile web development process. The web development project is split up into various well defined phases and encourages active participation of the end users or customers in each and every phase of the project.

Internet occupies the center stage in modern life. It offers a global platform, where people from all walk of life, can buy or sell, different products and services, online. Business owners, at a click of the button, can reach their customers, irrespective of their time zones or geographic locations.  The growing popularity of the e-commerce sites on the net, has added new dimension to internet. Through website, business enterprises launch and market their products or services to the worldwide clientele.

The Australian economy is growing thanks to immigrants who are shifting to Down Under in search of better opportunities. This has increased consumer demand and more people are setting up business to be part of the Australian growth story. Australian climate and its vast expanse offer a great challenge to the local business. Online business is the solution to this problem. Hence the Web development in Australia is picking up fast as it needs to deliver e-commerce solutions to its local economy.

Internet is highly competitive place for the online business and is teeming with millions of such websites.  It is important to get noticed by larger number of daily internet surfers so that greater numbers of people know about the hosted products or services. But it is easier said than done, keeping in mind the mind-boggling numbers of business websites hosted on the net. The competition out there is quite stiff.

It is important to take some standard points into consideration when choosing a good web development company for professional help in your online business development. The basic features of their services and solutions must impart reliability, dependability, and that the website should match your business image and processing.

Internet today is faster, richer and busier place than what it was a decade back. The development of groundbreaking, richer internet applications (RIA) have completely changed the image of internet. It is now more business oriented and supports millions of websites, which are into online business.

Australia has long been the land of great IT people with strong knowledge of the web development strategies. Web development in Australia may be a relatively young market as compared to the other web development giants like US and India, but the market is growing fast and offering a good number of opportunities to the web developers and even the companies across the world.

A web development company has the prerequisites of creativity and constant technological upgrade for being a prominent name in deploying precise web development solutions successfully. All enterprises in the world seek for the best web development services at cost effective rates, and that is what a professional web development company should be expert of.

Ruby on Rails or just RoR for short is an open source web application framework that has its foundations in the Ruby programming language and the Rails web application framework.

In today’s time, where there is cut throat competition everywhere, it is very essential that businesses concentrate more on core areas rather than on secondary work like web application maintenance which can be off shored to countries like India.

Microsoft Office SharePoint Server generally referred as MOSS is widely used to develop enterprise or business applications. MOSS Services are mainly used to integrate different systems of a business, these systems may be within an organization or at some remote place. Microsoft SharePoint Development helps business enterprises to centralize data storage for faster retrieval of data. Microsoft SharePoint Solutions make the process of transferring, receiving and accumulating data very simple.

In this recession hit period due to stringent budgets and lack of professional expertise this organizations are moving to countries like India for website development.