Friday, September 24, 2010

check this out

1) -- How to crate & place themes in Share point sites?
2) -- How can u call the custom CSS in Share point?
3) -- How many types of permissions in Share point?
4) --How to change the default date format (mm/dd/yyyy) to jan-01-2008? 
5) -- BDC? Why to go for BDC?
6) --In how many ways backup and restore the SharePoint site?
7) -- What is Audience targeting? 
8) --Can u write the code to copy the existing list to another list?
9) --What is the use of STSADM tool? 
10-- How to create & delete list using object data model? 
11--Did u create any workflows in ur project ? what are the workflows u created ( and either by using sharepoint designer or visualstudio)
12--Difference between Seq.work and statemac. Workflow ? 
13--How do u debug the workflows ( how do u handle exceptions) ? 
14--Can we generate the strong name key to private assembiles ? 
15--How can u deploy the webpart to sharepoint gallery Sub question : ( I don’t want to put the assembly in GAC i want that is as a private assembly ) Why it s necessary to mention that is a safecontrol ?

SP interview questions

What are the benefits of Microsoft Office SharePoint Server 2007?

* Provide a simple, familiar, and consistent user experience.
* Boost employee productivity by simplifying everyday business activities.
* Help meet regulatory requirements through comprehensive control over content.
* Effectively manage and repurpose content to gain increased business value.
* Simplify organization-wide access to both structured and unstructured information across disparate systems.
* Connect people with information and expertise.
* Accelerate shared business processes across organizational boundaries.
* Share business data without divulging sensitive information.
* Enable people to make better-informed decisions by presenting business-critical information in one central location.
* Provide a single, integrated platform to manage intranet, extranet, and Internet applications across the enterprise.

Questions to keep in mind.
Q. How would you retrieve large number of Items form the list ?

Ans. To retrieve large number of items with a better performance we can either use SPQuery or PortalSiteMapProvider Class. Read More with Examples
Retrieving large number of Items from sharepoint list
Q. What Do you know about SharePoint Object Model?

Q. What is the difference between a Site Definition and a Site Template?

Ans. Site Definitions are stored on the hard drive of the SharePoint front end servers. They are used by the SharePoint application to generate the sites users can create. Site Templates are created by users as a copy of a site they have configured and modified so that they do not have to recreate lists, libraries, views and columns every time they need a new instance of a site.

Q. Where do you deploy the additional files used in your webpart, like css or javascript files, and how do you use them in your WebPart?

Ans. You can deploy the css or javascript files in _layouts folder in SharePoint's 12 hive. To use them in your webpart, you need to first register them to your webpart page and then specify a virtual path for the file for e.g. _layouts\MyCSS.css See Code examples at Using External Javascript, CSS or Image File in a WebPart.

Q: When should you dispose SPWeb and SPSite objects?

Ans. According to the best Practices you should always dispose them if you have created them in your code. You can dispose them in Finally block or you can use the "Using" clause, so that they gets disposed when not required. If you are using SPContext then you need not dispose the spsite or spweb objects.

Q.What is the main difference between using SPListItem.Update() and SPListItem.SystemUpdate()?

 

Q. When do you use SPSiteDataQuery ?

Ans. You can use SPSiteDataQuery when you need to extract data from more than one list\library in your site colletcion. The data is extracted on the basis of the query you write and is
returened as a Datatable. You can also specify the GUID for the lists\libraries you want to query against.

Q. How do you create a Custom action for an item in a list ?

Ans. This can be done by adding a new feature into SharePoint. You would need to use customaction tag in your elements.xml file and will have to set various properties like imageurl or UrlAction for your customaction. You can later add this feature into sharepoint using stsadm install feature command.

Q. How will you deploy an existing asp.net webapplication or website in SharePoint?

Ans. You would need to wrap the web application in a solution package in order to deploy it in 12 hive or say ShraePoint. It is recommended to create a feature first, and then wrap everything in a Solution package. See example Depoly a Custom aspx Page in SharePoint

Q. What are content types?

Ans. A content type is a flexible and reusable WSS type definition (or we can a template) that defines the columns and behavior for an item in a list or a document in a document library. For example, you can create a content type for a leave approval document with a unique set of columns, an event handler, and its own document template and attach it with a document library/libraries.

Q. Can you add a Cutsom Http Handler in SharePoint ?

Ans. Yes, a Custom httphandler can be deployed in _layouts folder in SharePoint. Also, we need to be register the handler in the webapp's webconfig file.

Q. While creating a Web part, which is the ideal location to Initialize my new controls?
Override the CreateChildControls method to include your new controls. You can control the exact rendering of your controls by calling the .Render method in the web parts Render method.

Q. How do you return SharePoint List items using SharePoint web services?
Ans.
In order to retrieve list items from a SharePoint list through Web Services, you should use the lists.asmx web service by establishing a web reference in Visual Studio. The lists.asmx exposes the GetListItems method, which will allow the return of the full content of the list in an XML node. It will take parameters like the GUID of the name of the list you are querying against, the GUID of the view you are going to query, etc.

Q. How Do you deploy Files in 12 hive when using wspbuilder or vsewss?

Ans. Typically, you can add these files in the 12 hive folder structure in your project. In Vsewss however, you will have to create this structure manually.

. What are event receivers?

Ans. Event receivers are classes that inherit from the SpItemEventReciever or SPListEventReciever base class (both of which derive out of the abstract base class SPEventRecieverBase), and provide the option of responding to events as they occur within SharePoint, such as adding an item or deleting an item.

Q. When would you use an event receiver?

Ans. Since event receivers respond to events, you could use a receiver for something as simple as canceling an action, such as deleting a document library by using the Cancel property. This would essentially prevent users from deleting any documents if you wanted to maintain retention of stored data.

 

Q. If I wanted to restrict the deletion of the documents from a document library, how would I go about it?

Ans. You would create a event receiver for that list/library and implement the ItemDeleting method. Simply, set: properties.Cancel= true and display a friendly message using Properties.Message("How can u delete this... Its not your stuff!");

What is a SharePoint site definition? What is ghosted (uncustomized) and unghosted (customized)?

SharePoint site definitions are the core set of functionality from which SharePoint site are built from, building from the SiteTemplates directory in the SharePoint 12 hive. Site definitions allow several sites to inherit from a core set of files on the file system, although appear to have unique pages, thereby increasing performance and allowing changes that happen to a site propagate to all sites that inherit from a site definition. Ghosted means that when SharePoint creates a new site it will reference the files in the related site definition upon site provisioning. Unghosted means that the site has been edited with an external editor, and therefore the customizations are instead stored in the database, breaking the inheritance of those files from the file system.

 

Reference links:

http://www.sharepointsecurity.com/sharepoint/sharepoint-development/sharepoint-developer-interview-questions-answers/
http://mysharepointwork.blogspot.com/2010/05/sharepoint-2007-moss-2007-developer.html

Sharepoint interview questions

What is Sandbox solution? Posted by: Shankul2784 | Show/Hide Answer When user writing custom code then it is not trusted, its failure causses on entire site. So the sandbox solution concept is used. In that case program is only written for particular site & solution is uploaded in the same site. The solution size limit is decided at the time of site creation & if size increases or code showing bad performance then it is easy to administrator to stop the working of solution. What is the difference between Sandbox solution & farm solution? Posted by: Shankul2784 | Show/Hide Answer We can create sandbox solution for particular site but not for the entire site collection or farm. It is not applicable for farm solution. There are some restriction while creating the sandbox solution. Why we use the properties.current.web instead of SPContext.Current.web in event receiver? Posted by: Shankul2784 | Show/Hide Answer When we deploy project from Visual studio then we can use the SPContext.Current.web but when we use the powershell to activate or deactive the feature then we have to use properties.current.web beacuse there is no access of browser here. Which are default master pages in Sharepoint 2010? Posted by: Shankul2784 | Show/Hide Answer 1. v4.master - This is default master page. 2. default.master - this is used to support the 2007 user interface 3. minimal.master 4. simple.master- it is used for accessdenied.aspx, confirmation.aspx, error.aspx, login.aspx, reqacc.aspx, signout.aspx & webdeleted.aspx pages. What is the difference between CustomMasterUrl & MasterUrl? Posted by: Shankul2784 | Show/Hide Answer MasterUrl is used to change the layout of all use end pages but CustomMasterUrl is for changing the layout of admin side pages. what is web part?and type Posted by: Sagarp | Show/Hide Answer Web Parts are the fundamental building blocks for Share Point user interface, and with them we can build and integrate many different types of applications.In share point also be create custom web part using .oscx control steps create custom web part 1.create web part project copied .oscx control and build application.place .dll file in GAC .reset IIS. 2.go 12 hive _layout folder create folder past your .oscx control 3.go inetpub ->wwwroot->wss->open Your site ->web con fig->create safe control write assembly information of web part application 4.open sharepoint site ->site action-site editing->Galleries ->web part->new Add your web part. follow few web part in WSS 3.0 Content Editor Web Part Data View Web Part List View Web Part Image Web Part Members Web Part . Page Viewer Web Part What are the types of input forms that can be created for a workflow ? Posted by: Sagarp | Show/Hide Answer You can create four different types of input forms including 1. An association form 2. An initiation form 3. A modification form 4. A task edit form. what is CAML? Posted by: Neeks | Show/Hide Answer CALM tands for Collaborative Application Markup Language and is an XML-based language that is used in Microsoft Windows SharePoint Services to define sites and lists, including, for example, fields, views, or forms, but CAML is also used to define tables in the Windows SharePoint Services database during site provisioning. What are the advantages of SharePoint Portal Services (SPS) over SharePoint Team Services (STS)? Posted by: Neeks | Show/Hide Answer harePoint Portal Services (SPS) has MUCH better document management. It has check-in, check-out, versioning, approval, publishing, subscriptions, categories, etc. STS does not have these features, or they are very scaled back. SharePoint Portal Services (SPS) has a better search engine, and can crawl multiple content sources. STS cannot. STS is easier to manage and much better for a team environment where there is not much Document Management going on. SPS is better for an organization, or where Document Management is crucial. References" http://www.dotnetfunda.com/interview/ShowCatQuestion.aspx?category=87

Thursday, September 23, 2010

Installing IIS with vista Home edition

You just cannot install complete IIS 7.0 on Windows Vista Home Basic Edition, that seems silly right. Sad, but true.

Tuesday, September 21, 2010

Sharepoint - Case Study

1. Use of default Publishing features: We created a site collection using Collaboration Publishing Portal site template, in that way we got what we wanted for ECM including Page Publishing with Approval mechanism. Case study http://www.sharepointfix.com/2009/01/case-study-ecm-for-enterprise-wide.htm 2. Site Structure and Architecture: We had a single site collection with various internal departments as Sites under One site collection like : we had Home as the top level site and then HR, Finance, Administration, Business Units etc as our sub-sites within the site collection. We had a single server farm, one dedicated search server and one SSP configured. We had separate Virtual machines configured for Development, Content Management and Production environment respectively with WSS SP 1 and MOSS SP 1. We had identified a few Content Managers from within the respective units, who would maintain their respective sites for managing/uploading content in lists/libraries. 3. Capacity Planning: We had a Cord Core processor with sufficient hard-disk and 4 GB RAM, our capacity planning was based on the fact that we had a target audience of 3000 users within the organization. 4. Use of custom Master page, custom Page Layouts and custom styles: We actually created a copy of default.master, a copy of Page Layout from Blank Web Part page and a copy of Core.css from Style Library using SharePoint Designer, after creating copies of each of them we restructured the entire master page and added some new styles in our custom style sheet, we had to hide certain Content Placeholders from Master page(you should not delete these placeholders, instead place them all in an control with visibility as hidden to avoid errors), we then added a new Left Web part Zone to our Custom Page Layout, all using SharePoint Designer But doing all the above mentioned customizations using SPD was not a viable option as all the pages would then become un-ghosted (customized) and everything would be then stored into SharePoint Content Databases, instead we copied all the three files we developed with SPD into the file system and deployed it as a feature using WSP builder, so we could get both the benefit of Visual design using SPD and Ghosting (un-customization). So we now have our custom master page, custom page layout and custom style sheet on the file system, making it more scalable across farms, as all of them have been deployed as features, we also have them under our source control now. 5. Use of .NET User Controls: We used a lot of pure .NET user controls within the custom master page, for e.g. the organization wanted to display names of its employees having their birthdays on that day, in a dynamic ticker which would change each day, the birthday data was exported from excel to SharePoint list using the Excel Add-In for MOSS 2007, click on the link to download, 6. List Items as Pop-ups: We also made a .aspx page which will accept List Item Id to be displayed, List Name and Column Name as query string parameters, this was deployed in the LAYOUTS folder of the 12 hive structure, it meant that it will now be accessible to any site within the site collection due to the virtual directory _layouts which is mapped to the physical folder LAYOUTS, so if I have to call the .aspx page from the HR sub-site, I would call it in the following way: /HR/_layouts/ShowListDescription.aspx?ItemId=1&ListName=NewsEvents&ColumnName=NewsDescription We used to link the .aspx page as a Read More… pop-up in the List View web part, so that it could show the description/details of that particular list item in a pop-up window. 7. Daily Back Up and Restore: Since, we had a separate Content Managers Environment for uploading data into lists/libraries, we would actually perform back-up and restore drills each day to move updated content from Content manager’s environment to Production environment. We created back-up and restore batch scripts, it would have to be run manually each day by a dedicated Administrator as he had to copy .bak files and move it across the server and then restore. Later on we found that this could have been achieved without manual intervention using Content Deployment Jobs, to download this white paper, visit: http://technet.microsoft.com/enus/library/cc627268.aspx 8. Third party web parts: We used various free third-party web parts like the Quick a. Surveys web part for Surveys & Polls (http://code.msdn.microsoft.com/QuickSurveys) b. Zone Tabs web part to show web parts in a tabbed manner (http://code.msdn.microsoft.com/zonetabs) c. RSS Feed Reader web part from CodePlex: http://www.codeplex.com/FeedReader/Release/ProjectReleases.aspx?ReleaseId=19830 We also customized the existing Content Query Web part to include URL’s from Link List, here is an excellent article: http://www.helloitsliam.com/archive/2007/11/06/moss2007-–-link-lists-and-the-content-query-web-part.aspx 9. Use of Visual Studio workflows: We had to pick up email addresses from a master list based on the site context and send an Email alert to the appropriate contact, whenever a Suggestion/Feedback is entered from the portal; we used Visual Studio Workflows and deployed it as a SharePoint feature. 10. Search Scopes: We created context based Search Scopes like HR, Finance, Admin, Purchase using Central Administration and then added them to our Site Collection using Search Scopes setting at the top level site collection. 11. Stress Testing Tool: We used Microsoft Stress Testing tool in order to load test concurrent users, we created 100 dummy users and test scripts for all the pages, load tested our application for about 12 hours, we found RPS rate was good and the application didn't even crashed once, when the concurrent stress testing was going on. All throughout i was reading Andrew Connel's book on Web Content Management for Sharepoint, (Go to Andrew Connels bookshelf) Heather Solomon’s blog for Custom master pages (http://www.heathersolomon.com/blog/) During my development phase, i got some help from John Holliday in relation to Disposing Sharepoint objects while using Sharepoint API. Liam Cleary's wonderful posts also help me profoundly.

Monday, September 6, 2010