Saturday, October 29, 2011
Ans: Web Part Page Gallery is the default gallery that comes installed with SharePoint. Site Gallery isspecific to one site. Virtual Server gallery is specific to that virtual server and online gallery aredownloadable web parts from Microsoft.
Q. What is the difference between a site and a web?
Ans: A site in sharePoint is a site collection. It is an object of SPsite class in sharepoint. While a Web is simply a blank site within that site collection. Web is a Part of SPweb class, thus represents a site within a site collection.
Q. When to use Diffrent Site Collections?
Ans. An Individual Site collection offers following :
For the Users:
Dedicated Recycle bins
Dedicated usage Reports
Distributed administration (site collection administrators)
Dedicated search scopes, keywords, and best-bets
Custom feature deployments
Dedicated language translation maintenance
Dedicated galleries for web parts, master pages, content types, site columns, site templates, and list templates
Dedicated shared libraries, such as site collection images and site collection styles
Dedicated real estate (Self Containment)
For the IT Administrators:
Site quota templates
Database maintenance options
Backup / Restore abilities
InfoPath forms services global template targeting
Q. why to use different site collections
1. Site quotas is one of the reasons. The issue is the recycle bin is based on site collections and the quota for a site collection. If everyone shares a site collection, then they share the recycle bins storage size.
2. Delegated Security and distributed administration is the next big thing. For eg, you have a IT department that doesn't know who should be able to see what content, besides how it should be organized. This is the job of the content owners and users. SharePoint site collections offers IT the ability to create a site collection for a project, team, department, document, or whatever the needs are, then assign an owner and hand it off to them.
3. In addition to these two points is the need to separate the content between databases.
Q. What is Authentication and Authorization.
Ans : An authentication system is how you identify yourself to the . The goal behind an authentication system is to verify that the user is actually who they say they are.
Once the system knows who the user is through authentication, authorization is how the system decides what the user can do.
Q. What are Security methods(Authentication methods) available in sharepoint 2007.
Ans : Out of the box", SharePoint 2007 supports nine authentication methods. NTLM (short for NT Lan Manager, which is simply the Windows authentication that everyone is familiar with) and Kerberos (also a Windows "standard" authentication) are offered during installation, but I recommend to get started with NTLM, as Kerberos requires "special configuration by the domain administrator", while NTLM works without further hassle.
Q. Can you name some of the tools used for SharePoint Administration?
Ans. Some of the tools Used for SharePoint Administration are
* Axceler's ControlPoint (Version : ContolPoint 3.5 )
Description : ControlPoint 3.5 helps enterprises adopt and embrace microsoft sharepoint more than ever before. ControlPoint 3.5 boasts powerful new capabilities that give enterprises more control over their configuration and deployment of SharePoint while strengthening their SharePoint security.
* DocAve (Latest Version : DocAve Software Platform v5.3)
Description : DocAve Software Platform v5.3, is considered the industry's most comprehensive software solution for SharePoint backup and recovery, administration, archiving, auditing, replication, reporting, compliance, and migration.
* Nintex Workflow(USed for Workflow )
Description : Nintex Workflow 2007 enables organizations to build complex workflow processes quickly and easily using a web browser interface. Nintex Workflow 2007 empowers users across the organization to automate business processes, review workflow activities and automate common SharePoint administrative tasks.
Q. Can a web application use few shared services like search,audience from ssp?
Ans. No, it has to use all the shared services in that SSP.
Thursday, June 16, 2011
When you're in a command prompt, sometimes you need to navigate to the 12 Hive directory. But no one wants to type the directory path to c:\Program Files\Common Files\Microsoft Shared\web server extensions\12. Wouldn't it be easier if you could just type the following to get there?
c:\Program Files\Common Files\Microsoft Shared\web server extensions\12
I'd sure say it is! The other thing is I almost always want to be within a Visual Studio Command Prompt to have easy access to things like SN.EXE and GACUTIL.EXE. A VS Command Prompt is nothing more than a simple batch file. I've created my own batch file that executes the VS Command Prompt batch file and sets the %12HIVE% variable to the 12 Hive directory. Here's how:
- Create a new file called SharePointCommandPrompt.cmd and insert the following text in it (if you're on a 64 bit system, you'll want to make the appropriate changes):
echo Setting 12HIVE environment variable.
set 12HIVE="C:\Program Files\Common Files\Microsoft Shared\web server extensions\12"
"C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat" x86
- After saving the file, create a new shortcut with the following target:
%comspec% /k ""c:\[Path To The File You Just Created]\SharePointCommandPrompt.cmd""
- To put a cherry on top, drag the shortcut onto your Quick Launch toolbar... should work like a champ!
To try it out, click the shortcut and type CD %12HIVE% at the command prompt. You should change directories to the root of the 12 Hive.
Saturday, April 30, 2011
Advantages of User control
There are three primary advantages to user controls when dealing with SharePoint. They are: familiarity, reusability, and development speed.
One of the keys to development is managing the degree of change that the team is put through as it transitions from technology to technology. Part of managing that change is minimizing it where possible. This is one of the reasons that user controls are such a good solution for many organizations. User controls are a core ASP.NET construct, they are something that developers are likely already familiar with — or at least aware of. This familiarity increases the knowledge reuse coming into the project, which keeps morale high, improves productivity, and improves reuse of the experience after the SharePoint project.
Another way user controls are advantageous is that they can be used with other ASP.NET-based solutions. They aren't explicitly tied to SharePoint. If for some reason in the future you decide that SharePoint isn't the right platform for the solutions you're building — or you decide you need to reuse the technology in another non-SharePoint project — you have that capability.
Direct support by Visual Studio for a visual interface for user controls — as opposed to manually adding in controls through code — is a great advantage in development speed. Having a visual look and feel instantly available makes the process go faster.
*Debugging is faster too, as you can construct testing harnesses that fully exercise and instrument the user control. Web Parts are essentially only runable from within SharePoint. This means that you must deal with all of the SharePoint infrastructure while trying to debug.
Maintenance is also easier and faster with User Controls, primarily because they are easier to understand and debug. The net of this is that developing with user controls is substantially faster than developing a Web Part for everything but the most trivial implementations
A good example of an Application Page is the default Site Settings page: every site has one, and it's not customizable on a per site basis (although the contents can be different for sites).
With application pages, you can also add in line code.