Wednesday, September 26, 2012
Tuesday, September 25, 2012
Watch the VideosThis Guide comes with 38 videos that explain all scenarios in a step-by-step manner.
Part 1- Introduction & Overview
Part 2 - Creating & Preparing the Required Infrastructure
Part 3- Installing and Configuring Team Foundation Server Pre-requisites
Part Part 4- Installing and Configuring Team Foundation Server
Friday, September 21, 2012
A design pattern approach in SharePoint development is very important for standard and reusable Solution for most common problems in software development. A design pattern is not only for implementation of code. its solution template to solve real life Programmatic Problems. adopting design pattern approach to develop solution for SharePoint that allows you to formulate a high level Solutions that is independent of the implementation details.
Most Common Design Pattern for SharePoint Development.
- Model-View-Presenter (MVP)
- Service Locator
- The Trusted Façade Pattern
- Duplicated code
- A higher potential for programming errors
- Weak typing of the business data
- Difficulty in centralizing data-related policies such as caching
- An inability to easily test the business logic in isolation from external dependencies
- You want to maximize the amount of code that can be tested with automation and to isolate the data layer to support unit testing.
- You access the data source from many locations and want to apply centrally managed, consistent access rules and logic.
- You want to implement and centralize a caching strategy for the data source.
- You want to improve the code's maintainability and readability by separating business logic from data or service access logic.
- You want to use business entities that are strongly typed so that you can identify problems at compile time instead of at run time.
- You want to associate a behavior with the related data. For example, you want to calculate fields or enforce complex relationships or business rules between the data elements within an entity.
- You want to apply a domain model to simplify complex business logic.
- The concrete implementation of the dependencies must be available at compile time.
- Your classes are difficult to test in isolation because they have a direct reference to their dependencies. This means that these dependencies cannot be replaced with stubs or mock objects.
- Your classes contain repetitive code for creating, locating, and managing their dependencies.
- The next section describes how to address these issues.
- You want to be able to test your classes in isolation, without the dependencies.
- You do not want the logic that locates and manages the dependencies to be in your classes.
- You want to divide your application into loosely coupled modules that can be independently developed, tested, versioned, and deployed.
- Authenticate external users of a SharePoint application that is located in a perimeter network. The SharePoint application uses a credential store that is also in the perimeter network.
- Authenticate the SharePoint application in a perimeter network to a Web service in the corporate network with credentials that are recognized in the corporate security domain.
- Ensure the confidentiality and integrity of messages that are exchanged between the SharePoint application and the Web service.
- Have a Web service in a corporate domain apply authorization rules that are based on the identity of the external user.
- Avoid creating additional credential stores to store passwords in the SharePoint application.
Monday, September 17, 2012
Out Frist Great Effort with UAE DEV Community. Thanks to All member of Dev Saturday UAE. to make this event and community. Special thanks for All Student off Khalifa University and IEEE.
o Mr. Khalid Hikmat
- Khalifa University’s IEEE Student Chapter, Abu Dhabi Campus.
- Dev Saturday UAE
Great Community UserGroup Startup with Oubai Abbasi Omar A. Rizk, Khalild,Ali.
FaceBook : Join US
Sunday, September 16, 2012
Posted by Usama Wahab Khan at 8:15 AM
My First Presentation for SharePoint Dev
Posted by Usama Wahab Khan at 1:41 AM
Thursday, September 13, 2012
- Create lists and content types by using designers.You can more easily create a list or a content type by using a designer to set up and lay out the contents of the list or content type. For more information, see Creating Site Columns, Content Types, and Lists for SharePoint.
- Create site columns for SharePoint sites.You can more easily create SharePoint site columns, which are also known as "fields," by using an item template. For more information, see Creating Site Columns, Content Types, and Lists for SharePoint.
- Add Silverlight web parts to your SharePoint projects.You can more easily and conveniently create Silverlight web parts by using a project template. For more information, see Walkthrough: Creating a Silverlight Web Part that Displays OData for SharePoint.
- Publish SharePoint solutions to remote SharePoint sites.You can publish SharePoint solutions to remote SharePoint sites, in addition to local SharePoint sites. For more information, see Deploying, Publishing, and Upgrading SharePoint Solution Packages.
- Increase SharePoint performance by using profiling tools.By using tools in Visual Studio, you can identify code and other elements that are slowing down your SharePoint projects and perform other performance profiling. For more information, see Profiling the Performance of SharePoint Applications and Analyzing Application Performance by Using Profiling Tools.
- Create sandboxed visual web parts..You can include visual web parts in sandboxed SharePoint projects, not just farm projects.
- Create sandboxed solutions more easily.When you’re working on a sandboxed solution in Visual Studio, only compatible APIs appear in Intellisense, and a compiler error occurs if you try to use farm-only API calls.
- Develop SharePoint projects more easily by using streamlined project templates.To help streamline SharePoint development, some SharePoint project templates from the previous version of Visual Studio were moved into project item templates. For a full list and descriptions of the project and project-item templates, see SharePoint Project and Project Item Templates.
- Test your code by using the Microsoft Fakes framework.SharePoint projects support Microsoft Fakes, which is an isolation framework in which you can create delegate-based test stubs and shims in .NET Framework applications and test your code by isolating your unit tests from the environment. For more information, see Verifying and Debugging SharePoint Code by Using ALM Features.
- Create apps for Office.An app for Office is a type of Office solution that provides new experiences within Office applications by surfacing web technologies and cloud services within Office documents, email messages, meeting requests, and appointments. For more information, see Create Apps for Office by using Visual Studio.
- Develop Solutions for Microsoft Office 2013 Preview.By using Microsoft Office developer tools, you can create document-level customizations and application-level add-ins for Office 2013 Preview applications. To obtain project templates for Office 2013 Preview applications, you download and install the Microsoft Office Developer Tools for Visual Studio 2012.