Friday, September 14, 2012
Ans: No, Windows Server 2012 doesn't support SharePoint 2010 right now. If you try to install SharePoint 2010 on Windows Server 2012, you might see at least one of three issues, described in this Microsoft Support article. Unless you don't mind being on the receiving end of some "unexpected behavior," it might be best to wait.
KB Article Explaining this: http://support.microsoft.com/kb/2724471
- Branding public-facing SharePoint sites considered mandatory
- Custom user interfaces (UIs) require custom training
- Invest in a governance plan, governance team
It seems that one of the first things people want to do with a new Microsoft SharePoint installation is to brand it. Branding public-facing SharePoint sites is considered practically mandatory.
Branding internal corporate portals to reinforce the company image might also make sense. But the most common use of SharePoint within an organization is for departmental sites, team-collaboration sites, and document-management sites. Should you brand these internal sites?
There are two kinds of SharePoint branding for internal sites. One preserves the full SharePoint UI and feature set. This type of simple branding modifies graphics, colors, and font types. It uses features that are built in to SharePoint to let site owners update site navigation and Web Parts.
This branding might involve changes to Cascading Style Sheets (CSS) or edits to the SharePoint master pages, but it leaves the UI completely predictable to the average SharePoint user and can be supported without help from an outside branding expert or the person or department that performed the branding.
Anything more complex than this falls into the second category of branding. This type of branding often involves an outside branding consultant and hours upon hours of planning, design, and implementation to match the external company website or an older, custom internal site. This type of branding changes how SharePoint and its UI work.
Before you decide to brand internal sites by using this second category of customizations, ask yourself the following 10 questions. (If you still insist on branding your SharePoint installation after reading this article, see the sidebar "If You Must Brand SharePoint.")
#1: Would you pay to brand Windows Explorer or Microsoft Excel?
Have you branded your word processor or your email client? Of course not! These are tools. They should have a consistent and predictable UI, such as an obvious start button. After learning how to use a tool one time, you should be able to figure how to use the same kind of tool the next time.
SharePoint is also a tool, especially when used for team collaboration and document management. Branding sites that are used for those purposes-especially when users might access more than one site-should be treated as such.
#2: Do you want to increase your per-user costs?
The per-user cost of a SharePoint installation is fairly reasonable. That is, until you start spending $10,000 to $30,000 per department-or even per site-to pay for a graphics design firm or branding consultant to customize your internal sites. The real-world branding costs can easily be in the hundreds of dollars per user and provide only a cosmetic benefit.
#3: How fast do you want users to get to work?
Customizing UIs takes time and often delays the start of a new SharePoint installation. Then, when branding has been approved, teams are put together to get the sites branded.
These teams must interview consultants, review designs, wait for delivery, and test the result before the sites can be deployed to users. And then, if each site looks different, with a different and unpredictable UI, users will be wasting time figuring out how to navigate the site and how to find content.
#4: How much do you want to spend on training?
Out of the box, SharePoint has a wealth of available training and support resources, including instructor-led classes, books, online videos, and endless web resources.
All these resources are affordable (or even free) but are useful only for uncustomized sites. Custom UIs require custom training; without it, users are less productive.
#5: How much do you want to spend on support?
If each site is different, will your support groups be able to help your site users? Will your Help desk be able to answer questions such as, "In the HR site, I click on a green duck to get to the employee manuals, but I just went to the IT site to find software manuals, and there's no green duck. There are just two trucks, a race car, and a go-cart. Which should I click?"
(If you think the duck-and-cars example is ridiculous, I'm not just being silly. I've seen many branded SharePoint sites that can be described only as "unique" and can be explored only by clicking everything you see until you find what you're looking for. You've probably seen sites like these, too-although, to be fair, site owners are sometimes the ones who insist on these odd designs.)
This brings up a related issue: Graphic designers aren't always good SharePoint designers. Graphic designers tend to think of SharePoint as just another custom website and often break or remove the most basic features, such as Quick Launch or the ability to add or change a Web Part.
After the consultant, designer, or brander has finished with the site, who will pay for fixing such issues, or even updating the site later? If you want to add just one more link to their custom-designed navigation, will you need to pay to redesign the site?
#6: How much time do you want to waste?
Of course, much too often, the site owner is the one doing the branding. SharePoint Designer is free, easy to download, and talked about everywhere on the web. And it's so easy to use that site owners often become self-taught site web designers, spending much of their time playing with SharePoint Designer.
This problem isn't new. Remember the early spreadsheet days, when managers switched from managing teams to spending all day playing with spreadsheets? Now, in the age of SharePoint, we have managers and team leaders spending too much time as web designers. Most of these site owners have no design training and no governance.
#7: Do you know who's in charge?
When every department is doing its own thing with SharePoint, is any department doing the right thing with corporate assets? Are site owners following corporate standards for site content and content governance, or are they simply creating cool-looking sites with random links and storage?
If you lose control of SharePoint and the content that's stored there, you might never get it back (short of starting over from scratch). And when the legal or R&D departments ask, "Can you find X?" or "Can you tell me who did Y?" are your SharePoint sites organized and structured enough to actually perform an audit?
#8: How difficult will sites be to audit?
If each department and team feels free to create custom UIs as a means of branding, then they also might feel free to store their content any way they like. If they have their own branding, then they will surely have their own custom content types, list types, and metadata.
How will a researcher or auditor find anything in such a system? Imagine being an auditor who must visit a hundred sites, each with a different UI, to find a document about a customer or a product. This Wild West approach is expensive and difficult to maintain.
#9: Are there better places to invest your money?
How much sense does it make to try to reduce costs by licensing SharePoint Foundation or SharePoint Server Standard Edition, only to spend a lot of money on custom (and cosmetic) branding, and then more money on custom training and lost productivity because of the branding? For the same price, you can stay with out-of-the-box SharePoint and spend the extra money on SharePoint Enterprise Edition, Microsoft FAST Search Server, and some powerful business intelligence (BI) tools.
You might even have enough to invest in faster hardware, the next level of SharePoint, or more user training. If you're interested in doing things the right way, right from the start, then invest in a governance plan and an ongoing governance team.
#10: Do you really want to do this all over again?
Your branding costs don't end with the current installation of SharePoint. Sooner or later, along comes the next generation of SharePoint with a whole shopping cart full of new features that you want and need.
Branded sites almost never upgrade cleanly. Over the past few years, I've seen how the migration from SharePoint 2003 to SharePoint 2007-and more recently from SharePoint 2007 to SharePoint 2010-has worked for branded sites.
Typically, it hasn't been a good experience and has required paying branders to rebrand all the sites to work in the new version. Are you willing to bet on the effort and cost of moving your branded sites to the next version of SharePoint?
The Bottom Line
Before you make the decision to brand internal sites, make sure you have a real business need to do so. Remember, SharePoint is a tool, like Microsoft Word or Excel. You don't brand those programs, do you?
Talk to other companies that use SharePoint, and find out what it's really costing them to brand sites, including the ongoing costs to support branded sites. Will new hires be able to figure out all the custom UIs and site designs? Will you need to upgrade customized sites to a new version of SharePoint (or even to another product)?
Look at your budget. Can you afford the up-front costs, ongoing support costs, end-user training costs, and eventual upgrade costs of branding?
And what about legal and business accessibility requirements (e.g., support for screen readers, high-contrast text, nonmouse navigation, Web Content Accessibility Guidelines--WCAG-2.0). How might branding affect these requirements?
In a nutshell, do you really need to brand?
If you're still not convinced, see the sidebar to Michael's article: "If You Must Brand SharePoint."
Q. How does Client object model works?
Q. How many types of Client Object model extension are available in 2010 and when would you use one or the other.
Ans. To develop rich client side solutions, three set of client-side APIs has been introduced in the Microsoft.SharePoint.Client namespace. The three APIs are targeted for three different types of clients.
1. .net Managed applications – These are used when we have to create console applications or window applications, web applications which are not running inside SharePoint Contex.
2. For Silverlight applications
Q. What is the purpose of calling clientContext.ExecuteQuery() ?
Ans. ExecuteQuery gives you the option to minimize the number of roundtrips to the server from your client code. All the components loaded into the clientcontext are executed in one go.
Q. What Do you know about SharePoint Object Model?
Ans. In Sharepoint Object model there are two Important namespaces, Microsoft.Office.Server and Microsoft.SharePoint . The Microsoft.Office.Server namespace is the root namespace of all Office Server objects and Microsoft.SharePoint is the root namespace for all WSS objects.
Q. How Do you bind a Drop-Down Listbox with a Column in SharePoint List ?
Method 1 : You can get a datatable for all items in the list and add that table to a data set. Finally, specify the dataset table as datasource for dropdown listbox.
Method 2 : You can also use SPDatasource in your aspx or design page.
Q. What are the various tools used for creating the solutions?
Ans. Some of the common tools are
2. VSeWSS (Visual Studio extensions for WSS )
Q. Client Object Model vs Server Object Model in SharePoint 2010 ?
Where as In Server Object Model is like a Production Server Environment to access the data where SharePoint server installed on the machine .
InfoPath is based on industry-standard Extensible Markup Language (XML). Extensible Markup Language (XML) is a condensed form of Standard Generalized Markup Language (SGML) that enables developers to create customized tags that offer flexibility in organizing and presenting information. When you design a form, InfoPath creates a form template (.xsn) file, with an .xsn extension. When someone fills out a form in InfoPath, the data in that form is saved in XML format. This makes it easy for organizations to reuse the data elsewhere, perhaps in an existing process that relies on XML, such as an expense reporting process.
However, you don't need to understand XML in order to design or fill out an InfoPath form. The important point is that the form's XML format makes it easy to repurpose and share the data you collect.
In InfoPath, you can do two things:
You can design and publish interactive, user-friendly forms in design mode. In addition to inserting standard controls into a form, InfoPath lets you insert controls that offer users the flexibility to add, remove, or hide sections of a form. The forms you design can range from simple forms for collecting data to complex forms that are part of a larger business process. You don't need programming or scripting expertise to design an effective form. However, if you know how to write script, you can use Microsoft JScript or Microsoft Visual Basic Scripting Edition (VBScript) in your forms by accessing the Microsoft Script Editor (MSE) from within design mode.
Fill out forms:
Users who have InfoPath installed on their computer can fill out forms using familiar, document-like features, such as the spelling checker and rich text formatting. Depending on the form's design, users may also be able to merge data from multiple forms into a single form, or export data to other programs. Users can also save forms to their computer, work on them offline, and then submit them to the corporate network when they are reconnected. This is especially useful for people who have intermittent or limited access to network resources, such as employees who travel frequently.
Why to Use InfoPath?
InfoPath forms can be straightforward, simple forms that are used by a few people in a small workgroup For example, a 10-person sales team can use InfoPath to fill out and share information in sales call forms. These forms can be published to and accessed from a common location on the company network, such as a form library located on a Microsoft Windows® SharePoint™ Services site. Alternatively, the sales call form can be designed so that data is submitted directly to an existing database of customer information.
InfoPath forms can also be more sophisticated forms that are integrated into the existing business processes of a large organization. For example, if a company uses Microsoft BizTalk Server to manage the process of expense claim reporting, developers in the company's IT department might design an InfoPath expense claim form that submits data to BizTalk, which then routes that data to the appropriate department for approval or processing.
The following lists are some of the most important benefits of using InfoPath:
Reusable data: The data stored in an InfoPath form doesn't have to remain locked in the form forever; it can be easily separated from the form and reformatted or reused in a variety of ways. This enables form designers to integrate form data into existing business processes.
Accurate data: As a user fills out an InfoPath form, the data they enter can be checked for data validation errors. If your form is connected to a database or Web service, users won't be able to submit data until they fix these errors. This helps you ensure that the data you collect is accurate and error-free, and that it conforms to whatever standards you specify.
Offline support: Unlike Web-based forms, InfoPath forms don't have to be filled out while a user is connected to a network. Users can fill out forms offline, and then submit them later, when they are reconnected.
Flexible controls: In addition to standard controls, such as text boxes and list boxes, InfoPath also includes a number of new controls, such as repeating tables and optional sections these types of controls let you create a flexible form that is designed to accommodate your users. For example, in an expense report form, you can use a repeating table to allow users to enter only as many expense items as necessary.
Tablet PC support: InfoPath allows you to design forms for Tablet PC users. In particular, you can include special controls, called ink picture controls, in your form. Tablet PC users can then add handwritten words or drawings inside these controls.
Microsoft Office SharePoint Portal Server 2003 connects people, teams, and knowledge across business processes. It unifies disparate information, facilitates easy collaboration on documents, projects, and other efforts, and presents specific applications and customized content based on a user’s functional group and organizational role. SharePoint Portal Server works with Microsoft Windows Explorer, Microsoft Office applications, and Web browsers to help you create, manage and share content throughout your organization.
The InfoPath form library is the primary integration point between Windows SharePoint Services and InfoPath. An InfoPath form library is a special type of document library that can contain and promote any information from any XML file. All documents stored within it are based on a specified InfoPath form template.
The form library is the main distribution point for a specified InfoPath form template; it allows the form to be maintained, deployed, and shared for use by the members of an organization. The form library can display columns of information extracted from the forms. With these columns, the user can create custom views to organize the forms and their content, called property promotion.
The form library also makes the extracted information available for searching as part of the SharePoint site. A form designer can use InfoPath to publish a form template directly to the form library and to define custom views for the forms.
You can use SharePoint Products and Technologies in combination with InfoPath to improve status reporting with a project team.
Members of a project team compose and submit project status reports on a weekly basis. The status report covers topics such as tasks, progress, issues, hours logged, and budget expended. The project manager reviews the status report submission for each team member and consolidates relevant information from all team members into a single report, which is then specified to the project sponsor.
Project teams use a generic status report document and store all status reports on a file share. The status report process typically operates as follows:
· Team Member Creates a Status Report The team member opens a local, possibly outdated, copy of the generic status report document. The team member types new information for the current reporting period.
· Team Member Submits a Status Report The team member posts the completed status report to a file share and sends an e-mail message to the project manager; alternately, the team member mails the status report to the project manager.
· Project Manager Collects Individual Status Reports The project manager checks both the file share and e-mail periodically, looking for new status reports.
· Project Manager Browses Status Reports The project manager must open a specific report to examine its contents, even if the project manager wants only a quick summary of the status report.
· Project Manager Searches Status Reports The file share is not included in an index by a search engine, so searches against the contents of the status reports are not possible.
· Project Manager Creates the Consolidated Status Report Once all reports are submitted, the project manager goes through a time-consuming, manual process to generate the consolidated status report for the project sponsor.
· Project Manager Submits the Consolidated Status Report The project manager posts the completed status report to a file share and sends an e-mail message to the project sponsor; alternately, the project manager mails the status report to the project sponsor.