SharePoint 2013 Development: Solutions vs. Apps

Microsoft launches each new version of SharePoint 2013 with innovative features and broader capabilities. The latest version of SharePoint comes with a set of advanced features that enable developers to build apps with additional features and functionality. Microsoft also recommends all developers to build SharePoint Apps. However, the enterprises still have option to build conventional SharePoint solutions. So it becomes important for enterprises to decide the pros and cons of both SharePoint apps and solutions. At the same time, they also need to understand some of the key differences between these two to take the right decision.

SharePoint 2013 Development: Solutions vs. Apps

Execution of Code: The SharePoint apps run completely outside the SharePoint server. Further, the custom code is executed on a non-SharePoint server or the client browser. However, a business has options to pick from three types of apps, i.e., SharePoint-hosted, provider-hosted and auto-hosted. The SharePoint –hosted apps can run within the framework without any external dependencies. But the provider-hosted apps are designed with a single or multiple SharePoint components. Similar to the provider-hosted apps, the auto-hosted apps are also designed with external business logic and data storage. When these apps package is installed, a user can avail both website and database.

Enhanced Stability and Capability: As the apps run outside SharePoint server, these are effective in providing enhanced stability, performance and compatibility. A business can easily switch to a more advanced version of SharePoint as the apps are testing platform independent. At the same time, the apps can communicate with SharePoint through CSOM, ODATA and REST API. Microsoft has optimized these features to enable developers to build custom SharePoint apps without using the server-side API.

Easy to Deploy and Reuse: Microsoft has further made it easier and simpler for developers to install and upgrade the SharePoint apps. The simple configuration will further encourage many developers to switch to Sharepoint application development. At the same time, the apps can also be reused, packaged and marketed through a Public Marketplace or Corporate. The options make it easier for end-users to buy apps that can run on-premise and cloud environments, while complementing their specific needs.

Support for Server-Side Code: Unlike SharePoint solutions, the apps do not support server-side code. So the programmers have to build a solution to implement a new functionality by writing server-side code. Further, the code cannot be stored on the SharePoint farm as part of the app. The server-side code needs to be hosted on premises or in the cloud. On the other hand, the SharePoint app enables enterprises to promote a custom functionality by targeting relevant users. That is why; the solutions will be still used as part of robust SharePoint apps.

Custom Functionality: SharePoint allows enterprises to manage a variety of documents and content store on their intranet and on the web. The customized SharePoint solutions are used widely by businesses to manage their online and offline content. But Microsoft recommends enterprises to build apps to create a custom functionality as a sandboxed solution in SharePoint 2010. Further, the apps can also be used in SharePoint Online. On the other hand, the SharePoint solutions will be effective only in local and on-premise environments.

Adding User-Centric Functionality to SharePoint: In comparison to SharePoint solutions, the apps are more effective in adding user-centric functionality to SharePoint. The apps can also be used as a medium to implement functionalities according to the specific needs of an enterprise. These custom-functionalities further extend the internal functionality like Event Handler or Timer Job of SharePoint solutions. Also, the apps are effective in creating custom-functionality to make SharePoint more user-friendly.

As a business has option to choose from SharePoint apps and solutions, it is always important to do a cost-benefit analysis. A company can further determine its exact needs before comparing these two options. However, an enterprise can always switch to SharePoint apps to avail a number of advantages, while meeting the latest trends technology.

We provide SharePoint site migration and SharePoint deployment planning services. If you would like to speak to our 100% SharePoint certified team, please get in touch with us at Mindfire Solutions.

SharePoint 2013 Best Practices: Setting Up a Dev Environment - One Piece!

In order to establish a development environment for SharePoint 2013, you must begin with determining what kind of environment is required. The first step is to understand what you want to develop. You might look forward to building solutions which exclusively make use of the server-side object model. Creation and publication of apps for SharePoint can also be done, and in that case you need to opt for an Office 365 developer site. In case you want to build apps for SP catering to a corporate catalog like apps having complete control permissions, you have to consider SP 2013 full set up on a local computer as well as configuration of that set up for application isolation.

Installation of app OS for SP development environment

With respect to development environment for SharePoint app installation, the requirements are less costly and stringent compared to those for a production environment. Irrespective of the development environment, it is essential to use a computer having an x64-capable CPU, along with minimum RAM of 16 GB for installation and running of SharePoint 2013. It is preferable to make use of 24 GB of RAM.

Considering your specific budget and requirements, any one of the below-given options may be chosen:

• Installation of SharePoint 2013 on 2012 Windows Server or 2008 Windows Server R2 Service Pack 1 x64.
• Utilize Microsoft Hyper-V and go for setting up of SharePoint 2013 on a virtual machine that is running R2 Service Pack 1 x64 2008 Windows Server or guest operating system for 2012 Windows Server.

Installation of the app building prerequisites for the OS and SP 2013
To get Sharepoint application development right using SharePoint 2013, your operating system needs to have particular pre-requisites installed prior to the beginning of the installation. Owing to this, SP 2013 incorporates a PrerequisiteInstaller.exe tool which helps in the installation of all the pre-requisites. This tool should be done before execution of the Setup.exe tool. The following is the series of steps:

1. The PrerequisiteInstaller.exe tool is run.

2. The Setup.exe tool, that comes with the installation files, is executed.

3. Then the license terms for Microsoft Software should be accepted.

4. Once you go to the “Choose the Installation” page go for Stand-alone.

5. In case there are any errors during the installation process, the log file needs to be reviewed. For locating the log file, the first step is to open a Command Prompt window, followed by typing the requisite commands. Once you are done with the installation, you will be able to see a link to the log file.

6. When the installation is done, you will be prompted to begin the configuration wizard for SP Products and Technologies.

7. Once the configuration wizard is over, the Template Selection page pertaining to the new SP 2013 site is visible.

Installation of Visual Studio 2012 along with tools
When you go for installation of Visual Studio 2012 as well as the Office Developer Tools for the same, you obtain every tool and template required for development of SharePoint 2013 across your local development machine.

After you have completed installation of Visual Studio 2012, Office Developer Tools with respect to Visual Studio 2012 along with the SP Client Components need to be downloaded as well as installed. The client components and tools can be installed by opening the Apps download page for Office and SP Developer Center, thereby selecting the link pertaining to the web-based platform installer which installs the assemblies and tools required for development of SP apps. The specific version of the assemblies and tools is suitable for a SP hosted, autohosted or provider-hosted app for SharePoint. The assemblies can be used within the client components for development of a web application or a client application that connects to SharePoint, and is running or hosted over an x86-bit platform. In case your target is a web application of x64-bit then the x64-bit versions of the requisite assemblies have to be installed separately.

We provide SharePoint site migration and SharePoint deployment planning services. If you would like to speak to our 100% SharePoint certified team, please get in touch with us at Mindfire Solutions.

Top 8 Ways to Mitigate Risks in SharePoint Deployment

Deployment of the useful web application development platform of SharePoint involves certain risks. The SharePoint sites, which primarily include the SharePoint Online and the hosted SharePoint farms, have high chances of falling prey to some of the serious content security risks. Considering the fact that SP Online is highly preferred by all types of enterprises today for regulation of data, securing this data is a dire necessity. In fact, organizations are often found facing certain problems when it comes to maintaining the security of the data in SharePoint. The risks need to be mitigated without any wastage of time to ensure smooth work flow.

Here is a brief overview of the risks involved in SP deployment along with the possible ways of reducing their effects.

1. Less Awareness about SharePoint Content

The lack of awareness about SP content is a prominent risk in the deployment of this particular web application development platform. The two main ways of spreading increased awareness are implementation of the governance guidelines along with providing of content classification. The end users should be trained accordingly for performing periodic scans of content. Teams also have the option of making use of the SP metadata as well as workflows to pass the sensitive information to the secure locations.

2. Failing to Secure the Content in SP Servers, Transit and Endpoints

Securing the content in the SharePoint servers as well as endpoints is necessary. Enterprises must make it a point to implement solutions that ensure the security of the content on the SP servers as well as the backups through access control and encryption. Additionally, the teams should also go for a whole-disk encryption for endpoints and most essentially, laptops. The SSL encryption for data in transit should also be enabled by the security administrators.

3. Misconfiguration of the Access Controls and Permissions

This is yet another risk that often poses a problem in the deployment of SharePoint. The solution lies in auditing the existing SharePoint permissions and then reviewing or creating of the corporate access control policies. Following this, the SP permissions should be aligned with the corporate directory services, by which, the administrators can get an idea about the usage of inheritance as well as unmanaged item-level permissions.

4. SP Platform Security Risks

The SharePoint platforms need to be hardened by means of disabling the ports as well as services that are not essential to the functioning of the platform. Regular patching apart from whitelisting of applications also helps in reducing the risks of platform security.

5. Failing to Limit the Administrator and Service Accounts

One essential way in which the risk of failing to limit the administrator as well as service accounts can be reduced is by limiting the privileges on service accounts. Disabling the install account and not using the shared administrator accounts are other prominent ways of mitigating this particular risk.

6. SP System Architecture and Network Configuration Issues

The system architecture as well as network configuration issues related to the SharePoint can be reduced by putting a dedicated SP web front end in a DMZ and by making use of a single-function-per-server approach. Hardening of the SP, OS as well as the database as per the best practices is also highly recommended.

7. Issues Related to SP and Malware

Risks arising from SharePoint as well as Malware can be solved by implementation of the server malware solution along with a regular updating of the anti-virus definitions.

8. Difficulty in Performing Backups and Providing DR Capability

The only possible way in which this problem can be solved is by performing annual backups as well as tests and restoring them on a regular basis.

Managing the above-mentioned security risks through an application of the appropriate security controls helps in reducing the level of content security as well as compliance risks in SP to a great extent. If you were to attempt a SharePoint site migration project, understanding of these best practices would ensure a successful migration.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint programmers, please get in touch with us at Mindfire Solutions.

Getting Started Developing for SharePoint 2010?

The process of developing for SharePoint is naturally quite elaborate and encompasses several steps. In order to have a complete overview of the development on this much popular and preferred web application platform, it is good to go step-by-step and accordingly, begin with a conceptual overview of the SharePoint foundation.

Understanding SharePoint Foundation

The application of Microsoft SP Foundation is built on top of the Microsoft ASP.NET framework and the Internet Information Services. Server Farm, which is basically a set of servers running the various components of SharePoint Foundation, also comprises more than one front-end web servers along with Microsoft SQL server database servers. Every farm has an individual configuration database consisting of information about the front-end web servers in the administrators of the farm. Each content including that of the user information, on the other hand, is stored in the content database while the server farms too have multiple content databases.

Choosing the Best-Suited SharePoint API

Microsoft SP comes with three different types of APIs and the next question that arises with regards to the development on this platform is which of the APIs to be used. Here is an overview of the three kinds along with their advantages and limitations.

• Server-Side Object Model

To begin with, there is the server-side object model coming up with a wide range of options for extending the capabilities of SP 2010. The good part of this is that it has all APIs that are documented in the SP 2010 Class Libraries and Web Service References section of the MS SP 2010 software development kit.

• Client Object Model

The client object model allows for integration of SharePoint 2010 capabilities into script. This can be executed in the browser or code, in a .NET framework managed application or in a Microsoft Silverlight application. The APIs in this particular model act as wrappers around a customized web service, dispatching the calls to the server- side object model.

• SharePoint 2010 Web Services

The SP 2010 web services pave the way for an integration of the SP capabilities into a code that runs in a client- side or server-side applications remotely. This specific variety offers a limited set of REST interfaces for developers, who happen to be familiar with the particular standard.

Glide Path for ASP.NET Developers

This area concerns the use of SharePoint Foundation as an ASP.NET application. Developers must be aware of the manner in which development differs with respect to ASP.NET and SharePoint. The areas that need to be taken into account are mobile adapter development, modification of Web.config files, page development as well as user and group authorization.

SharePoint Foundation Development Tools

Several tools are implemented when it comes to developing solutions for this remarkable web application development platform. These tools can accordingly be customized to maximize the efficiency of the developer and lead to a better outcome. The setting up of the development environment for SP 2010 on Windows 7, Windows Vista and Windows Server 2008 is an essential consideration. At the same time, one must also be informed about the usage of visual studio and SharePoint designer for SP development.

Important SharePoint Programming Tasks

A number of SharePoint programming tasks are taken up as a part of the process of developing for SP 2010. Following are some of these tasks:

• Conversion of date as well as time values
• Description of forms of URL strings
• Addition or deleting of list items
• Returning items from a list
• Registering as well as Importing of Namespaces
• Security validation and making of posts to update data

Knowing about the Best Practices

When it comes to development on the highly advanced platform of SP 2010, understanding the best practices is essential to ensure perfect execution of the task. Some of the best practices include the following:

• Avoidance of the suspended impersonation of the calling user
• Avoidance of unnecessary construction of SPWeb and SPSite objects
• Disposal of objects
• Restrictions on file naming
• Techniques of object caching
• Optimizing of the code performance

The above-mentioned steps offer an overview of how the development process can take place in a smooth manner. If you were to attempt a SharePoint site migration project, understanding of these best practices would ensure a successful migration.

We provide SharePoint bespoke development services. If you would like to know more about the expertise of our SharePoint programmers, please get in touch with us at Mindfire Solutions.

.Net to SharePoint Migration - Top Insights you can't ignore for a successful migration

Any sort of migration must always begin with a proper understanding of the capabilities of both the source system and target system. What new potentials the target system might provide? Is there any missing functionality in the target system that might necessitate the purchase of third party components? These are some aspects that need to be considered prior to taking the plunge. A proper understanding of the differences as well as the similarities of both the platforms will definitely help in the entire process of migration.

Today, a number of .NET developers are considering a move towards the creation of a SharePoint site. So, why such a move has been favored by web developers all around? Well, here is a quick look at the reasons that favor the SharePoint solution:

• No need of providing support as well as maintenance to data stored in the database of SQL server in the SharePoint.
• Site templates can be used for the creation of new sites and publishing pages featuring different layouts.
• Versioning of the content can be maintained easily without any coding
• Security of item level can be provided without taking up any extra effort.

These reasons strongly support the migration of .Net application to a publishing website of SharePoint. In most cases, the use of a migration tool is witnessed as it ensures an efficient and successful migration. The migration strategy involves the following aspects.

1. Source System (SS) - An application based on .Net usually stores data in a specific database of SQL server. This is referred to as the source database. The data comprises of the profile information of user, static texts, files, and images.

2. Staging Database (SD) - A staging database needs to be designed for pushing the data (apart from the binary ones) from database of the source system with proper formatting making use of the stored process. It is to be noted that the binary data will be recovered directly from the source system file.

3. Target System (TS) - Following this, it is important to create a parallel sub site for each .NET application page categorized under diverse functional areas in SharePoint under separate site collection.

4. Migration Tool (MT) - Henceforth, the migration tool that is designed will extract the data from the source system database and subsequently push it to the publishing pages of SharePoint in the corresponding site. Here is a look at the process:

Choose the content pertaining to a specific functional area from the staging database into the .Net Data Table and create publishing pages concerning each row mentioned in the table. You must update the metadata following this:

• The tool helps in wise migration of all Meta data including the Modified date as well as Created date along with other specific custom fields.
• It also helps updating the published content, rollup image, and page image on the fly
• The tool also assists in setting the custom properties of a customized web part in a publishing page on the fly.
• It will choose the binary data from the database of the source system along with uploading the specific data into the picture and document library of the SharePoint site respectively.
• For a specific functional area, the migration tool will likely go for the creation of sub sites on the fly following it up with creation of page with the updated Meta data.

The tool also offers the status of the presently running tasks.

General Steps to Migration

ASP.Net to SharePoint migration involves three basic steps. Here is a look at the same:

• Addition of a Web Deployment Project to the website that helps creating a single DLL for all codes and several other dependent DLLs of the website.
• Copying the DLLs bin folder into the bin folder of the SharePoint and modification of the web configuration file for using the copied DLLs.
• Opening of the SharePoint site from the Designer and importing the web pages from the application following it with the linking to proper DLLs.

Adopting the above-mentioned steps and strategies will surely help you to go forward with the successful migration of .Net to SharePoint. To help you with small migrations, you could even use webparts. To help you with SharePoint Webparts development, there would be numerous companies who can assist.

We provide custom SharePoint development services. If you would like to discuss with our SharePoint developers, please get in touch with us at Mindfire Solutions.