Dot Guru

In which server SharePoint solutions needs to be deployed? Add-SPSolution will move your solution to SP Admin database Install SP-Solution will create a timer job to push all feature files to 14/15 hive DLL's to GAC Web.Config changes etc to the Front end servers where you have "SP Web Application service" running. So it doesnot matter which server you are using to deploy your WSP. Since the solution functionalities will be always executed on your front end server, your app server doesnot need the WSP artifacts.

Sand Box Solution:   1.       Introduced in SP2010 and are partially trusted. 2.       Solution must be deployed by site collection administrators and above 3.       Solution is deployed to site collection Solution Gallery 4.       Runs in a separate process – SPUCWorkerProcess.exe which isolates from SharePoint worker process 5.       Dlls are copied to file system only, when a request made to sandbox objects for the first time. This is taken care by SPUCHostService.exe 6.       Strict CAS policy is defined for sandboxed solutions, limiting the functionality 7.       Control is given to site collection administrators instead of relying on Farm admins 8.       Allows you access services using CSOM.   Limitations: 1.       Code can...

There are different types of pages available in SharePoint Foundation 2010. I am addressing here primary page types, Application Page and Site page. Application Pages: Application pages are stored in physical file system, i.e., \14\Template\Layouts\. Since stored in physical location, these are accessible across Web Application We can add server code as In-line or code behind Do not have dynamic Web Parts or Web Part zones but can have Static web parts Application pages are not cusotmizable by end users. These are controlled by web application administrators Generally these pages are used when custom code is required, and should be available through out the web application 7. These are parsed in direct mode., Compiled initially and cached. Site Pages: When a site page is created first time a reference is stored in content db. When end user customizes the page, reference in content db is replaced with site page. These are customizable using browser...

Features in SP 2010 Deployment scope of Features Farm, Web Application, Site Collection, Web Site The Feature scope is determined by the setting of the Scope attribute in the Feature element defined in the feature.xml file A sample Feature element tag is given below: Id = "F62C96CF-79FD-44be-8882-E9BFBD199184" Title = "Feature Title" Description = "Feature Description" Version = "1.0.0.0" Scope = "Site" Hidden = "false" > Web Site scoped Feature (Scope="Web"): A Web Site scoped Feature is one that can be activated only at the individual Web site level. List templates, list instances, custom actions, event receivers, etc are the some common elements for web site scoped features. Web Site scoped features can be activated by using: Run the following STSADM command: stsadm - o installfeature - name FeatureFolderName – url http : //servername/site/subsite Site ...

What is Feature Stapling in SharePoint Development

MS.NET: Oops A to Z •  How to implement two interfaces when they have a method with the same signature? •  Explain the scenario where you will use Abstract class, Interface? And explain the differences? Differences between stored proc and a function Is sqlconnection managed or unmanaged code? Explain the reasons? Explain about Garbage collection? How will you call explicitly garbage collection? How will you handle unmanaged code with the help of Garbage collection? What namespaces are used in ADO.NET What is the difference between delete() and remove() methods of Datagrid row? How to use unmanaged code in a .net application? Explain about design patterns? What are application blocks? Difference between [Proctected Internal] and Internal? Difference between data reader and dataset? Optimization techniques •  Application level •  Database level •  how to find out the performance bottlenecks in deployed application and what a...

SPs are Databse subroutine used to perform tasks within the database, whether it be to INSERT, UPDATE, DELETE, SELECT, send return values, send output parameters, send e-mail, call command line arguments, encapsulate business logic, enforce data integrity, or any combination thereof. They are compiled when first run, and the query plans are stored and cached by SQL Server's optimizer, and those cached plans are swapped out depending on frequency of usage. View: • To hide the complexity of the underlying database schema, or customize the data and schema for a set of users. • To control access to rows and columns of data. • To aggregate data for performance. UDFS: Set of statements which must return an object considered as function. In general, UDFs can be a serious source of performance issues. Also, UDFs cannot be used for DML operations (INSERT/UPDATE/DELETE), cannot use non-deterministic functions, cannot use dynamic SQL, and cannot have error-handling (e.g. RAISERROR)....