Blog Easyciel for .NET
blog.easyciel.net author="Patrick Rabian" about="c#, sharepoint, biztalk, team system resources" more="news, samples, tips for .NET world's developers !"

Identify Sharepoint installed version

Tuesday, 31 January 2006 11:54 by prabian

For WSS : go to ‘Administration site’ and list ‘Virtual servers’. The WSS version number is displayed for extended site.

For SPS : go to ‘Add and Remove programs’, select ‘Sharepoint Portal Server 2003′ and click on the ‘Support link’ on the left.

Windows SharePoint Services
or SharePoint Portal Server 2003 versions
 WSS SPS2003
Original version 6.0.2.5530? 11.0.5704.0
Service Pack 1 6.0.2.6361 11.0.6715.0
Pack 1 Security Update post-service Windows
SharePoint Services		 6.0.2.6411 N/D
Service Pack 2 6.0.2.6568 11.0.8126.0

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   SharePoint
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Articles, tools on .NET

Saturday, 28 January 2006 01:22 by prabian

An Overview Of The New Services, Controls, And Features In ASP.NET 2.0
I you need a resume on ASP.NET 2 features, look at this MSDN article : http://msdn.microsoft.com/msdnmag/issues/06/00/ASPNET20Overview/default.aspx

Security enhancements on .NET 2.0
http://msdn.microsoft.com/msdnmag/issues/06/00/SecurityBriefs/default.aspx

Tools every C# developer should know about
http://geekswithblogs.net/gyoung/archive/2006/01/26/67191.aspx

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   .NET Projects
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Custom drop down menu like SharePoint does

Tuesday, 24 January 2006 18:41 by prabian

Interesting article at : http://aspadvice.com/blogs/matthias/archive/2005/12/16/14350.aspx

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   SharePoint
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Problem with ‘AlternateCSS’ attribute of ‘Project’ (ONET.XML)

Tuesday, 24 January 2006 15:38 by prabian

If you are working with site definition in Sharepoint, maybee you would like to change the CSS style. In the Sharepoint documentation, it is specified the add ‘AlternateCSS’ attribute in the main tag ’Project’ of the ONET.XML.
So, as I tried and NOTHING changed !

When you look at ‘default.aspx’ root file in your site definition folder, you will find :

<Link REL=”stylesheet” Type=”text/css” href=”/_layouts/<%=System.Threading.Thread.CurrentThread.CurrentUICulture.LCID%>/styles/ows.css” mce_href=”/_layouts/<%=System.Threading.Thread.CurrentThread.CurrentUICulture.LCID%>/styles/ows.css” >

….whereas, in an administrator page as ’settings.aspx’ (from _layouts/….), you will find something like this (and it works) :

<SharePoint:CssLink DefaultUrl=”/_layouts/<%=System.Threading.Thread.CurrentThread.CurrentUICulture.LCID%>/styles/ows.css” runat=”server”/>

So, a solution is to replace the first version with the second in all files from site definition’s hierarchy (101 files should be updated for a total of 141).

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   SharePoint
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Customizing SharePoint Context Menus

Tuesday, 24 January 2006 09:43 by prabian

How to modify the javascript code of a context menu directly from Sharepoint Web interface by using the Content Editor Web Part. “…The Content Editor Web Part enables custom HTML and script to be added to a page and delivered to the browser…”

Show me this article ! from Mark Bower

Download sample named “SharePoint Send Mail & Hello World Custom Menu Item Web Parts” on www.gotdotnet.com

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   SharePoint
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Service Pack 2 for Windows SharePoint Services (WSS)

Monday, 23 January 2006 16:37 by prabian

Upgrading
to .NET Framework 2.0

Although it is not required that you upgrade to ASP.NET 2.0, there are many improvements
to the development platform and environment in that release of the framework.
The Windows SharePoint Services 2.0 object model and SOAP services are fully
supported for use in ASP.NET 2.0 applications.

To leverage ASP.NET 2.0 Web Parts in Windows SharePoint Services, a wrapper Web
Part must be written to make the ASP.NET 2.0 Web Part appear to be a Windows
SharePoint Services Web Part. After this is done, your ASP.NET 2.0 Web Part
should function normally within your Windows SharePoint Services pages. Wrapper
Web Parts will not be required in the next version of Windows SharePoint Services
or the next version of SharePoint Portal Server (code named Office “12″
SharePoint Servers), which both natively support ASP.NET 2.0.

In most SharePoint Portal Server installations, it is better to continue to use
the current technologies that are supported natively in the product — that
is, ASP.NET 1.0 and .NET Framework 1.1 — rather than mixing the platforms.


Implications
for Web Part development and deployment

The following set of frequently asked questions is taken from the SharePoint
Thoughts blog, and provides a good set of answers to what we suspect will
be the most commonly considered ways of exploiting this new development:

With Windows SharePoint Services with SP2, will the SharePoint worker process run
in ASP.NET 2.0?
Yes, it can. Alternatively, you are not forced to use ASP.NET version 2.0.

What is the advantage of running my virtual server in ASP.NET v2.0?
After you’re running in the ASP.NET version 2.0 space, the corresponding CLR
libraries are available. Your code will be able to take advantage of new features
in addition to the security and performance enhancements found in the new
runtime.

If my my virtual server continues to run in ASP.NET 1.1, can my code call another
assembly that was compiled in .NET v2.0?
No. CLR fundamentals state that you can’t “upstream” the CLR version
from the current running version. In other words, if you decide to run with
version 1.1, you are limited to loading and working with assemblies compiled
with version 1.1 or earlier.

If my virtual server runs in ASP.NET 2.0, will my Web Part code need to be recompiled?
No. This is basically the reverse scenario of the last question, but the answer
is not the same. “Downstream” is possible; therefore, any existing
1.x compiled assemblies should continue to work.

Can I create a virtual server/directory that runs in ASP.NET 2.0 and have my SharePoint
site running under ASP.NET 1.1 call into the pages and Web services exposed
by the ASP.NET 2.0 site?
Yes.

Can I use ASP.NET 2.0 Web Parts on Windows SharePoint Services with SP2?
Not as Web Parts. Given that all Web Parts can be treated as standard Web
Form controls, ASP.NET 2.0 Web Parts can be added to pages running in Windows
SharePoint Services with SP2, just not within Web Part zones. In this manner,
such Web Parts will behave no differently than standard Web Form controls,
and should have been written with this contingency in mind. Out of the box,
Windows SharePoint Services will not use any ASP.NET 2.0 constructs. At the
core level, SP2 will not change the rendering behavior of Windows SharePoint
Services. In other words, Windows SharePoint Services will not suddenly gain
the ability to use master pages or ASP.NET 2.0 Web Parts. Until the next major
release, your only course of action is to take an approach of encapsulating
an ASP.NET 2.0 Web Part with a Windows SharePoint Services Web Part designed
for this purpose. You might want to investigate http://www.smartpart.info
for an example of this technique.

Can I use Visual Studio 2005 to compile my Windows SharePoint Services Web Parts?
Visual Studio 2005 is bound to the 2.0 runtime; therefore, the answer is yes
if you are using SP2; otherwise, the answer is no.

Will I need to specify assembly redirection or runtime information for my Web Part
assemblies?
No.

Will I need to specify assembly redirection or runtime information anywhere else?
Yes. If you want to deploy Web Part packages that contain CLR version 2.0
compiled Web Part assemblies (that is, SharePoint Web Parts compiled by using
the new CLR), you will need to create a *.config file for stsadm.exe that
specifies the following:

<?xml
version=”1.0″ encoding=”utf-8″ ?>
<configuration>
<startup>
<supportedRuntime version=”v2.0.50727″ /> <!– update the
version # once .Net v2.0 is released –>
<supportedRuntime version=”v1.1.4322″ /> <!– this is the
version number for .Net v1.1 –>
</startup>
</configuration>

The
config file (appropriately named stsadm.exe.config) will need to be placed
next to stsadm.exe. If you don’t add the config file, you will get the error
message, “Version 1.1 is not a compatible version.”

Extracted from : office.microsoft.com

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5
Categories:   SharePoint
Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

Add a Custom List to SharePoint - a foray into CAML

Friday, 20 January 2006 16:24 by prabian

Table of Contents

  1. Step 1: What exactly do you need to accomplish?
  2. Step 2: Create a new custom site definition
    1. The Definition Copy
    2. The WEBTEMP.XML Copy and Modification
    3. The Results
    4. Technical Resources
  • Step 3: Create the custom list definition
      1. The Definition Copy
      2. The SCHEMA.XML Modification
      3. Adding the List to the ONET.XML file
      4. The Results
      5. Technical Resources
    1. Step 4: Add the custom list definition to the default page of a new SharePoint site
        1. Adding the List to the ONET.XML file Configuration and Module
        2. The Results
        3. Technical Resources
      1. Technical Resources: Composite List

        2. From : http://heathersolomon.com/blog/articles/1300.aspx

    Be the first to rate this post

    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Categories:   SharePoint
    Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

    The Dangers of using Front Page 2003 with SharePoint Sites

    Friday, 20 January 2006 16:00 by prabian

    I always use “site definition” and so, I never use “Front Page”…
    It’s just about ghosting !

    Ghosted ressource : linked to the original definition file.
    Unghosted ressource : modified ressource stored in database.

    Ted Pattison explain it to you in this word document : UsingFPwithSP.doc

    Be the first to rate this post

    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Categories:   SharePoint
    Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

    Several Sharepoint’s tips from “lancer227″

    Thursday, 19 January 2006 15:04 by prabian

    • How to share information between two webparts.
    • How to display a combo which shows all the sites.
    • How to add a custom property in Search Results.
    • That’s How to get doc values (properties) previous to a document library event.
    • User roles created automatically with a custom site definition.

    Go to : Several Sharepoint’s tips

    Be the first to rate this post

    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Categories:   SharePoint
    Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed

    Useful scaling information with SharePoint

    Wednesday, 18 January 2006 18:01 by prabian

    Read this article about “SharePoint Scaling Limits” on http://markharrison.co.uk/blog/2004/09/sharepoint-scaling-limits.htm

    And this one from Microsoft support : http://support.microsoft.com/kb/827930/en-us

    Two tables from the first article :

    SharePoint items Maximum Note
    Site collections (Database scope) 50,000 Total throughput degrades as the number of
    site collections increases
    Web sites (Web site scope) 2,000 The interface for enumerating subsites of a
    given Web site does not perform well much
    beyond 2,000 subsites
    Web sites (Site collection) 250,000 You can create a very large total number of
    Web sites by nesting the subsites. For example, 100
    sites each with 1000 subsites is 100,100 Web sites
    Documents (Folder scope) 2,000 The interfaces for enumerating documents in
    a folder do not perform well beyond a thousand entries
    Documents (Library scope) 2 million You can create very large document libraries
    by nesting folders
    Security principals (Web site scope) 2,000 The size of the access control list is limited
    to a few thousand security principals, in other words users and groups in
    the Web site
    Users (Web site scope) 2 million You can add millions of people to your Web
    site by using Microsoft Windows security groups to manage security instead
    of using individual users
    Items (List scope) 2,000 The interface for enumerating list items does
    not perform well beyond a few thousand items
    Web Parts (Page scope) 100 Pages with more than 100 Web Parts are slow
    to render
    Web Part personalization (Page scope) 10,000 Pages with more than a few thousand user personalizations
    are slow to render
    Lists (Web site scope) 2,000 The interface for enumerating lists and libraries
    in a Web site does not perform well beyond a few thousand entries
    Document size (File scope) 50 MB The file save performance degrades as the file
    size grows. The default maximum is 50 MB. This maximum is enforced by the
    system, but you can change it to any value up to 2 GB (2047 MB) if you have
    applied Windows SharePoint Services Service Pack 1.

    SPS Features Typically Maximum supported
    or tested    		 Maximum is hard
    limit
    Portal sites (full) 2 15 x
    Portal sites (child) 10 100 X
    Areas 1,000 10,000  
    Best Bets 1,000 25,000  
    Area depth 5 20 X
    User profiles 50,000 1,000,000  
    Audiences 500 10,000  
    Audience memberships 500,000 5,000,000  
    SSO credentials 100 100,000  
    Search indexes 3 32  
    Content sources 25 250  
    Search scopes 25 250 X
    Indexed documents per content index 100,000 5,000,000  
    Indexed documents 2,500,000 20,000,000  
    Thesaurus entries 1,000 10,000  
    Alerts 50,000 1,000,000  
    Team sites 10,000 250,000  
    Personal sites 10,000 250,000  

    Moreover, read this article on Microsoft Support KB : Error messages when you delete or rename large folders or sites in Windows SharePoint Services

    Read particularly this information about scaling limits

    Windows SharePoint Services users cannot delete a folder, a document library, a site, or a site collection if either of the following conditions is true:

    • The folder, the document library, the site, or the site collection contains over 40,000 subfolders and documents.
    • The size of the folder, the document library, the site, or the site collection is larger than (but not equal to) 2 gigabytes (GB).

    Windows SharePoint Services users cannot rename a folder, document library, site, or site collection if either of the following conditions is true:

    • The folder, the document library, the site, or the site collection contains over 10,000 subfolders and documents.
    • The size of the folder, the document library, the site, or the site collection is larger than (but not equal to) 500 megabytes (MB).

    The calculation of the maximum number of objects that a folder, a document library, a site, or a site collection can contain includes the root folder, the subfolders, the documents that are contained in the root folder, and the documents that are contained in the subfolders.

    For example, a document library that contains 9,993 documents exceeds the maximum limit of 10,000 items. The number of items that is calculated for the document library is actually 10,001 because the number of items includes the number of documents (9993), the number of files in the Forms folder (6), the forms folder (1), and the root folder of the document library (1).

    Be the first to rate this post

    • Currently 0/5 Stars.
    • 1
    • 2
    • 3
    • 4
    • 5
    Categories:   SharePoint
    Actions:   E-mail | del.icio.us | Permalink | Comments (0) | Comment RSSRSS comment feed
     
    Powered by BlogEngine.NET | Enhanced by GravityCube.net