sharepoint

Change page: < 1 2 3 4 5 6 7 8 9 10 11 12 > | Displaying page 1 of 12, items 1 to 50 of 589.

Microsoft Sharepoint 2013 : Understanding app patterns (part 5) - Building MVC apps - Introducing MVC4

To get started, first create a provider-hosted or autohosted app. When the new remote web is created, open the associated web.config file and copy the settings for the ClientId and ClientSecret entries.

Microsoft Sharepoint 2013 : Understanding app patterns (part 4) - Building MVC apps - Understanding web form challenges

When developers think of creating SharePoint apps with C# and CSOM, they might immediately think of using ASP.NET to create a remote web. In fact, this is the default template used in Microsoft Visual Studio for provider-hosted and autohosted apps.

Microsoft Sharepoint 2013 : Understanding app patterns (part 3) - Building MVVM apps - Utilizing promises

When developing more complex apps against the REST API, you must often make multiple asynchronous RESTful calls. For example, an initial RESTful call might retrieve master data, whereas subsequest calls fill in child data.

Microsoft Sharepoint 2013 : Understanding app patterns (part 3) - Building MVVM apps - Utilizing promises

Microsoft Sharepoint 2013 : Understanding app patterns (part 2) - Building MVVM apps - Introducing knockout

JavaScript does not natively support the kind of loose coupling that the MVVM pattern requires. Therefore, additional support must be introduced in the form of a third-party library.

Microsoft Sharepoint 2013 : Understanding app patterns (part 1) - Building MVVM apps - Understanding JavaScript challenges

The biggest challenge in implementing apps with JavaScript is the intimate relationship between the webpages and the libraries. In many JavaScript implementations, the code in the libraries must have detailed knowledge of the markup in the webpages.

Microsoft Sharepoint 2013 : Working with documents - Checking documents in and out

Checking out a SharePoint 2013 document ensures that you are the only one making edits to it. When you’re finished making edits, check in the document so that other users can view the changes you made. Even if the document is saved, if it is still checked out, the most recent changes will not be visible to other users.

Microsoft Sharepoint 2013 : Working with documents - Requiring and displaying document check out

SharePoint 2013 is a collaborative platform with which several users can store and share documents with other team members. It’s likely that more than one user will attempt to open and edit a document at the same time.

Microsoft Sharepoint 2013 : Working with documents - Uploading multiple documents

SharePoint 2013 users will undoubtedly need to upload or move multiple documents to other locations, such as local hard disks, network file shares, or other SharePoint locations. SharePoint lets you drag files directly to your library or upload documents by using Explorer on the Library’s ribbon.

Microsoft Sharepoint 2013 : Working with documents - Customizing document templates

When a new document library is created, several file types, or content types, are available when you create a new document from the SharePoint 2013 menu.

Microsoft Sharepoint 2013 : Working with documents - Managing documents with a document library

The key difference between a SharePoint 2013 library and a list is that libraries are designed to manage files as well as the information attributed to those files.

Micorosoft Sharepoint 2013 : SharePoint Metadata Types (part 4) - Metadata in Publishing

I will elaborate further on how site columns and content types play a part in the publishing infrastructure of the SharePoint platform, to expand on metadata use in SharePoint.

Micorosoft Sharepoint 2013 : SharePoint Metadata Types (part 3) - Metadata in Lists

Lists and content types marry together nicely—if a content type describes some data, and lists contain instances of data, then the content type effectively describes the schema of a list.

Micorosoft Sharepoint 2013 : SharePoint Metadata Types (part 2) - Content Types

Content types provide content owners with the powerful capability to manage metadata content in SharePoint. The basic anatomy of a content type is that of a group of site columns (fields) that represents a content object in the content management system.

Micorosoft Sharepoint 2013 : SharePoint Metadata Types (part 1) - Site Columns

SharePoint maintains a list of site columns, which represent attributes for metadata. If you have created a custom list, or looked at an existing list defined in SharePoint, then you will have seen the site columns in action as the “columns or fields” of the list.

Micorosoft Sharepoint 2013 : The SharePoint Content Type Model - New Content Type Model Functionality

If metadata is data about data, then a metadata model is a system that allows the creation, editing, and management of metadata. SharePoint has a metadata model—called the Content Type Model.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Preparing the Server and Installing OWA via the GUI

As noted earlier, the evolution and expansion of OWA has changed the installation procedures greatly from the previous version. The first step to any OWA install is to prepare and configure the server.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Topology

Office Web Apps has moved from an exclusive SharePoint service onto its own standalone server. This change is critical to how you configure and architect Office Web Apps to service the SharePoint 2013 farm.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Mobile Device Support

Just as the nature of how SharePoint information is accessed has evolved, so has its delivery method. The previous model, which offered a rather static view that lacked graphics suited for small, low-resolution displays, has been radically updated for use as an appropriate communications platform.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Desktop Enhancements

A primary concern for Microsoft following the release of Office Web Apps 2010 was the varying user experience between different operating systems. For example, users of Office Web Apps on a Mac had only some functions available.

Sharepoint 2013 : The Office Web Applications for Sharepoint - Licensing and Versions

Office Web Apps offers some significant changes from the previous version in the licensing arena. There are two licenses in Office Web Apps this time around. The default Office Web Apps mode is view-only, and it is provided free.

Microsoft Visio 2013 : Collaborating on and Publishing Diagrams - Saving Visio drawings to SharePoint 2013

In the previous section, you learned that Visio Services on SharePoint reads Visio 2013 files directly. As a result, publishing a diagram to Visio Services can be accomplished by simply uploading the file to SharePoint. From there, anyone with a web browser can click to view the diagram.

Microsoft Visio 2013 : Collaborating on and Publishing Diagrams - Understanding Visio Services in SharePoint 2013

Visio Services is a Microsoft SharePoint Server 2013 feature you can use to share diagrams with people who don’t have Visio. There are three key advantages to sharing diagrams via Visio Services instead of publishing static webpages

Microsoft Sharepoint 2013 : Claims Authentication and Oauth - Server-to-Server Authentication

Server-to-Server authentication (S2S) represents an example of application-to-application OAuth. This approach uses a Microsoft extension of the OAuth protocol to enable applications or servers to share resources on behalf of users, without user authentication.

Microsoft Sharepoint 2013 : Application Authentication (part 3) - App Authentication - App Catalog App Authentication

This example illustrates the second approach to app authentication. In this case, your app is hosted on-premises in servers that are not a part of the SharePoint farm, and not in the cloud as in the previous example.

Microsoft Sharepoint 2013 : Application Authentication (part 2) - App Authentication - SharePoint Store App Authentication

his example demonstrates installing an app from the SharePoint Store, and using ACS as the STS. Your on-premises SharePoint farm can use an external STS, such as ACS, and in general SharePoint can be configured to trust many different token providers

Microsoft Sharepoint 2013 : Application Authentication (part 1) - Cloud App Model, OAuth

The new SharePoint 2013 Cloud App Model enables developers to provide solutions, called apps in the new terminology, to extend the capabilities of SharePoint 2013.

Microsoft Sharepoint 2013 : User Authentication (part 4) - Using Claims-Based Identity - Federated User Authentication Process

As collaboration boundaries expand and need for information increases, access to resources that are not hosted by your company or an organization that knows you is needed.

Microsoft Sharepoint 2013 : User Authentication (part 3) - Using Claims-Based Identity - Understanding the User Authentication Process and Authentication Providers

User authentication scenarios in SharePoint 2013 can be as straightforward as using Windows Integrated Security and Active Directory or as complicated as using Windows Azure Access Control Service as a federation provider.

Microsoft Sharepoint 2013 : User Authentication (part 2) - Using Claims-Based Identity

The purpose of this section is to show how claims identity is used to authenticate users. It begins with a real-world analogy that illustrates the use of claims. Then you will learn the technical requirements for implementing claims authentication. Finally, you will walk through the actual claims authentication process.

Microsoft Sharepoint 2013 : User Authentication (part 1) - Claims-Based Identity

The answers to these questions are associated with the key challenges related to providing users with access to information. These challenges include user identity, user access, and user information and storage. As you will see, claims-based identity presents a solution to these challenges.

Microsoft Sharepoint 2013 : What’s New with Claims and Authorization?

Several new capabilities are introduced in SharePoint 2013, and the following sections cover those most pertinent to the administrator.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 3)

Using the REST API from a C# application is certainly possible, but it is easily the least attractive of all the programming options. You will find that retrieving form digests, parsing out properties, and creating payloads can be tedious and messy. This section details the steps necessary to work with the REST API in C#.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 2) - Working with the REST API in JavaScript

When you choose to use JavaScript with your app, you will find that by using the REST API, you can write cleaner code than CSOM. Furthermore, you will find built-in support for REST in the jQuery library, which makes it much easier to use than CSOM.

Sharepoint 2013 : Client-side Programming - Working with the REST API (part 1) - Understanding REST fundamentals

Remote Procedure Call (RPC) is a software architecture that uses a generated client-side proxy to communicate with a remote web service. Simple Object Access Protocol (SOAP) is the protocol that is used along with the RPC architecture in classic SharePoint web services.

Sharepoint 2013 : Working with the CSOM (part 6) - Working with the JavaScript client object model - Creating, reading, updating, and deleting in the JavaScript client object model

Creating, reading, updating, and deleting list items by using the JavaScript client object model is more complex than with the managed client object model.

Sharepoint 2013 : Working with the CSOM (part 5) - Working with the JavaScript client object model - Handling errors

Just like the managed client object model, the JavaScript client object model must deal with the potential for server-side errors during the round trip.

Sharepoint 2013 : Working with the CSOM (part 4) - Working with the JavaScript client object model - Returning collections

The JavaScript client object model supports both a load and loadQuery method. The loadQuery method can be used to store a collection into a variable other than the one referencing the desired collection.

Sharepoint 2013 : Working with the CSOM (part 3) - Working with the managed client object model - Creating, reading, updating, and deleting

In the conditional scope shown in Example 4, a new list is created if the user has the appropriate permissions. Creating new lists and items using the managed client object model is done with the creation information objects.

Sharepoint 2013 : Working with the CSOM (part 2) - Working with the managed client object model - Handling errors

Because of the disconnected nature of the client object model, error handling is especially important. You might see errors thrown when you attempt to access an object or value that has not yet been retrieved from the server.

Sharepoint 2013 : Working with the CSOM (part 1) - Understanding client object model fundamentals

The managed and JavaScript client object models are maintained in separate libraries, which are located under the SharePoint system directory.

Sharepoint 2013 : SharePoint Designer 2013 (part 2) - Locking Down SharePoint Designer

SharePoint Designer is a great tool for editing design files, uploading files in bulk to SharePoint, and making configuration changes to lists and sites.

Sharepoint 2013 : SharePoint Designer 2013 (part 1) - New Features

SharePoint 2013 includes all of the existing capabilities of the previous version with some new features and enhancements.

Sharepoint 2013 : Branding with the Design Manager (part 2) - Creating a Brand

You are now getting to the fun part of Design Manager: the capability to design a SharePoint brand from raw HTML, CSS, and JavaScript files.

Sharepoint 2013 : Branding with the Design Manager (part 1)

Branding SharePoint has never been a trivial task. I know a number of talented SharePoint UI designers who have devoted their careers to doing just that. Designing a good user interface brand for any web site requires experience and knowledge of web rendering principles.

Sharepoint 2013 : SharePoint Designer and Branding - SharePoint 2013 User Interface

Because the new Windows 8 branding is less graphic intensive and geared more to simplicity with text, the coding behind the design is less complex. Designers can easily integrate the design of custom functionality with minimal use of Cascading Style Sheet (CSS) elements and HTML. This is not to say that the user interface loses capability.

Sharepoint 2013 : Microsoft Office Integration and Office Web Applications - Office Web Applications

Office Web Applications (Office Web Apps) are web browser–based applications that enable users to edit Word, Excel, PowerPoint, and OneNote files without needing Microsoft Office applications installed on client machines.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - Client-Side Object Model API Coverage

One of the original drawbacks with the prior implementation of the Client-Side Object Model was its lack of coverage for SharePoint APIs and access to functionality.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - REST and OData (part 3) - Creating, Updating, and Deleting

In this example you use a SharePoint-hosted app using the Napa Office 365 Development Tools and use the REST/OData API to create a new list in the host Web.

Sharepoint 2013 : Overview of The Client-Side Object Model and Rest APIs - REST and OData (part 2) - Filtering and Selecting

When you query for data it’s important to ask for only the data you really need. This keeps payload sizes down and speeds up delivery of the data. _Api uses OData semantics to let you do this by filtering records and selecting properties you want.