The terms ghosting and unghosting are often used in conjunction with the. Page ghosting lets a front-end Web server store an. Page ghosting offers performance benefits because WSS can serve up pages for thousands of sites using a page template stored on the local file system and loaded into memory just once. When a user modifies a page template and saves the changes, a customized version of the page is stored in SQL Server for that particular site.
This is often referred to as unghosting a page. However, the documentation no longer uses the terms ghosting and unghosting. Now the term "uncustomized page" describes a page template used directly from the local file system of the Web server, while "customized page" is used when talking about a modified version of the page template that has been written to the content database for a particular site.
Microsoft Office FrontPage has been renamed Office SharePoint Designer , but its target audience remains users rather than developers. One of the most tedious aspects of customizing and branding sites in WSS 2. As a result, many developers and designers resorted to copying HTML layouts and pasting them from page to page. As you can imagine, this makes it very hard to customize and maintain a site whose layout requirements differ from the standard WSS site.
A remedy appeared in the form of a powerful page templating feature known as Master Pages, introduced with ASP. A Master Page is a template that allows you to define a standard page layout for an entire site with elements such as a banner, navigation controls, and other menus. The pages that link to a Master Page are known as content pages. The key concept is that each content page links to the Master Page to acquire the shared layout and then extends the Master Page by inserting customized content in named placeholders.
Every version 3 site is provisioned with a special catalog known as the Master Page gallery that contains a page named default. The Master Page layout includes standard menus and navigation controls. Figure 2 shows an example page based on the standard layout defined by default. The default. Take a look at the simplicity of the content page definition:. The content page definition does nothing beyond placing a minimal fragment of HTML content inside PlaceHolderMain, but it produces the typical page layout with site icons, menus, and navigation bars as shown in Figure 3.
Once you learn how to use the standard set of placeholders defined in default. NET controls. This can be done for pages at the scope of a site or a site collection. Master Pages and content pages are stored and loaded like the page templates and page customization discussed earlier. There are page templates defined for the Master Page as well as for content pages that reside on the local file system of the front-end Web server. Each site initially uses uncustomized ghosted versions of the Master Page template and content page templates.
When a user customizes and saves one of these pages for a particular site using a tool such as SharePoint Designer, a customized unghosted version is saved into the SQL Server database. You can customize the Master Page for a site if you like, leaving the content pages uncustomized.
Or you can customize one or more content pages while leaving the Master Page uncustomized. And you can undo any changes; both WSS and SharePoint Designer provide simple menu commands to discard customization changes from the SQL Server database and revert back to the original page template. This is a tokenized reference to a Master Page that can be changed programmatically on a site-wide basis. Note that each site has its own Master Page gallery with a default. That means all the sites inside a site collection do not automatically use the same Master Page.
This dynamic token works in conjunction with the CustomMasterUrl property of a site and provides a secondary target Master Page that can be redirected programmatically. These static tokens allow you to hardcode a relative path to a Master Page from either the root of the current site or the root of current site collection. One of the most popular ways for developers to extend WSS 2.
Web Parts are great because they add the extra dimensions of user customization and personalization. Consequently, there are now two different Web Part styles.
WebPartPages namespace. The newer ASP. WebParts namespace. It was an important design goal for WSS 3. NET-style Web Parts. This goal was accomplished by building WSS 3. NET services database. Web Part Pages can also contain catalog parts that let users add new Web Parts into zones. For more background information about how the ASP. The WSS 3. When you create a content page that links to default. The other controls that appear on a typical WSS 3. Instances of the WebPartZone control are usually defined in content pages.
As you can see, this. WebPartPages namespace and let it do all this work for you behind the scenes. At a minimum this involves creating a class that inherits from the WebPart base class defined in the System. WebParts namespace and overriding the RenderContents method.
The Web Part definition shown in Figure 8 has no dependencies on Microsoft. The WebPart class in the older version of Microsoft. NET Control class, as shown in Figure 9. However, you can also see that the WebPart class in the new version of Microsoft. NET Web Part class instead. This technique of changing a base class in a later version of an assembly is known as rebasing.
The rebasing of the WebPart base class in Microsoft. If you look at the standard web. One nice aspect of writing code to query BDC entities is that you don't have to worry about managing connections or whether you are accessing the back-end system through Web services or ADO.
CMS provided a structured way for content authors to add content to a company's public Web site using professionally formatted layout pages. CMS also provided a formalized scheme where a privileged user must approve any page modification before it can be seen by the Web site's visitors. While there is a connector that provides a certain degree of integration between CMS and SPS , these two products are built on very different architectures, and you cannot build a site that fully benefits from both the CMS Web content management features and the SPS portal features.
This will obviously have a significant impact on customers who have already become familiar with CMS development. Instead, the infrastructure has been designed using basic WSS 3. This approach lends itself to building custom solutions that extend the basic Web content management infrastructure by using standard WSS components such as custom event handlers and workflows. However, MOSS extends this functionality by introducing a publishing scheme based on page layouts.
A page layout provides a structured approach to collecting content from content authors and displaying it on a page within a portal site.
Some of the page layouts provided by MOSS include welcome pages, articles, and news items. An example of a page layout in editing mode as seen by a content author is shown in Figure 9.
As you can see, page layouts are designed to make it fairly straightforward to add and modify content from within the browser. You might also notice that MOSS provides a toolbar within the browser to give content authors and approvers a convenient way to move content pages through the editing and approval processes.
Each page layout is based on a WSS content type and an associated. By layering page layouts on top of content types, MOSS makes it possible to add custom fields for storing different types of structured content such as HTML, links, and images.
Once a custom field is defined inside the content type associated with a page layout, it can be data bound to the associated. MOSS ships with several field controls such as a rich HTML editor as well as others for editing custom fields based on images and links. Many field controls support adding extra declarative constraints to keep portal content within a highly structured format.
Note that the page layout infrastructure is extensible because WSS content types support inheritance. It's fairly straightforward to take one of the built-in page layouts and customize it by extending its underlying content type or. In addition to field controls, an. NET server controls and Web Part zones. A page layout with Web Part zones provides the content author with the flexibility to add Web Parts displaying content outside the schema of the current page layout. The master page gallery also contains a metadata column to associate each.
Note that it is possible to have multiple page layouts, each with its own. This is useful when you want to create several different views for the same set of structured content. Whenever a content author creates a new content page from a page layout, MOSS creates a new instance of the associated content type and stores it in a document library named Pages. When a content author updates content for custom fields within a page layout, WSS stores the data within a structure defined by the underlying content type.
The fact that content page instances are stored in a WSS document library means that the MOSS Web content management infrastructure can take advantage of basic document library features such as versioning, auditing, approval, workflows, per-document security configuration and security UI trimming.
By default, MOSS uses the basic document approval features of a WSS document library to control when the updated content is shown to the site's visitors. However, the infrastructure was designed to make it straightforward to associate custom workflows with the Pages document library for scenarios where you need something more sophisticated than the default content approval functionality.
Note that an instance of a content page stored in the document library does not represent a copy of the page template. Instead, it contains redirection logic to link it with the.
That means updating the. MOSS provides a framework for document converters, components designed to read content from an external format such as a Word document and convert it into a format that can be displayed within a content page. Several document converters are scheduled to ship with MOSS , as well as a framework for building and integrating custom document converters.
MOSS provides content deployment features that allow you to transfer content from one site collection to another. This is valuable for companies that prefer to author content in a staging environment before moving it into their production environment. You take advantage of MOSS content deployment features by configuring paths and jobs.
A path defines one site collection as a content source and another site collection as a content destination. Once you have defined a path, you can define one or more jobs to move content from the source to the destination.
Jobs can be run on demand or they can be scheduled to run at a future time or on a periodic basis. MOSS also supports a feature known as site variations for companies that need to duplicate a site's content for translation into multiple spoken languages or for targeting different types of rendering devices. For example, imagine you have configured variation support for German, French, and Spanish. MOSS maintains a parallel structure across these three different sites with respect to pages and child sites.
When a content author adds a new page to the master variation site maintained in Spanish, MOSS automatically adds the same page into the structure of the other sites as well. MOSS can also be configured to create a WSS task marking the required translation as a to-do item for a language translator. While MOSS will not actually convert your content from one language to another, it does keep multiple sites in sync with respect to their content structure, which provides a good deal of value.
MOSS provides several caching options. NET page, it provides a more sophisticated framework to reach the same end. You can enable MOSS output caching at the site collection scope. When using these caching features, you configure caching profiles to control caching page items and complete pages in memory. MOSS also supports Web front-end disk caching. If you enable this cache, MOSS will begin writing the large files it retrieves from the SQL Server database into a special cache on the local file system of the front-end Web server.
This procedure eliminates the need to continually move. In particular, WSS 3. Developers have used these BI technologies as a platform for building dashboard-style applications that provide upper-level management with up-to-date data that reflects the health of a business and flags potential problems in a timely matter. Consistent customer feedback indicated that a large percentage of corporations maintain a significant amount of business logic in Excel workbooks, and that this business logic has been hard to reuse across a large organization.
Excel Services doesn't suffer from the same types of scalability problems that occur when you run the desktop version of Excel on the server. Excel Services also provides a server-side rendering engine that can display worksheets in the browser as HTML. That means a company can store its Excel workbooks in a centralized document library and make them viewable by users who don't even have Excel installed on their desktops. Furthermore, users can see the numbers displayed by a worksheet within the browser without having any access to the business logic behind it, thereby protecting a company's intellectual property.
The Microsoft Office system introduces a new paradigm, recognizing that companies maintain business logic within Excel just as they maintain business logic within compiled assemblies or SQL stored procedures.
To support this new paradigm, the Office team added many new features to the Office system products designed to expose and update this business logic as well as to protect the intellectual property represented by this logic. The desktop version of Excel has been enhanced to allow information workers with Excel expertise to publish and update their workbooks in a document library within an MOSS portal site or a WSS team site.
Users running Excel can view these workbooks through the familiar client experience while other users can rely on Excel Services to view the same workbook inside the browser. Note that this new workbook publishing metaphor allows a company to maintain a single master copy of its critical workbooks.
It also allows the workbook author to post updates without the need to involve the development or IT staff. It's important to note that the use of Excel Services isn't restricted to the browser. You can create a Windows Forms application that uses the server-side Excel calculation engine but that doesn't use the rendering engine.
For example, a Windows Forms application can use Web services from Excel Services to load a workbook on the server, enter input data, perform calculations, and return a result as shown in Figure You can see it's not that hard to take advantage of formulas in Excel spreadsheets from across the network in a desktop application.
This example furthers the analogy that Excel Services exposes the business logic defined in a workbook just as SQL Server exposes the business logic defined in a stored procedure. Do you need to assign all these cases to the same person? Create a view containing the column you need to edit, lets assume its a "assigned too", linked to the People Picker, AD or whatever Within this view, change it to a datasheet view, this will give you spread sheet editing capability Here, you'll be able to change the "assigned too" value in one move via copy and paste functions.
Highlight the column and paste the desired value in Save back to standard view, all the changes will be made to the server Editing at the source seems unnecessary to me.
Thursday, March 10, PM. The two versions of the software I referred too are free, all you'd need to find is the time. Hopefully we're moving to MS Service Manager and won't need it anymore. Any thoughts? Is it a list? You can either use DataSheet view OR export it as a linked spread sheet, make all the changes you need, and synchonise the changes. I thought I'd be back! If you've got admin rights, make your own view, select all the needed columns and use the datasheet view on that. So will editing the views edit the actual data in the list?
By creating a view of the data that'll work for your needs, you'll be able to edit them much faster than one item at a time. So unless I'm completely missing the point, that doesn't seem to achieve my goal it will only provide a view with the edits.
0コメント