Showing posts with label MOSS 2007. Show all posts
Showing posts with label MOSS 2007. Show all posts

Dynamic Meta Tags in SharePoint Site

Do you want to add dynamic Meta tags in SharePoint site??

DO you want to have SEO compliance site??

Below is the one of the good site to add dynamic Meta tags to each page in SharePoint site.

Click here to visit the site!!!

Error Solution during MOSS setup on domain controller

Error: At a time of MOSS set up on “T1” computer and SQL server on “T2” which is added in DC(Domain Controller) and in case if you got user privilege error then do following things:

Solution:

Add domain controller user in to the Administrator group on Computer in which you have privilege error.

Follow the step to give “Administrator” right:

1.Start >> Administrative Tools >> Computer Management >> Local User and Groups >> Groups
2.On right side panel right click on “Administrators” and click on Properties
3.Click Add and add domain controller user.

Happy Coding.. :)

STSADM Commands


One of the good link providing detailed reference for all STSADM command parameters.

Click here to view the original site

Is the above link useful to you? Let us know your feedback, it will help us to improve our posting(s). or You can send your feedback linkOblast.

Building a Hello World Web Part for Windows SharePoint Services 3.0

Building a Hello World Web Part for Windows SharePoint Services 3.0


Excerpts:
The purpose of this article is to demonstrate how to develop a very simple Hello World Web Part. The target application for this Web Part is Windows SharePoint services 3.0 (WSS), although it could of course be installed on Microsoft Office SharePoint Server (MOSS). The development of this assembly will be conducted on a system that does not have WSS/MOSS installed. The conclusion will demonstrate how to manually deploy and run this code, as opposed to using Visual Studio's built in deploy process.
This article is inspired by the work of Ted Pattison, whose video this writing is based upon and loosely follows.





Click here to read the original article.


Is the above link useful to you? Let us know your feedback, it will help us to improve our posting(s). or You can send your feedback linkOblast.

Configure anonymous access (Office SharePoint Server)

I was searching to provide Anonymous on my SharePoint Web Site, I just found this useful article at follwoing path:

Click here to View Article

Abstracts:

Configure anonymous access (Office SharePoint Server)

Updated: 2009-03-26

In this article:

Anonymous access enables users to find resources in the public areas of Web sites without having to provide authentication credentials.

About anonymous access

Internet Information Services (IIS) creates the IUSR_computername account to authenticate anonymous users in response to a request for Web content. The IUSR_computername account, where computername is the name of the server that is running IIS, gives the user access to resources anonymously under the context of the IUSR account. You can reset anonymous user access to use any valid Windows account.

NoteNote:

You can set up different anonymous accounts for different Web sites, virtual or physical directories, and files.

In a stand-alone environment, the IUSR_computername account is on the local server. If the server is a domain controller, the IUSR_computername account is defined for the domain.

By default, anonymous access is disabled by Office SharePoint Server 2007 when you create a new Web application. This provides an additional layer of security because IIS rejects anonymous access requests before they can ever be processed by Office SharePoint Server 2007 if anonymous access is disabled.

Enable anonymous access for a zone

Use the following procedures to enable anonymous access for a zone of a Web application. Within each Web application, you can categorize different classes of users into one of the following five zones:

  • Internet is the zone used for customers. Typically, the Internet zone is the only zone you would configure for anonymous access.

  • Intranet is the zone used for internal employees.

  • Default is the zone used for remote employees.

  • Custom is the zone used for administrators.

  • Extranet is the zone used for partners.

Enable anonymous access for a zone of a Web application

  1. From Administrative Tools, open the SharePoint Central Administration Web site application.

  2. On the Central Administration home page, click Application Management.

  3. On the Application Management page, in the Application Security section, click Authentication providers.

  4. On the Authentication Providers page, make sure the Web application that is listed in the Web Application box (under Site Actions) is the one that you want to configure. If the listed Web application is not the one that you want to configure, click the drop-down arrow to the right of the Web Application drop-down list box and select Change Web Application.

  5. In the Select Web Application dialog box, click the Web application that you want to configure.

  6. On the Authentication Providers page, click the zone of the Web application on which you want to enable anonymous access. The zones that are configured for the selected Web application are listed on the Authentication Providers page.

  7. On the Edit Authentication page, in the Anonymous Access section, select Enable Anonymous Access, and then click Save.

At this point, the Web application zone has been enabled for anonymous access.

Enable anonymous access for individual sites

Now you need to enable anonymous access for individual sites in the site collection.

Enable anonymous access for individual sites

  1. Go to the site on which you want to enable anonymous access and click the Site Actions menu.

  2. On the Site Actions menu, click Site Settings.

  3. On the Site Settings page, in the Users and Permissions section, click Advanced Permissions.

  4. On the Permissions page, on the Settings menu, click Anonymous Access. The settings for anonymous access lists three options:

    • Entire Web site   Select this option if you want to enable anonymous access for the entire Web site.

    • Lists and libraries   Select this option if you want to limit anonymous access to only the lists and libraries on your site.

    • Nothing   Select this option if you want to prevent anonymous access from being used on your site.

  5. Click OK.

At this point, your site is configured for anonymous access based on the options that you have selected.

Enable anonymous access for individual lists

If you select Lists and libraries, enable anonymous access for individual lists.

Enable anonymous access for individual lists

  1. Go to the home page of your Web site and, in the left navigation pane, click View All Site Content.

  2. Click the list on which you want to enable anonymous access.

  3. On the Settings menu, click List Settings.

  4. On the Customize List page, in the Permissions and Management section, click Permissions for this list.

  5. On the Permissions page, on the Actions menu, click Edit Permissions. A dialog box is displayed informing you that you are about to create unique permissions for this list. Click OK.

  6. On the Settings menu, click Anonymous Access.

  7. Select permissions for users who have anonymous access to the list, and then click OK.

At this point, users have anonymous access to the list you have configured. You can control whether users have anonymous access to other lists, the home page, or other pages on this site.




Getting a list of files from a MOSS document library using a SharePoint web service

A useful link that shows how to get list of files form doc lib of MOSS using webservice


Excerpts:

My challenge was simple. I needed to develop an SSIS package that
would download and extract data from
Publish Post
every Excel file held in document
libraries across several SharePoint sites. SSIS was the natural choice as
the data needed to be cleaned and validated before being imported into a
database. However, SSIS is not great with web services – especially in the data
flow. As I not worked with the SharePoint web services much, I started with a
good old Console application.
MOSS, or more accurately, WSS provides a whole host of web services to obtain information about
SharePoint sites. However, figuring out which method to invoke and what
parameters to pass is more problematic. Especially as many of the
parameters are chunks of Collaborative Application Mark-up Language (CAML) – a
dialect of XML developed by Microsoft specifically for use with SharePoint.
A False Start
My first console app simply obtained the GUID of the document library using the
GetListCollection() method of the Lists web service. The GUID was then
passed to the GetListItems() method which duly provided all documents and folders
at the top level of the document library. It then seemed logical to me to
recursively call the GetListItems() method using the GUID of each sub-folder.
On no, how wrong could I be! The GetListItems() method simply chokes on these
folder GUIDs.

On searching the internet I found many other incorrect forum posts and blog
entries about the same topic – but no working solutions. I also made an
extensive search of my eBook collection – but again no solutions – which
overall motivated me to write this blog entry.

The solution - RTFM
Well, if I had read the whole page in the manual, I would have got to the
solution earlierCrying. The key to my puzzle was
the QueryOptions XML fragment which
has both a Folder element and the all important <ViewAttributes
Scope="Recursive" /> element. Using these elements together, it is
possible to obtain a list of all documents in all subfolders in the list.
Indeed, it does not even bother returning the subfolder details!

So here is the code for my working C# sample.


using System;



using System.Collections.Generic;



using System.Text;



using System.Xml;



using System.Web.Services;



using System.Web;



using System.Net;





namespace ConsoleApplication1



{
class Program
{

static void Main(string[] args)
{



string siteUrl = @"http://yourserver/sites/yoursite";

string documentLibraryName = @"Shared
Documents"
;

SharePointList.Lists
wsList = new SharePointList.Lists();

wsList.Credentials
= System.Net.CredentialCache.DefaultCredentials;

WebProxy
proxyObj = new WebProxy("yourproxy", 80);

wsList.Proxy
= proxyObj;

wsList.Url
= siteUrl + @"/_vti_bin/lists.asmx";

// get a list of all top level lists

XmlNode
allLists = wsList.GetListCollection();

// load into an XML document so we can use XPath to query
content

XmlDocument
allListsDoc = new XmlDocument();

allListsDoc.LoadXml(allLists.OuterXml);

// allListsDoc.Save(@"c:\allListsDoc.xml"); // for debug

XmlNamespaceManager
ns = new
XmlNamespaceManager(allListsDoc.NameTable);

ns.AddNamespace("d", allLists.NamespaceURI);

// now get the GUID of the document library we are looking
for

XmlNode
dlNode = allListsDoc.SelectSingleNode("/d:Lists/d:List[@Title='"
+ documentLibraryName + "']", ns);

if (dlNode == null)

{

Console.WriteLine("Document
Library '{0}' not found!"
, documentLibraryName);

}

else

{

// obtain the GUID for the document library and the webID

string documentLibraryGUID = dlNode.Attributes["ID"].Value;

string webId = dlNode.Attributes["WebId"].Value;

Console.WriteLine("Opening
folder '{0}' GUID={1}"
, documentLibraryName, documentLibraryGUID);

// create ViewFields CAML

XmlDocument
viewFieldsDoc = new XmlDocument();

XmlNode
ViewFields = AddXmlElement(viewFieldsDoc, "ViewFields",
"");

AddFieldRef(ViewFields,
"GUID");

AddFieldRef(ViewFields,
"ContentType");

AddFieldRef(ViewFields,
"BaseName");

AddFieldRef(ViewFields,
"Modified");

AddFieldRef(ViewFields,
"EncodedAbsUrl");

//viewFieldsDoc.Save(@"c:\viewFields.xml"); // for debug

// create QueryOptions CAML

XmlDocument
queryOptionsDoc = new XmlDocument();



...
...
...
...


Click here to read full article.


Is the above link useful to you? Let us know your feedback, it will help us to improve our posting(s). or You can send your feedback linkOblast.

Deploying Assembly in GAC vs BIN


There are many differences between these two methods...

Read it here

Excerpts:

  • If you are frequently updating the Assembly,
    then you always better to deploy it in BIN.  Since, Assembly will be
    reloaded automatically just after the updating.    But when you update
    the Assembly in GAC, you have to restart the IIS (IISRESET) to grab the
    new version. The reason is GAC keeps the assembly in Cache.

  • When you deploy your Assembly on GAC then you can access
    the Assembly from any SharePoint web application. But when you deploy
    Assembly in web application’s BIN folder, then it can only access from
    the given web application. Anyway, if you have all-purpose web part,
    you better to deploy it in GAC and avoid the multiple Assembly
    deployments in BIN. 

  • If you have multiple versions of same Assembly, then you
    have to deploy it in GAC. Coz, GAC manages the multiple version of
    given Assembly, but BIN doesn’t.

Click here to read full article

SharePoint Workflow How-to Videos


Free Series of SharePoint Workflow How-to Videos


Excerpts:
This is the series of "How to" Document Workflow with SharePoint using
Visual Studio 2008 (using the .NET Framework 3.0 for backward
compatibility to Visual Studio 2005).  I have created video's that show
the most common requests that I have seen around MOSS/SharePoint 2007
workflow & document workflow.

For more details click here

or

http://www.sheltonblog.com/archive/2007/11/04/series-of-sharepoint-workflow-how-to-videos.aspx