Creating Web Applications, Site Collections and Sites in SharePoint 2010ProblemIn a recent tip, I discussed installing the Windows SharePoint service and SharePoint Foundation 2010. Once you have completed the installation, you need to understand the steps to create a web application, site collections and sites. In this tip, we cover the steps required to complete your SharePoint installation.SolutionIn this tip I am going to use SharePoint 2010 Central Administration to create a web application, site collections and sites. The same can be done programmatically by using PowerShell using the SharePoint libraries or object model / SharePoint APIs. In future articles, I will talk about how setup can be done programmatically.Web ApplicationIn the SharePoint hierarchy, a web application is the top tier. It is nothing but an IIS (Internet Information Services) website which is specifically configured to run as a SharePoint site and contains at least one or more site collections. While creating a web application you can either associate it with an existing application pool or you can create a new application to be associated with it. While creating your SharePoint web application you also need to specify a content database and details like authentication method used to connect to the content database. It is possible to have multiple content databases for different site collections for the web application. Using multiple databases makes it easier for content database management, backup, restore, etc...Site CollectionsAs I mentioned above, a web application needs to have one or more site collections. A site collection is a logical container for grouping sites and allows hierarchical arrangement of sites within it. A site collection has exactly one default top level site and may have many child sites. By default all sites of a site collection share navigation, security/permissions, templates and content types so you should plan to include all sites in single site collection if they all need to share these things. If needed, you can specifically change settings for a particular site if required.SitesA site collection has at least one parent site which is created by default when you create a site collection and may have many other sites within its hierarchy. A site allows us to organize and store all content in SharePoint, the content can be Lists, Libraries (Document Library, Picture Library, Report Library, Form Library etc...) Web pages, Web parts, Sites and Workspaces. Further a site can have child sites in its hierarchy.Enough on concepts, let's go through some examples: Go to START -> All Programs -> Microsoft SharePoint 2010 Products and click on SharePoint 2010 Central Administration, this will open the Central Administration site UI as shown below. Click on Manage web applications under Application Management in Central Administration page or under Web Applications in the Application Management page.  
On the web applications page, in the right pane you will notice all the web applications created so far. On top you will see an Office style ribbon which is a new feature of SharePoint 2010. Because we intend to create a new web application, simply click on the New option in left most side of the ribbon. 
This will open up a Create New Web
Application page, you need to specify different settings/parameters for your
new web application to be created. Some of these settings/parameters are described below:
Once you have specified all of the
required/optional parameters on the Create New Web Application page, simply
click on the OK button and wait for the web application to be created.
Once the web application is created you will see a screen like below. Click on
the
Create Site Collection link to create a site collection as the web application is
not usable unless you create at least one site collection.
 On the Create Site Collection page, first you need to specify the Title and Description for your new site collection. Next you need to specify the URL for your site collection in the Web Site Address section. Then you need to select one of the several available custom created templates which will be used as a blue-print to create your site collection. Next you need to specify the Primary Site Collection Administrator, specifying the Secondary Site Collection Administrator is an optional setting, but recommended as it allows secondary administrator to take charge of administration if the primary administrator is not available. Next if required, you can use the Quota template to restrict growth of your site collection to a certain limit.  Click on the OK button and you are done with the creation of the SharePoint web application. Click on the link and you will see your web application like this.  We normally create a site for each division/department/project. To create more sites, click on Site Action on the top left corner and you will see several options like this (this is another change from last SharePoint version where it used to be on top right side):  Click on New Site and specify different parameters (Title and URL) for your new site as shown below.  You can create as many sites as you want, for example I have created a couple of different sites for each department of the organization as you can see below.  Notes
Next Steps
|
|
Sponsor Information
Setup SharePoint Blogs Wikis and Announcements
Setup SharePoint Blogs Wikis and Announcements
In this article we will focus on three things -
1) How to setup SharePoint Blogs
2) How to setup SharePoint Wikis
3) How to setup SharePoint Announcements
How to setup SharePoint Blogs
Blogs (Web Logs) are similar to Wikis in that they allow users to add information, but unlike a Wiki, a Blog’s entries are dated and arranged in reverse chronological order (newest first). Under SharePoint, Blogs can contain any type of information including text, links, pictures, and other multimedia files.As with Wikis, SharePoint blogs are created using the Blog template in the New SharePoint Site window. To create a blog, follow these steps:
- Under Site Actions, click Create
- In the Web Pages list, click Sites and Workspaces
- Enter the title and description for the blog (remember these appear on each page, so useful descriptions should be employed). For the Web Site Address enter the address to be used for the blog.
- Under Template, click the Collaboration tab and select Blog:
- Under Permissions, set the Blog permission to their initial values
- Click Create
By default, users can add to blogs based on their SharePoint permissions, but you can overrule those permissions to allow only restricted access, or allow specific people to have edit capabilities. More commonly, you will want to have everyone on the system have access (and the ability to post to) your blogs, even if they do not have these permissions on the parent site. This is easy enough to accomplish by setting permissions for your Blog pages independently, instead of inheriting them from the parent.
The right side of the page allows users to add to the blog. Those with permissions can also edit and modify the blog.
To create categories for your blog, to allow subjects to be broken down more logically, follow these steps:
- Under Categories click the Add New Category link
- Enter the new category name and click OK
To delete a blog category, under the Category list click on the category name, then select Delete Item. The category will be removed.
How to setup SharePoint Announcements
Announcements are simply notices posted within SharePoint that are displayed and accessible for the whole team. Announcements appear on the home page by default, but can be placed anywhere in a site.Announcements are part of a list, and there are several list templates provided in SharePoint, as well as sample announcements. To create announcements in SharePoint, follow these steps
Backup and Restore a SharePoint Site Collection
Software development industry which develop projects based on SharePoint 2010, now trying to move into new approach what we called "Backup and Restore" rather than stick with the traditional approach where you create all the list site and other stuff with in the SharePoint project (VS project). specially when you are in a mid scale project time is a crucial factor and your client always expect to see something alive in daily basis.
When I join to the Navantis, my first project client wanted to finished it with in 4 weeks. Then, Navantis has decided to take Back up & Restore approach (which they haven tried before here in Sri Lanka).
In this approach, you are always asked to use, Out of the Box features (OOB). When you create list with in the site collection, when you create pages with in the site collection, master pages styles, almost everything including Data view web parts (by using SharePoint Designer). but if you are using some custom web parts, then you have to deploy them separately.
Open the Central Administrator (you should have privileged to CA). Start > All Programs > Microsoft SharePoint 2010 Products> SharePoint 2010 Central Administration
then you can see the Central Administration panel
Using SharePoint 2010 Central Administration Web site, under Backup and Restore, click perform a site collection backup
Then You get a Backup panel which has two main fields, which mandatory to be filled.
1) Site Collection path.
2) Backup path (where to save the Backup file)
and there is a option to select whether we are going to overwrite the existing file or not.
through the upper coner drop down you can choose the site collection
path which need to be Backup. then choose the site collection path (even
if it's in the manage path).
After that you need to enter the Site collection backup file path. Eg: C:\SharepointBackup\port80.bak, then click ok. But there are some concerns on this path.
1) The folder (in here SharepointBackup) should have Write privileged.
(other wise you'll get an Error when the service is started.)
2) Backup File name should have .bak extension.
3) If a Backup File already exist on the current lactation with a same
name then you need to check the "Overwrite existing file" option.
then you can see the backup service is starting.
Initially there are two options refresh and delete the job. if something
going wrong with the backup or you accidentally click ok button then
you can delete the backup service job.
but when the service got started. then you have to wait. and by clicking
refresh button you can see whether service job finished or not.
when it get finished. then you can go to the location, where your file
should be saved then you can see you backup file has been created.
This is how you can take entire site collection back up, which contain
all the files and settings, but as I mentioned earlier, If you got any
custom Web parts in your site collection. then you need WSP file also
for restoring process .
How to RESTORE a site collection using Backup File.
Restoring is also a easy process like the backup process. but you need
to concentrate many factors when you are going to restore the backup
file in to a new environment.
The following SharePoint Server Configuration should be exist on the server.
1)SharePoint farm version number should be equal or above, Means that
sharePoint version number of the restoring server environment should be
equal of higher than Backup server environment.
NOTE :
Using PowerShell - (get-spfarm).BuildVersion command then we can get the version number
PS C:\Users\thilinak> (get-spfarm).BuildVersion
Major Minor Build Revision
----- ----- ----- --------
14 0 4762 1000
Version number: 14.0.4762.1000
2)SharePoint should run the Profile Synchronization Service Application and User Profile Service.
3)Other features (Eg: Language Packs), if Required need to be installed in the Restoring environment.
NOTE:
Using SharePoint 2010 Central
Administration Web site, under Upgrade and Migration, click Check
product and patch installation status
Once you are done with the initial configuration. we need to create a
web application. on restore SharePoint environment. Or if you are going
to restore it into the same application then you need to creat a Manage
path . but make sure that, the path which you are going to restore
should be empty (No site collection Existed ).
NOTE:
Create Managed path in the Production web application (if it is not already exist or created)
Using SharePoint 2010 Central Administration Web site, under Application Managment, click Create Site Collections.
Then Go-to the Define Manage paths to
create one. Give a name to the path “eg : Main” select type as Explicit
inclusion , the added it and click ok.
Restore Back up file in to the manage path or Root path.
Using PowerShell –
restore-spsite -identity http://sharepointqa.example.com/main/ -path C:\ExampleIntranetBackup\
ExampleIntranetUATProductionRLS01\
ExampleIntranetBackup.bak
Then you will get the message asking the restore options. Give A for that (yes to all)
(replace “http://
ExampleIntranet.camoplastsolideal.com/main/ “ with valid production URL and replace “C:\
ExampleIntranetBackup\
ExampleIntranettUATProductionRLS01” with production back up file location)
Confirm
Are you sure you want to perform this action?
Performing operation "Restore-SPSite" on Target
"
http://sharepointqa.example.com/main/ ".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):A
Wait till the restoring process is finished (if the process is
successful it will display root path without given any red warnings)
If there is a site collection already exist in the given manage path
then, we need to do the restoring process with overwrite command.
(-Force)
[Warning: This will overwrite content and
everything. You might lose any existing content. Which not include in
the back up file. ]
Using PowerShell –
restore-spsite -identity http://sharepointqa.example.com/main/ -path
C:\ExampleIntranetBackup\ ExampleIntranetUATProductionRLS01\
ExampleIntranetBackup.bak -Force
Then you will get the same message asking the restore options. Give A for that (yes to all)
Confirm
Are you sure you want to perform this action?
Performing operation "Restore-SPSite" on Target
" http://sharepointqa.example.com/main/ ".
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):A
When you got any wsp (which contain custom web parts and other required dlls), then you should deploy it into the application.
WSP Deployment.
Add the required wsp (Internet.SharePoint.wsp) into the system using PowerShell –
add-spsolution -literalpath 'C:\Backup\ UATProductionRLS01\Internet.SharePoint.wsp'
(C:\Backup\ UATProductionRLS01\Internet.SharePoint.wsp is the wsp path)
Then using SharePoint 2010 Central Administration Web site, under System
Settings, click Manage farm solutions. Verify that wsp was added.
Deploy Required WSPs on production application.
SharePoint 2010 Central Administration Web site, under System Settings,
clicks Manage farm solutions. Then click on WSP which need to deploy.
Clicks Deploy Solution
Select application which you need to deploy (eg: http://sharepointqa.example.com) clicks ok
Now you are done with the restoring process. but event you are done you
might not be able to access the site,Backup file which extract form
development environment might include development users (who exist in
different domain) as site collection administrators. So we need to
replace them with production administrators.
SharePoint 2010 Central Administration Web site, under Application
Management, clicks Change site collection administrators. Then select
the site collection. And change the Administrators.
Then you can access the site with admin account.
Creating Anonymous sites in Sharepoint
Prerequisites
- Admin site should have been already created.
- user should have necessary privileged in central admin and the admin site.
Open the Central Administrator (you should have privileged to CA). Start > All Programs > Microsoft SharePoint 2010 Products> SharePoint 2010 Central Administration.
then you can see the Central Administration panel
Select Manage web application under the Application Management.
Then in the Application management panel Select the Admin Application Which you need to create Anonymous site by extending. when you select it you'll see that there's a Extend button which located in the top corner in the ribbon.
Setting The permission.
Login to the created site as site owner.
Click the site permission link. And click anonymous access.
Select as above and click [OK] button to see the site.
Now you complete the process and you'll be able to see the different between Authoring site and Anonymous Site.
When you logging to the Authoring site you'll see the Ribbon and Logging panel also you can do the editing stuff with in the site.
When you access the Anonymous Site.You don't get those features like ribbon and logging panel etc..
1. On the SharePoint Central Administration home page, click the Application Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section, click Create site collection.
3. On the Create Site Collection page, in the Web Application section, select a Web application to host the site collection from the Web Application drop-down list.
4. In the Title and Description section, type a title and description for the site collection.
5. In the Web Site Address section, select a URL type (personal or sites), and then type a URL for the site collection.
6. In the Template Selection section, select a template from the tabbed template control.
7. In the Primary Site Collection Administrator
section, specify the user account for the user you want to be the
primary administrator for the site collection. You can also browse for
the user account by clicking the Book icon to the right of the text box. You can check the user account by clicking the Check Names icon to the right of the text box.
8. Optionally, in the Secondary Site Collection Administrator
section, specify the user account for the user you want to be the
secondary administrator for the site collection. You can also browse for
the user account by clicking the Book icon to the right of the text box. You can check the user account by clicking the Check Names icon to the right of the text box.
9. Click Create to create the site collection.
|
Create a SharePoint site
1. On the SharePoint Central Administration home page, click the Application Management tab on the top link bar.
2. On the Application Management page, in the SharePoint Site Management section, click Site collection list.
3. On
the Site Collection List page, in the URL column, click the URL for the
site collection to which you want to add a site. The full URL path for
the site collection appears in the URL box.
4. Copy
and paste the full URL path into your browser, and then, on the home
page of the top-level site for the site collection, on the Site Actions menu, click Create.
5. On the Create page, in the Web Pages section, click Sites and Workplaces.
6. On the New SharePoint Site page, in the Title and Description section, type a title and description for the site.
7. In the Web Site Address section, type a URL for the site.
8. In the Template Selection section, select a template from the tabbed template control.
9. Either change other settings, or click Create to create the site.
10. The new site opens.
Introduction
SharePoint Timer Jobs are the heartbeat of any SharePoint Farm. They perform many important background tasks and generally consume substantial amounts of memory. Hence it becomes important to understand the ins and outs of these jobs - their location, scope, security aspects, customization aspects and performance related aspects. The SharePoint Timer Job Service is a windows service for The SharePoint Server. A Windows service is a long-running executable that runs in its own Windows session and performs specific functions that are designed ot not require user intervention. This service should not be confused with other SharePoint Service Applications like Excel Service Application, Word Service Application, Business Data Connectivity Service and so on. Those are web services as shown below where-as the SPTimer Job service is a windows service.  Physical Location The SharePoint timer job process - OWSTimer.exe - runs on all servers on a SharePoint farm. It does not have a SharePoint Admin GUI from where it can be stopped. We need to locate the Windows service and stop it manually on each server. Each timer job is either associated with a SharePoint Service Application or a SharePoint Web Application. If the service is provisioned for a web application, then only then will the related timer jobs be executed. A job can also be associated with a specific server and if the service is provisioned on that server then the job will run. The picture below depicts this.  Preferred Web Server for Timer Jobs Using a new option in SharePoint 2010 Central Administration, we can now set the preferred server where the timer service runs. To do this, click in the Manage Content Databases menu of the Application Management section of SharePoint Central Administration. Then click on the content database and scroll down to the setting for The Preferred Server for Timer Jobs. The web server can be chosen from the one's available in the farm as shown below. In the custom timer job we can also specify the server on which the job should run.  State machine workflows are saved in the content database. SharePoint executes workflow instances in one of two places depending on the last action. If the last action in the workflow was waiting on a user input, the workflow continues to execute on the Web front end where the user completed that input. If the workflow is continued from a delay timer or from an event being received elsewhere, it executes within the timer service. If the preferred server is mentioned – it executes on that server. Privileges of OWSTimer.exe and W3wp.exe The SharePoint timer job process - OWSTimer.exe - runs under the full trust execution model under the service account setup for it. This typically has higher permission levels than the IIS worker process - w3wp.exe. The application pool identity is essentially what the ASP .Net code of the portal site will be executing as. The Farm Account, which is used for the SharePoint 2010 Timer service and the Central Administration site, is highly privileged and should not be used for other services on any computers in the server farm. The account used by the Timer service should have access to the Content Database. We cannot elevate privileges in a SharePoint job so we are restricted to the permissions granted to the OWSTimer service account. Logical Scope of action All timer jobs have a scope of action - an object type upon which they are intended to work. This scope are reflected in the three values of the SPJobLockType enum: Job, None, and ContentDatabase.
The custom job should not be long-running since if it is then it will severely affect the performance of the farm. Tracking Locks Content Database Locks are tracked by an entry in a table - TimerLock - in each content database associating the database with a single server in the farm as shown below.  Acquisition and maintenance of content database locks for a server is handled by the Timer Service Lock Management job (job-timer-locks). Content database locks are handled at the server and database level, not at the individual job level. That is, a server which acquires a lock for a given content database takes responsibility for executing all jobs for that database. No other server in the farm will execute any jobs for that database. Job Locks - to ensure only one server runs each job with a lock on the scope of the farm; locks are associated with a single specific server via a table in the Configuration Database – TimerLocks as shown below.  Once taken by a server, the lock is typically held by the same server until the Timer Service on that server is stopped. By default, job locks time out after 20 minutes - which means that when all is functioning properly the Refresh job will ensure no lock ever times out. Custom Timer Jobs Timer Jobs in SharePoint have to be deployed in the GAC because the timer service is a separate process and runs as the full trust execution model. With the assembly deployed to the GAC, we can now deploy the timer job to the Windows SharePoint Services farm. In the next article we will see how to write a custom timer job and deploy it. How to Configure the Master Data Service in SQL Server 2008 R2
Master Data Services (MDS) is a new SQL
2008 R2 component that will help your organization effectively manage
master data in a centralized location.
Master Data Services uses business rules
to create basic workflow solutions. You can automatically update and
validate data and have e-mail notifications sent based on conditions you
specify. Business rules in Master Data Services are intended to manage
the most common workflow scenarios.
If your workflow needs require more complex
event processing, such as multi-tiered approvals or complex decision trees, you
can configure Master Data Services(MDS) to send data to a custom assembly that you
create, or to SharePoint to start a SharePoint workflow.
Each time you apply the start Workflow
business rule to your entity, records that meet the business rule conditions
are passed to the Service Broker queue of the Master Data Services database(MDS). At
regular intervals, the SQL Server MDS Workflow Integration service calls a
stored procedure in the Master Data Services database. This stored procedure
pulls the records from the Service Broker queue and passes them to the workflow
component that you specify.
Important
Note: The MDS(Master Data Services) Workflow Integration service that calls
your custom workflow code is meant to trigger simple processes. If your custom
code requires complex processing, complete your
processing either in a separate thread or outside of the MDS(Master Data Services) workflow
process.
Prerequisites
Before configuring Master Data Services to
work with a workflow, you must have the following software available:
·
1. SQL Server 2008 R2 Master Data
Services November CTP or later
·
2. Microsoft® Visual Studio® 2010
Beta 2 Ultimate or later
This software will be installed in the
following procedures.
Workflow
To send master data from Master Data
Services to a workflow, you will complete the following steps.
·
Search Service Configuration (Part 1)
[How to stop ?? admin content search through service]
I was reported some issue in one for my SharePoint project by client, it's regarding to the search functionality it said "the search function is displaying as a default search result. i.e. it is displaying admin section also."
. what they mentioned is when they search something they get result
which also related to the Admin section also like Central Administrator
or other test sites.
this project we have used default search web parts and core result web
parts to get and show the search results. means we cannot do many
changes in web part levels. so what we need to do is, Looking at the
search configuration.
Who Responsible .....
Service applications are responsible for many SharePoint services which
provide through the framework. when you consider on search basically
it's Search Service Application. so if you have a search service
application then you get at-least something for search result when you
search something . if you don't then you'll get something like following
image, with error massage "The search request was unable to connect to the Search
Service." when you search.
so if you don't have one just create one.
How To Create ...
Login to central admin using the farm admin credential Access to
“Manage service applications” under “Application Management” .
Then click on new and select Search Service application.
Then Fill the required field in the popup. Give name as a Search Service
Application (you can give any name you like, but this is much
professional).
you need to do some configurations, under the "Application Pool for Search Admin Web Service" and "Application Pool for Search Query and Site Settings Web Service".
You can configure these section with new application pool or
chose existing one (I recommend to chose existing one to eliminate
configuration errors.).
Then click OK, you get loading popup once it's creating.
Once it done you can search through the SharePoint Application but still
that's not our main issue. Ore issue is how to stop getting Admin
Content Search Results.
ISSUE ....
The issue is on the search configuration (Central Admin level). The
default configuration is (eg: All Site or Advanced Search) to get all
the result related for the farm level that’s why you get all result
including Admin level.
SOLUTION ...
To solve this issue we need to configure search service application and edit the Local SharePoint Site list.
for that we need to navigate to the Local SharePoint Site List .
Go to The Manage service Applications (I explain the path above). then click Search Service Application.
Click on “Content Sources” under “Crawling” in the left navigation
Click on the dropdown arrow “Local SharePoint sites” and click “Edit”
 
Under “Type start addresses below (one per line):” section you can see
all the site URLs including admin level URLs also configured.
Ensure the following values are set.
• Remove all the URLs which already configured,
• Give both <site> URL and the <anonymous site> URL as the “Start Address”
• For the schedule of “Full crawl” and “Incremental crawl”, click on “Edit Schedule” and use the default and click OK [Scheduling part is optional you can schedule it or keep it as none for both Full Crawl and Incremental Crawl ]
At the end of this process start full crawl of this content source.
Click on the dropdown arrow “Local SharePoint sites” and click “Start
Full Crawl”
Wait until the status part is “complete”. Then go to the application and
Search something. It will only give the Site or Application Contents.
SharePoint applications built in Iron Speed
Designer are easily deployed to your SharePoint server using the
procedure described below.
It is important to note that only applications
developed in the same version of Iron Speed Designer can be deployed to
the same Microsoft SharePoint hosting application (port). Web
applications are deployed to the common Layouts folder of the Microsoft
SharePoint server, and their respective DLLs are placed in the \bin
folder of the SharePoint hosting application (port). This means all DLLs
with the same name (such as BaseClasses.dll, AjaxControlToolkit.dll,
Ciloci.dll, Reports.dll, MySql.Data.dll, FredCK.FCKEditorV2.dll and
CarlosAG.ExcelXmlWriter.dll) are shared between all applications
deployed to the same SharePoint hosting application (port) and so your
applications must use the same version of these DLLs.
If you have applications developed in older release
of Iron Speed Designer you must first retract them from your SharePoint
server, migrate those applications to the current release of Iron Speed
Designer, and then re-deploy the updated applications to your
SharePoint server.
Deploying SharePoint Solution Packages (WSP) to your SharePoint server
Follow these steps to deploy an Iron Speed Designer Web Application for SharePoint:
Step 1: In Iron Speed Designer, use the
Deployment Wizard to create the SharePoint Solution Package (.WSP) file
in the application deployment folder, e.g.:
…\<MyApp_Deploy>\
In addition to the .WSP file, sample installation
(MyApp_addSolution.bat) and uninstallation (MyApp_removeSolution.bat)
batch files are also created.
See Deploying Applications with the Deployment Wizard for details.
Step 2: Copy the SharePoint Solution
Package (.WSP) file and the sample batch (.BAT) files to the SharePoint
server in a temporary location. For example, copy the files from the
deployment folder to C:\Temp on the SharePoint server.
Step 3: On the SharePoint server, edit the
sample installation batch file (.BAT) commands to match your situation.
Specify the location of the STSADM command on the SharePoint server.
Typically this is located in the Program Files folder under the
Microsoft Shared sub-folder, e.g.:
SharePoint 2010:
@SET STSADM="C:\Program Files\Common Files\Microsoft Shared\web server extensions\14\BIN\STSADM"
SharePoint 2007:
@SET STSADM="C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN\STSADM"
Step 4: Run the modified installation batch
(.BAT) file in a command window from the same folder where the .WSP and
the .BAT files are located. This adds the SharePoint Solution Package
(.WSP) file to the SharePoint solution store.
Note: You must have administrator rights on the
Microsoft SharePoint server to run the installation batch file;
otherwise you will get an ‘Object reference is not set to an instance of
an object’ error.
Step 5: Use the SharePoint Central Administration web page to deploy the solution.
SharePoint 2010
On the SharePoint server, double-click the
SharePoint Central Administration utility. Select System Settings on
the left vertical menu in the Central Administration click on Manage
farm solutions:
Select solution and select deploy solution:
On the Deploy To dropdown list, select the web
application where the solution will be deployed. You can also deploy
the solution to the farm by selecting "All content Web applications".
IMPORTANT: Make sure this web application does have
a default root site collection (/). If it does not you first have to
create it! Site collections are created on the Central Administration /
Application Management screen.
Once the solution is successfully deployed,
additional configuration steps are still needed to update the files
before the application will work.
SharePoint 2007
On the SharePoint server, double-click the
SharePoint Central Administration utility. Click the Operations tab,
and select Solution Management from the Global Configuration section.
Then select the solution you want to deploy.
 
Click the “Deploy Solution” button to begin the deployment.
On the Deploy To dropdown list, select the web
application where the solution will be deployed. You can also deploy
the solution to the farm by selecting "All content Web applications".
Any deployment errors will be shown here.
IMPORTANT: Make sure this web application does have
a default root site collection (/). If it does not, you first have to
create it! Site collections are created on the Central Administration /
Application Management screen.
Once the solution is successfully deployed,
additional configuration steps are still needed to update the files
before the application will work.
Step 6: Activate the SharePoint feature to complete the deployment.
SharePoint 2010
While In Central Administration Activate Feature…
Select your web application and click on Manage Features:
Now click Activate:
SharePoint 2007
Make sure you have selected correct Web Application in the top right corner. Then click Activate:
Step 7: Change the SharePoint Code Access Security to permit your application to run properly.
See Changing Code Access Security (CAS) for details.
Step 8: Install your application’s database stored procedures.
If your application uses stored procedures and its
database is on different production server than your development server
you might need to deploy your stored procedures to the production
server. Use the LoadStoredProcedures.bat file located in the
application’s StoredProcedures subfolder, e.g.:
SharePoint 2010:
\C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\MyApp3\StoredProcedures
SharePoint 2007:
\C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\MyApp3\StoredProcedures
See LoadStoredProcedures.bat for details.
Step 9: Run your application in SharePoint. The application is now available and can be run at a URL such as:
http://SharePointServer:34318/_layouts/MyApp (note ‘_’: 38318/_layouts/MyApp)
Step 10: (Optional.) Add navigation to your application.
See Adding navigation to your application for details.
Step11: (Optional) During deployment and
feature activation the following entry is added to the hosting
application’s Web config file in order to handle JavaScript properly:
<add verb="GET,HEAD" path="ScriptResource.axd"
type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions,
Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"
validate="false" />
Sometimes the hosting application’s Web.config file already has the following entry in the httpHandlers section:
<add verb="GET,HEAD,POST" path="*" type="Microsoft.SharePoint.ApplicationRuntime.SPHttpHandler, …/>
In this case, the SharePoint Solution Package (WSP)
adds the “GET.HEAD” entry after the “GET.HEAD.POST” entry which may
cause problems with proper JavaScripts execution because “GET.HEAD.POST”
will serve all requests, including those related to the ScriptResource.
In this case manually reverse the order of these entries.
See Also
How to Create a Custom Webpart in SharePoint 2013
Creating a Visual WebPart in SharePoint 2013 is different
than what it was available in SharePoint 2010. In SharePoint 2010,
Visual WebPart was made of a User Control and a Webpart file which were
used to define Controls and define properties of the webpart. In
SharePoint 2013 however the Visual WebPart template has Changed. Both
the User Control and WebPart classes are merged to Create one template.
Also, now you have one Visual WebPart template that can be used to
Create both Sandbox and Farm solution. In this post we will look at
detailed steps on how to create a Visual WebPart Farm solution and add
the wsp to your SharePoint site.
Step 1 - Create a SharePoint 2013 Visual WebPart Project.  Step 2 - Next add the Site Url and select deploy as farm.  Step 3 - The Solution should look like below.  Step 4 - Next add a TextBox in the ascx file and add assign it some text using the Code behind.  Step 5 - Once you add the Textbox save the project and click Start.  Step 6 - Next navigate to the site and verify if the solution is added to the Solutions gallery.You can also add the wsp from your project folder in the Solutions gallery and activate it. See below.  Navigate to Site Settings -> Solutions and upload the wsp. Make sure that the solution is Activated.  Step 7 - Next Add the Visual Webpart to the page. Create a page using “Add Page” in Settings menu and edit it. Next click on the Insert tab and select “Web Part”   Step 8 - Once you add the webpart, save the page and you would see the resulting webpart with a textbox. 
Ads by google
Jan 30, 2012Creating List Programatically in SharePoint 2010 using Visual Studio 2010
Today we will discuss about
creating List programmatically in SharePoint 2010 using Visual studio 2010.
If we are using only one instance of list we will follow this approach for creating list. open the visual studio 2010. File-->New-->Project Select C#-->SharePoint-->2010 Select Empty SharePoint Project  Deploy as a Form solution. Click on Finish  Project Solution structure is below for Empty SharePoint Project.  Select the project and click on F4 for the properties. Check for the Sandbox Solution property it is set to false now as we select the Trust level for SharePoint solution as From Solution. From here if you change that to Sandbox solution by setting property Sandbox Solution=”True” You can edit the site URL which you want to deploy using site URL property.  Right Click on Feature node and click on AddFeature.  It will add Feature1 to the Features node in the project. Change the Title according to your requirement .Here it is Devendra Employee List feature. I want this List available at site collection level to achieve this we need to change the Scope From Web to Site.  Now I am using Scope as web level only.  We will create a list using object model because we are going to use only one instance of this list so there is no point of creating list definition. To do that I will add a feature receiver. Add Event Receiver to the Feature1 node in the project.  Go ahead and add . Then uncomment the FeatureActivated event . We will write a code here which will add the Employee List whenever we activated this feature. using System;
using System.Runtime.InteropServices;
using System.Security.Permissions;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Security;
namespace Devendra_Feature_Event_Receivers.Features.AddList
{
///
add one more class called utilities.cs of type static. using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
namespace Devendra_Feature_Event_Receivers.Features.AddList
{
public static class Utilities
{
public static SPList EnsureList(this SPWeb web, string listTitle, string desc, SPListTemplateType lstTemplateType)
{
SPListCollection lstCollection = web.Lists;
SPList lstObj = (from SPList lst in lstCollection
where string.Equals(lst.Title, listTitle, StringComparison.InvariantCultureIgnoreCase) == true
select lst).FirstOrDefault
Add Item to the list data to the Employee List. Once we deactivate this feature the list will get deleted. Add one more class call utilities.  Once you click on the package .go to Bin folder of the project get the WSP file.  Add the solution using stsadm command. Click on run: type CMD Execute below command Stsadm –o addsolution –filename c:\Devendra_Feature_Event_Receiver.wsp. Open Central Admin to deploy the solution. Got o system settings -> Manage Form solutions  Deploy the solution. You can see the below screen solution deployed globally.  Open the site URL which we deployed the solution. Click on SiteActions-->Site settings Under Site Actions click on Manage Site Features.  Activate the feature Devendra Employee List Feature.  After activation we can see the Employee list and data inserted into the list.  Once you deactivate the feature list will get deleted. SharePoint-Journey for Administrators, Developers and users 
Subscribe to: Post Comments
(Atom)
Jan 30, 2012Creating List Programatically in SharePoint 2010 using Visual Studio 2010
Today we will discuss about
creating List programmatically in SharePoint 2010 using Visual studio 2010.
If we are using only one instance of list we will follow this approach for creating list. open the visual studio 2010. File-->New-->Project Select C#-->SharePoint-->2010 Select Empty SharePoint Project Deploy as a Form solution. Click on Finish Project Solution structure is below for Empty SharePoint Project. Select the project and click on F4 for the properties. Check for the Sandbox Solution property it is set to false now as we select the Trust level for SharePoint solution as From Solution. From here if you change that to Sandbox solution by setting property Sandbox Solution=”True” You can edit the site URL which you want to deploy using site URL property. Right Click on Feature node and click on AddFeature. It will add Feature1 to the Features node in the project. Change the Title according to your requirement .Here it is Devendra Employee List feature. I want this List available at site collection level to achieve this we need to change the Scope From Web to Site. Now I am using Scope as web level only. We will create a list using object model because we are going to use only one instance of this list so there is no point of creating list definition. To do that I will add a feature receiver. Add Event Receiver to the Feature1 node in the project. Go ahead and add . Then uncomment the FeatureActivated event . We will write a code here which will add the Employee List whenever we activated this feature. using System;
using System.Runtime.InteropServices;
using System.Security.Permissions;
using Microsoft.SharePoint;
using Microsoft.SharePoint.Security;
namespace Devendra_Feature_Event_Receivers.Features.AddList
{
///
add one more class called utilities.cs of type static. using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using Microsoft.SharePoint;
namespace Devendra_Feature_Event_Receivers.Features.AddList
{
public static class Utilities
{
public static SPList EnsureList(this SPWeb web, string listTitle, string desc, SPListTemplateType lstTemplateType)
{
SPListCollection lstCollection = web.Lists;
SPList lstObj = (from SPList lst in lstCollection
where string.Equals(lst.Title, listTitle, StringComparison.InvariantCultureIgnoreCase) == true
select lst).FirstOrDefault
Add Item to the list data to the Employee List. Once we deactivate this feature the list will get deleted. Add one more class call utilities. Once you click on the package .go to Bin folder of the project get the WSP file. Add the solution using stsadm command. Click on run: type CMD Execute below command Stsadm –o addsolution –filename c:\Devendra_Feature_Event_Receiver.wsp. Open Central Admin to deploy the solution. Got o system settings -> Manage Form solutions Deploy the solution. You can see the below screen solution deployed globally. Open the site URL which we deployed the solution. Click on SiteActions-->Site settings Under Site Actions click on Manage Site Features. Activate the feature Devendra Employee List Feature. After activation we can see the Employee list and data inserted into the list. Once you deactivate the feature list will get deleted. , SharePoint 2010, Solution 2 comments:
Create a Workflow using Visual Studio 2010
By ,
5 Jul 2012
IntroductionIn this article we can experiment with creating a Workflow using Microsoft Visual Studio 2010. Visual Studio along with SharePoint 2010 Extensions provides sophisticated development tools to enable Workflow development.Types of WorkflowsThere are basically two types of workflows inside Visual Studio:
State Machine Workflow will have states persisted in between. The state could be continued execution between machine restarts. In this example we are trying to create a Workflow which on activation updates the null Address column of the Manager list. (You need to have a Contact template named Manager.) Step 1: Create Sequential Workflow Project For the time being, we can start with a Sequential Workflow. Start Visual Studio and create a new project from the template SharePoint > Sequential Workflow.  In the next screen select the option Site Workflow as shown below:  In the next screen, leave the default option saying the user manually starts the Workflow. Click the Finish button to create the project.  You will get the following screen once the project is created.  Step 2: Create Activity We need to create an Activity to perform our job. What is an Activity?A Workflow consists of a series of Activities. We can add Activities using the Toolbox. There are different types of Activities like Code Activity, SendEmail, etc. For our example we are using the more functional Code Activity. Drag and drop a Code Activity from the toolbox. You can locate this from the v3.0 group inside Toolbox.  Step 3: Add code for the Activity Now we need to add code for this Activity. Double click on the codeActivity1 item shown above. Place the following code in the appearing code view. private void codeActivity1_ExecuteCode(object sender, EventArgs e)
{
using (SPWeb web = SPContext.Current.Web)
{
SPList list = web.Lists["Manager"];
foreach (SPListItem item in list.Items)
{
if (item["Address"] == null)
{
item["Address"] = "PLEASE SET THE ADDRESS!";
item.Update();
}
}
}
}
Step 4: Build and Deploy the SolutionNow we are ready to build and deploy the solution. Right click on the solution and use the Build and Deploy command.  Step 5: Execute the Workflow inside SharePoint Now we are ready to test the Workflow inside SharePoint. As the Workflow was created as a Site Workflow it will be accessible for all the Lists and Libraries. You can click the Lists link inside the site.  Now click on the Site Workflows link. You will get the following screen.  Before executing the Workflow, you need to create a Manager item with Address not assigned. Click on the highlighted button and your workflow gets executed. Wait for a while and you can see the invalid manager record is updated with the message.  This concludes our article on Workflow using Visual Studio. NoteFor debugging the Workflow, you can set a breakpoint and use the Debug command of Visual Studio. When the Workflow is executed, the breakpoint will get hit.Workflows overview (SharePoint Server 2010)Published: May 12, 2010The workflow feature in Microsoft SharePoint Server 2010 enables solution architects, designers, and administrators to improve business processes. Fundamentally, a workflow consists of two things: the forms that a workflow uses to interact with its users and the logic that defines the workflow’s behavior. Understanding how workflows are created requires knowledge about both. In this article:
Workflow overview
Workflows in SharePoint Server 2010 enable enterprises to
reduce the amount of unnecessary interactions between people as they
perform business processes. For example, to reach a decision, groups
typically follow a series of steps. The steps can be a formal, standard
operating procedure, or an informal implicitly understood way to
operate. Collectively, the steps represent a business process. The
number of human interactions that occur in business processes can
inhibit speed and the quality of decisions. Software that simplifies and
manages this "human workflow" enables the automation of interactions
among groups who participate in the process. This automation results in
more speed, overall effectiveness of the interactions, and often a
reduction in errors.
You can model business processes by using flow charts, such as those created using Microsoft Visio 2010 and can represent business processes by using workflow terminology. You can automate business processes, such as document approval, by associating a workflow with data in SharePoint Server 2010. For example, you can create a workflow to route a document for review, track an issue through its various stages of resolution, or guide a contract through an approval process. One problem that many IT departments face when implementing business processes that require participation of information workers is that those processes do not integrate with the way people actually work. For a business process to be effective, it must be integrated with the familiar, everyday tools and applications used in the workplace so that it becomes part of the daily routine of information workers. In the electronic workplace, this includes integration with e-mail, calendars, task lists, and collaboration Web sites. Benefits of using workflows
The primary benefits of using workflows are to facilitate business processes and improve collaboration.
Business processes that enterprises use depend on the flow of information or documents. These business processes require the active participation of information workers to complete tasks that contribute to their workgroup's decisions or deliverables. In SharePoint Server 2010, these types of business processes are implemented and managed by using workflows. Examples of business processes that could be facilitated by workflows include:
Automating business processes
Businesses depend on business processes. Although those
processes often involve software, the most important processes in many
organizations depend on people. Workflows can automate interactions
among the people who participate in a process to improve how that
process functions, increase its efficiency, and lower its error rate.
Many processes can benefit from automated support for human interactions. Examples include the following:
Workflows improve collaboration
Workflows help people collaborate on documents and manage
project tasks by implementing business processes on documents and items
on a SharePoint site or site collection. Workflows help organizations
follow consistent business process practices. Workflows increase
organizational efficiency and productivity through management of the
tasks and steps involved in those business processes. Workflows speed up
decision making by helping to ensure that the appropriate information
is made available to the appropriate people at the time that they need
it. Workflows also help ensure that individual workflow tasks are
completed by the appropriate people and in the appropriate sequence.
This enables the people who perform these tasks to concentrate on
performing the work instead of on the work processes.
For example, on a SharePoint Server 2010 site, you can create a workflow to be used with a document library to route a document to a group of people for approval. When the author starts this workflow, the workflow creates document approval tasks, assigns these tasks to the workflow participants, and then sends e-mail alerts to the participants. When the workflow is in progress, the workflow owner or the workflow participants can check progress on the Workflow Status page. When the workflow participants complete their workflow tasks, the workflow ends, and the workflow owner is automatically notified that the workflow has finished. Predefined workflows
Microsoft SharePoint Server 2010 includes the following
predefined workflow templates that address common business scenarios:
When a site user starts a workflow on a document, item, or site, the user might have the option to further customize the workflow by specifying the list of participants, a due date, and task instructions. You can also make a copy of a predefined workflow to use as a starting point when creating a custom workflow. Sample workflow scenario
Imagine that you work for Adventure Works, a sports store
franchise that sells bicycles worldwide. This company has sales
representatives that visit different countries to help new franchisees
open new sports stores.
The scenario described in this section is one where an expense report is submitted for approval. If the expense report is for less than $5,000.00, a manager is required to approve, disapprove, or forward it. If the expense report is equal to, or more than, $5,000.00, a manager must review the expense report, comment on it, and then if the manager recommends approval, it is forwarded to a vice-president, who must approve or disapprove it. In this scenario, the expense report form is an InfoPath Forms Services form. The workflow is a sequential Approval type of workflow project created in Microsoft SharePoint Designer 2010, and is composed of both automated tasks and tasks that require human action. The workflow is running on SharePoint Server 2010.
In this sample expense report scenario, the business rules are always the same. This workflow solution defines the manager and vice president approvers, defines the business logic for the routing of the workflow, and predefines the content of the notifications. However, many real-world applications have complex business rules. Routing for approval can depend on many business variables. Notifications can also change, depending on other variables. For example, imagine that in the same expense reporting solution, you have to route the expense report to as many as ten managers, depending on the expense purpose, the expense total, and the date of submission. Additionally, depending on the expense purpose, the content of the notifications sent by the workflow contain some small differences. This means that there can be multiple workflow solutions with different routing levels and notifications. Microsoft SharePoint Server 2010 enables you to create and implement workflow solutions to meet the business needs of your organization. It does this by leveraging the workflow design and customization features of SharePoint Designer 2010 and Microsoft Visual Studio 2010 Premium Edition, the prototyping functionality of Microsoft Visio 2010 used with SharePoint Designer 2010, and the capabilities of the Microsoft Office system.
Workflow types: Declarative and compiled
An important distinction to understand about workflows is
whether they are a declarative workflow, such as those created using
Microsoft SharePoint Designer 2010 or a compiled workflow, such as those
created using Visual Studio 2010. A declarative workflow is a workflow
that is built from conditions and actions that are assembled into rules
and steps, and that sets the parameters for the workflow without writing
any code.
A compiled workflow, like declarative workflows, can also be built from conditions and actions without the workflow author actually writing code but also enable the workflow author to add custom code to the workflow. Regardless of whether a workflow author adds custom code to a code-centric workflow, the most important distinction to understand is the difference in the way that declarative and compiled workflows are run on the server. A compiled workflow is stored on a server running SharePoint Server 2010 as a precompiled dll file whereas a declarative workflow is deployed on a server running SharePoint Server 2010 as an Extensible Object Markup Language (XOML) file and compiled in the content database each time an instance of the workflow is started. For more information about the Microsoft supported tools for authoring workflows, see Choose a workflow authoring tool (SharePoint Server 2010). Workflow templates
When creating a custom workflow using SharePoint Designer
2010, you can choose to create a workflow that will only be used with a
specific list, library, content type, or site. Alternatively, you can
choose to create a reusable workflow template, which can be associated
with multiple lists, libraries, content types, or sites.
Workflow associations
SharePoint Server 2010 takes advantage of the Workflow
Foundation runtime. One or more workflow templates, each containing the
code that defines a particular workflow, can be installed on a server.
Once this is done, an association can be created between a specific
template and a document library, list, content type, or site. This
template can then be loaded and executed by the SharePoint Server
2010-hosted Workflow Foundation runtime, creating a workflow instance.
Like all Workflow Foundation workflows, those based on SharePoint Server 2010 rely on Workflow Foundation runtime services. The Workflow Foundation standard persistence service allows the state of a persisted workflow to be linked with the document or item, and allows for long-running business processes that can span days, months, or years. SharePoint workflows can be associated with lists, libraries, and content types. Reusable workflows created using Visual Studio 2010 can also be associated with sites. The following table describes the minimum permissions required to associate a workflow.
Office client interoperability
Implementation of business processes that require the
participation of information workers is often hampered by the fact that
those processes are rarely integrated with the way people work. For a
business process to be effective, it must be integrated with the
familiar, everyday tools and applications used in the workplace so that
the process becomes part of the daily routine of information workers. In
the electronic workplace, this includes coordination with e-mail,
calendars, task lists, collaboration Web sites, and client applications
such as Microsoft Outlook and Microsoft Word. This integrated approach
is implemented in workflows based on SharePoint Server 2010.
SharePoint Server 2010 delivers workflow applications through a technology called Windows Workflow Foundation. People interact with these workflows in the Web browser and in the 2007 Microsoft Office system and the Microsoft Office 2010 suites through programs such as Microsoft Word. SharePoint Server 2010 uses Windows Workflow Foundation functionality to deliver several workflows that automate common business processes. Additionally, custom workflows can be created by using various tools, and the workflows are then associated with SharePoint libraries, lists, content types, and sites. Create a Custom Page Layout in SharePoint 2013
This is a Step-by-Step tutorial on how to Create a Custom
Page Layout in SharePoint 2013.We will use the new Design Manager to
Create a Layout (from an existing one) and then edit it in one of the
editors like Notepad.Once the layout is Created and Uploaded to Master
Page Gallery, you can edit the generated html file in an editor of your
choice and upload it back to the Master Page Gallery.
If you need to add SharePoint Field Controls or any other SharePoint Controls such as search box,navigation etc in your custom layout, you can use the Snippet gallery to Copy the required field Control code and paste it into your custom Layout’s html file.In this post however we will only look at an example of Creating a Custom Page Layout and using it to Create a Custom Page. If you want to edit the page layout and add a code from Snippet gallery, see the upcoming post on ‘Add Snippets in Layout Page using Snippet gallery in SharePoint 2013′. Before you begin make sure that you have Publishing Feature enabled on your site and you see “Deisgn Manager” under Look and feel. Lets look at the detailed steps - 1. Navigate to Site Settings -> Design Manager (under look and feel).  2. Next in Design Manager select “6. Edit Page Layouts” and then “Create a page layout”  3. Now Create a Custom Page layout using the Article Page Content type.  4. When the Layout is Created, it gets available in “Edit Page Layouts” list and the “Master Page gallery” of the site.The Layout Page will be in Drafts mode until you publish it as a major version.  5. Next Edit the New Layout Page and save the Changes.In SharePoint 2013 for every Layout page two files – .aspx and html are created by default.  For making Changes to the Custom Layout, you need to download the html file (see above – Custom page Layout.html) of your layout page and make Changes to it.The modified html file is then saved back to the MasterPage Page gallery where the corresponding .aspx file gets updated automatically. For editing, see the detailed post on How to add Snippets from Snippet Gallery in Layout Pages in SharePoint 2013 6. Once you have updated and saved the Layout page, you need to Publish the Layout page as a major version to make it available in Layouts list.  7. Finally, Create a new Page with your Custom Layout. Navigate to Site Content in Site Settings and then Open the “Pages” gallery.   Click on the ‘FILES’ tab and select Page.  Finally Create a new Page with your Custom Layout.  To know more about Editing the Layout Pages and how to add a SharePoint Field Control in it, look for our next post tomorrow on how to ‘Add Snippets in Layout Page using Snippet gallery’.
Ads by googleated Posts
Quick Tip: Suppress the display of submitted search terms in a SharePoint 2013 search box web part by Pete Hurth
The Problem: A search results page can accept the k= parameter in the URL which passes the query to a search box web part. Unfortunately this is sometimes not desired as the query can be a bit ugly.
 One solution might be to use a= in the URL parameter. This suppresses the display; however it seems to also break the search results. So… not an ideal solution. In previous versions of SharePoint you could simply check a box in the search box web part properties called "Display Submitted Search". See this blog for a description of how to fix this in previous versions of SharePoint: http://strandsofsharepoint.blogspot.com/2013/12/use-a-url-parameter-when-passing-hidden.html. This does not work in SharePoint 2013 since the option is no longer available in the web part (the search web parts have been completely redesigned to use display templates). To make this same change you must edit the control display template used by SharePoint to render the search box. I'm assuming you have at least a passing familiarity with display templates. If not, see the following article for an overview on working with SharePoint display templates: http://msdn.microsoft.com/en-us/library/office/jj945138(v=office.15).aspx Now that you know all there is to know about display templates… navigate to: /_catalogs/masterpage/Display Templates/Search/ and locate "Control_SearchBox.html". Do not edit the default display template. It's bad karma to do so. Instead make a copy of this file (not the .js file, just the html file). Rename it to something appropriate like "Control_SearchBox-nosub.html". |
Note:
2 comments: