Stress Testing SharePoint with Application Center Test (ACT)#

James Edelen wrote a nice posting about stresstesting Sharepoint:

"Testing SharePoint is and incredibly important part of capacity planning. There is nothing worse than spending weeks or months implementing a solution and it not being able to handle the required load. Using a tool like ACT will enable you to test your hardware before production in order to ensure that it will perform as expected. It will also let you more easily discover bottlenecks in your system before going live. You can watch performance counters on your servers while stress testing to find bottlenecks."

Read full article

Tuesday, March 29, 2005 5:20:42 AM UTC #    Comments [3]  | 

 

U2U CAML Query Builder and Execution Tool Released #

Via Patrick's blog:

"What is the CAML Builder?

CAML itself is the abbreviation of Collaborative Application Markup Language. It is an XML-based query language that helps you querying, building and customizing Web sites based on Windows SharePoint Services. The XML elements define various aspects of a WSS site. In the first version of our CAML Builder tool, only the query aspect of CAML is worked out. The tool will help you build, test and execute your CAML queries.

We provide you with two things:

  1. A Windows application you can use to connect to your portal or team site and build your CAML query string in a WYSIWYG manner. (U2UCamlCreator.exe)
  2. A small assembly you can reference helping you with the execution of your CAML query string within your code. (U2U.SharePoint.CAML.Server.dll)

CAML builder is downloadable from our SharePoint site. You just unzip the file and start working with it. We will work out an official article with more guidance info on the stuff you can do with CAML and the tool. But for the moment, if you want to start, here is a small walkthrough demonstrating the possible use of the tool."

Great work (again) at U2U!

Tuesday, March 29, 2005 5:16:02 AM UTC #    Comments [1]  | 

 

Extending and Enhancing the SharePoint Portal Server Search User Interface#

I've mentioned it during the Office DevCon 2005 but it's finally here on GotDotNet: Extending and Enhancing the SharePoint Portal Server Search User Interface user sample!

Sample code from the Office Developer Conference 2005 session "Extending and Enhancing the SharePoint Portal Server Search User Interface". This code includes contributions made by Mike Schneider to the "Creating a Site Context Search Box" article/code on MSDN including: Search Box (HTC Menu and multiple Portal configs) and Search Results (wildcards, boolean and hit highlighting).

Especially the last one, I've been waiting for. Great!

Friday, March 25, 2005 8:38:03 AM UTC #    Comments [0]  | 

 

Sharepoint downloads on GotDotNet#

Paul mentions some Sharepoint downloads at GotDotNet. The downloads are actually demo's from a webcast by Mike Fitzmaurice (March 21st):

  • SharePoint List Browser/Copier Demo Application - An example of what can be done using a WinForms smart client to access SharePoint sites via SOAP.
  • Example of how to upload a file to a SharePoint library via the FrontPage RPC protocol - Example of how to upload a file to a SharePoint library via the FrontPage RPC protocol, including check-in and the setting of custom metadata. This FrontPage RPC protocol is mentioned a lot lately by Mike. Is it because it's going to even better in Sharepoint v3...?
  • SharePoint Document Library Event Handler for Parsing JPEG Images - Source code for a SharePoint document library event handler that parses JPEG images, extracts their EXIF properties, then updates entries with those properties,modifying the libraries' fields accordingly if needed.
  • What's New Web Part for SharePoint Sites - Source code for a Web Part that walks through an entire site using the WSS object model and returns the most recently changed entries.
  • Thursday, March 24, 2005 6:33:42 AM UTC #    Comments [0]  | 

     

    Sharepoit online training#

    Via Arpan Shah's weblog:

    "You can do SharePoint Products and Technologies Hands on Labs online. http://www.microsoft.com/technet/traincert/virtuallab/sps2003.mspx

    This is -absolutely- killer. You can learn about the product without even having to set it up."

    Thursday, March 24, 2005 6:18:36 AM UTC #    Comments [0]  | 

     

    [Sharepoint Tip] HTML Viewer Service for Windows SharePoint Services#

    It's an old one, but in some cases very useful:

    The Office HTML Viewer server provides support for users who want to view the content of files in Microsoft Windows SharePoint Services document libraries, but do not have Word, Excel, or PowerPoint from Office 97, or a newer release of Office, installed on their local computer.

    Download here

    Tuesday, March 22, 2005 3:06:38 PM UTC #    Comments [0]  | 

     

    Great NON-Sharepoint news!#

    Normally I do not write a lot of personal stuff on my blog, but I want to make an exception once. So, no Sharepoint news this time but something else:

    I asked my girlfriend last weekend to marry me and guess what..? She said yes! Whahoo!

    I rented a VW New Beetle convertable and took her to an nice castle where I asked her. I had a great weekend for sure!


    This was the place, romantic isn't it? :)

    Tuesday, March 22, 2005 9:26:00 AM UTC #    Comments [0]  | 

     

    Longitude for Sharepoint#

    Via Mark's blog, I found the BA-Insight website showing a product called Longitude for Sharepoint. Again, a product that fills the gap that is called 'more advanced search' for Sharepoint. This one is quite cool, especially the preview function in the search results which gives an html representation of the results:

    Some other highlights:

    • Page previews
    • Hit highlighting
    • Boolean Search
    • Taxonomy Navigation
    Tuesday, March 22, 2005 5:12:44 AM UTC #    Comments [0]  | 

     

    Sharepoint v3 "facts"#

    Mike Fitzmaurice started his blog a while ago and after a period of silence he's giving his opinion again in blogsphere. In a few of his latest posts, he's talking about things that will be in the next version of Sharepoint. A brief overview:

    Webparts:

    • WSS “v3” (and anything built on top of it like SPS) is being written with ASP.NET 2.0, and will use, natively, ASP.NET 2.0 Web Parts.
    • WSS “v3” (and anything built on top of it like SPS) will carry forward the object models used for SharePoint Web Parts, so it will continue to run anything being written today.  Natively. Anything you write today will still work tomorrow.
    • ASP.NET 2.0–only sites that do not involve SharePoint technology will only run ASP.NET 2.0 Web Parts.

    Some more info on .Net 2.0 with Sharepoint 2003:

    • WSS “v2” (the currently-shipping version) won’t magically acquire the ability to host ASP.NET 2.0 Web Parts when WSS Service Pack 2 ships.  WSS Service Pack 2’s date and fix list aren’t publicly sharable yet, with one exception:  WSS SP2 will allow WSS and the ASP.NET 2.0 runtime to coexist on the same machine.  And in case you didn’t connect the dots… Attention:  Until WSS Service Pack 2 ships, do NOT attempt to install Visual Studio 2005 or the ASP.NET 2.0 runtime on a machine running WSS or SPS.  Until WSS SP2 is installed, doing so will break WSS/SPS.
    • The WSS and ASP.NET teams are exploring ways to encapsulate and host some of the functionality of ASP.NET 2.0 Web Parts in WSS “v2”.  We’re not guaranteeing that it will happen at all, let alone how and when it would happen.  If it happens, you should treat it like a happy surprise — don’t make plans that depend on it.  If it happens, you’ll hear about it here (and other places, too, of course). 

    http://blogs.msdn.com/mikefitz/archive/2005/03/17/397775.aspx 

    Frontpage RPC's:
    If you want to work with documents in SharePoint Document Libraries, and you need to do so remotely, you’d be well-served to get familiar with FrontPage RPCs.  Why?

    • Our object model isn’t remotable.  If you’re doing work on the server, this isn’t a problem.  But if you’re doing server-to-server work or smart client work, this matters a lot.
    • SOAP can’t chunk; specifically, it doesn’t have a means to break up an envelope into multiple transmissions, send them across, and reassemble them on the other side.  Do you want to send a 50mb file over the wire in what amounts to a 75mb all-or-nothing post?  I didn’t think so.  SOAP is fine for enumerating and accessing everything about a document but its contents, but you’ll need to supplement it with something else to do the actual I/O.
    • WebDAV does chunk.  But it doesn’t know how to version (which is funny, since DAV stands for Distributed Authoring and Versioning).  It also doesn’t know how to do a checkin or checkout.  Batch operations?  Forget it.

    http://blogs.msdn.com/mikefitz/archive/2005/03/14/395112.aspx 

    CAML:
    CAML is here to stay. CAML is just too useful to kill.  It covers both data and rendering instructions.  It lets our List Viewer Web Part fetch a list and its rendering instructions in one step and then only have to apply the rendering to the data.  It's blazingly fast.  It's also backward compatible with everything we've done to date.

    http://blogs.msdn.com/mikefitz/archive/2005/03/13/394974.aspx 

    Monday, March 21, 2005 7:50:28 PM UTC #    Comments [0]  | 

     

    Webparts: from Sharepoint to ASP.Net 2.0#

    A nice article that's worth reading by Dino Esposito about ASP.Net 2.0 and webpart development.

    "If you’re a SharePoint consultant, or invested a lot in the current version of SharePoint, is the advent of ASP.NET WebParts a good or bad news? And vice versa, if you have significant ASP.NET skills (especially in control development), does the future open up a whole new world of job opportunities in the SharePoint’s land?

    Although this article has been written before the release of the Whidbey’s Beta 2—the build announced as feature-complete—I believe that a few quick considerations can be made regarding the future of ASP.NET WebParts and SharePoint products.

    • It is rumored that the next version of SharePoint products (both Windows SharePoint Services and SharePoint Portal Server) will entirely be built on the ASP.NET WebParts framework;
    • Today’s SharePoint 2.0 WebParts will continue work in the next version of SharePoint, thus preserving your today’s investments;
    • ASP.NET WebParts will work in the next version of SharePoint;
    • The next availability of an update to SharePoint 2.0 to support ASP.NET 2.0 WebParts seems not to be a far-fetched idea either;

    The core code of SharePoint WebParts can be easily ported to ASP.NET WebParts. It goes without saying that the more platform-specific features you use, the more work is required to adapt controls. However, conceptually speaking SharePoint and ASP.NET WebParts support a nearly identical set of features so that mapping one to the other doesn’t pose insurmountable problems."

    Read the full article

    Monday, March 21, 2005 9:54:35 AM UTC #    Comments [0]  | 

     

    SharePoint - Integrated BPM Evaluation#

    Bob Mixon made an evaluation of several business process management solutions. Great overview!

    "Over the past month or so I have had the opportunity to evaluate many business process management solutions.  This is a new initiative that I have been recently tasked with which I am very excited.  In this article, I will be giving you an idea of what I have found to date.

    As with any evaluation process, the first thing to do is eliminate the products that do not fit within your base requirements.  I found this to be quite simple; our fundamental requirements are as follows:

     

    The product must provide…

     

    1. a graphical user interface giving non-developer business analyst the ability to create process workflows.
    2. the ability to add or extend workflow process actions using the Microsoft .NET platform.
    3. integration in core Microsoft infrastructure.
    4. administrative tools to facilitate the development, management and deployment of workflow processes.
    5. integration with Active Directory.  Our environment uses AD OU's extensively and we cannot administer this information in more than location.
    6. integration with SharePoint; both WSS and SPS.  This integration must include:
      1. the ability to trigger workflow process events from both document libraries and lists,
      2. the ability to create and manage workspaces,
      3. the ability to upload, move and copy documents,
      4. the ability to update, move, copy and delete list items.
    7. integration with Microsoft Office tools, including InfoPath.  This integration must include the ability to extract information from documents/forms for use in workflow process decisions.
    8. a minimal set of built in reports giving us the ability to view running processes, process bottlenecks and optimization points, etc. "

     

    Read the full article

    Saturday, March 12, 2005 6:29:51 PM UTC #    Comments [1]  | 

     

    Windows SharePoint Services SDK update#

    Updated WSS SDK download on MSDN.

    The SDK contains conceptual overviews, programming tasks, and references to guide you in developing solutions based on Windows SharePoint Services as a platform. The SDK includes information about the following technologies:

    1. Web Part Framework Create, package, and deploy Web Parts on SharePoint sites.
    2. Server-side object model Work with individual lists and sites or manage an entire Windows SharePoint Services deployment.
    3. Web services Use default Web services, or create custom Web services, to interact with Windows SharePoint Services from external applications.
    4. Collaborative Application Markup Language (CAML) Customize the schemas that define lists and sites, define queries for use with members of the object model or Web services, and specify parameters for use with methods in Remote Procedure Call (RPC) protocol.
    5. RPC protocol and other protocols Post requests from client applications to the server in order to access or modify data.
    6. Client-side APIs Use ActiveX controls to launch applications on the client or to provide other features that enhance Windows SharePoint Services.
    Saturday, March 12, 2005 6:21:24 PM UTC #    Comments [0]  | 

     

    Microsoft extends online collaboration by taking over Groove Networks#

    Microsoft is about to acquire Groove Networks, a leading provider for online collaborations and virtual offices.

    As a Windows desktop-based collaboration offering, Groove's Virtual Office complements Microsoft's collaboration solution offerings, which include the following:

    • Real-time collaboration solutions such as Microsoft Office Live Meeting 2005 and Microsoft Office Live Communications Server that enable in-the-moment one-to-one and one-to-many collaboration
    • Server-based collaboration solutions such as Microsoft Office SharePoint® Portal Server and Windows SharePoint Services that allow businesses to create and manage collaborative work spaces online or on a company's internal IT system
    • Peer-to-peer collaboration solutions through Groove's Virtual Office, which let any Windows-based PC user instantly create ad hoc, virtual work spaces that securely and easily span organizational, geographic and network boundaries, and allow information workers to be productive whether they're online or temporarily disconnected from the network.

    Read the press release

    Thursday, March 10, 2005 2:51:37 PM UTC #    Comments [0]  | 

     

    12 things to expect in Office 12#

    We can read on ENTNews an overview of things we can expect in Office 12. It's not that reveiling, because there are no details, but it might be interesting to read.

    A 2006 delivery date

    There's not much detail beyond that yet. Some published reports have Microsoft trying to time the release of the Windows "Longhorn" client and "Office 12," the code-name for the next version. Microsoft also says it will release the next version of Exchange, code-named "Exchange 12" or "E12," in 2006 and close to the release of Office 12.

    Anti-virus integration

    The biggest change to e-mail since the Office 2003/Outlook 2003 debut is Microsoft's public declaration that it will produce a consumer-oriented anti-virus engine by the end of 2005. Integration with that anti-virus engine for small and medium-sized businesses, and with the recently acquired Sybari Antigen anti-virus product for enterprises, is likely to be a major selling point of the next Outlook.

    Further anti-spam protection

    Anti-spam improvements in Outlook and Exchange were a key improvement in Office 2003. The changes to Intelligent Message Filtering last year showed Microsoft is still busy in this area.

    Office search functionality

    The acquisition of the Lookout search tool and the creation of the MSN Search toolbar are evidence that Microsoft isn't standing by while Google beta tests its Google Desktop Search beta. Tight integration of new search capabilities with Office, as well as replacement of the subpart native search in Outlook may be on tap.

    Research improvements

    The Office 2003 generation of products featured a decent Research task pane with some handy tools, including dictionaries, thesauruses and encyclopedias. Let's keep our fingers crossed for further refinements on this functionality that makes even more useful information available for free (or for the cost of Word, to be more precise).

    Longhorn integration

    What exactly the integration will be remains a big question mark. Because Longhorn features aren't fleshed out much beyond major development pillars, it's hard to predict how the two products will leverage one another.

    Developer improvements

    Developers should see a bunch of goodies around the Office 12 release. They're already getting an interim refresh of Office development capabilities with the Visual Studio 2005 Tools for Office this summer. Yet another version of Visual Studio is planned for the Longhorn release, around the same time Office 12 would come out.

    Piggybacking on Exchange 12

    If the anti-spam and anti-virus improvements materialize, and if Outlook/Exchange 2003 is any guide, the newest versions of both Exchange and Outlook will have to be used together to get the biggest benefit.

    Collaboration improvements

    With the Exchange 12 roadmap revealed, Microsoft looks like it's moving away from earlier ambitions to turn the Exchange Server into a collaboration platform similar to Lotus Domino. But Microsoft hasn't abandoned its collaboration dreams, the company has just shifted its attention to the SharePoint technologies. A new version of Office is a new opportunity for better collaboration integration with Windows SharePoint Services and Microsoft SharePoint Portal Server.

    Integration with new versions of second-tier servers

    With the October 2003 launch of the Office 2003 System, Microsoft expanded the definition of Office considerably. Instead of just an array of desktop productivity suites, Office became the umbrella for a pantheon of Microsoft's lesser servers. In addition to SharePoint Portal Server, there's also Microsoft Project Server and Live Communications Server, and the Live Meeting service.

    Integration with Istanbul

    With the overhauled Instant Messaging client "Istanbul" for Live Communications Server 2005 coming this year, Microsoft will have a rich new collaboration tool, which will be integrated into Microsoft's many Office productivity products. Istanbul is designed to allow for chats, initiate phone calls and route incoming calls.

    More XML support without going all the way

    This has been a recurring theme in Office releases since the .NET initiative surfaced in 2000. With each release, Microsoft finds new ways to balance its desire to increase XML support without making document formats, especially Word, compatible with competitive Office suites and thus threatening Microsoft's massive market share lead.

    Beta | Office
    Thursday, March 10, 2005 6:21:49 AM UTC #    Comments [0]  | 

     

    Sharepoint Search IFilter Overview#

    Andrew Connell mentions a list of IFilters on Channel9. Good overview:

    Document Type

    Link

    Notes

    PDF

    Adobe

    Free

    JPG, JPEG

    AimingTech

    Free

    CEL, DGN, MSG, RAR, ZIP,

    Alna AB

    Commercial

    CAB, CHM, HLP, MHT, ZIP

    Citeknet

    Free

    DWG

    Autodesk

    Commercial

    DWG

    CAD & Company

    Commercial

    WP

    Corel

    Free

    MSG

    Hallogram Publishing

    Commercial

    DWF, EPS, GIF, JPEG, MSG, PNG, PS, PSD,
    PDF, SHTML, SVG, TIFF, VCF, WMA, WMV, ZIP

    IFilterShop

    Commercial

    MP3

    meticulus

    Free

    RTF

    Microsoft

    Free

    VDX, VSD, VSS, VST, VSX, VTS

    Microsoft

    Free

    XML

    Microsoft

    Free

    MPP, PRT, SLDPRT, SLDDRW, SLDASM

    Net Intent

    Commercial

    XML

    QuiLogic

    Free/Commercial

    ZIP

    4-Share

    Commercial

     

    Thursday, March 10, 2005 6:06:22 AM UTC #    Comments [0]  | 

     

    Competencies in Sharepoint Portal Server#

    Bart mentioned it before, I'm currently working on an internal project for connecting people (employees) to knowledge and competencies. Currently, there is a problem finding the right person for the right projects or knowledge in our organisation. Using Sharepoint Portal for our company's intranet, we would like to search for people with certain knowledge and compentencies using Sharepoint Search, which should return the right people in the result page. So, what would the solution look like?

    Managing competencies
    There is a demand for a Sharepoint integrated management for compentencies and people. A logical choise for that is InfoPath, which enables a richt client environment for managing that data. This data is stored as XML in a Sharepoint form library.

    Updating keywords and best bets
    To influence the search results, I created some code that updates the knowledge and competencies using keywords and best bests. Keywords, that represent the knowledge and competencies, best bets that represent the people. Best bets will be shown in the top of resultspage when searching on a realted keyword.

    When saving the infopath xml file, an eventhandler is fired that updates that keyword repository. I will post more details with code later. Based on a KPI, becasue I don't want have people list as bet best that do not have any knowledge.

    ...and an overview of the best bet property:

    Updating UserProfiles
    Of course, when someone is found, I want to see that level of knowledge for that person. I also want to see other competencies and knowledge that is connected to that person. When clicking on a user, we are redirected to that users profile. The same eventhandler for the keywords will also update the users profile with the values in the infopath xml form, inlcuding the sections:

    This way, I can find people based on keywords and best bets AND their userprofile.

    I'm currently developing this solution, so ther will probably change something here. Besides that we need to look very closely on the categories and competencies, before implementing it in a production environment. Updates with code will follow soon...

    Wednesday, March 09, 2005 8:27:01 AM UTC #    Comments [1]  | 

     

    Office Communicator 2005#

    Lot's of things happed last few days when talking about online communication and collaboration. After the release of Office Live Meeting earlier, Istanbul is beta now. Yesterday, Bill Gates was talking about Microsoft Office Communicator 2005, which will be the release name of Istanbul.

    Next to Office Communicator, the awaited SP for Live Communication Server 2005 will be released which integrates other IM networks such as AOL and Yahoo! and the MSN network. The updates:

    • PIC for LCS 2005. A result of customer feedback voicing the need to communicate with users on three major public IM networks (MSN, AOL and Yahoo!), PIC support allows organizations to exchange security-enhanced IM and presence information with customers, partners and suppliers on those networks.
    • Enhanced federation. Connecting two or more organizations using Live Communications Server has been simplified, reducing the IT administrator workload for enabling enterprise-to-enterprise federation.
    • "Spim" control. Corporations can get help defending against spam sent via instant messaging (or "spim") by restricting instant messages and the sharing of presence information to contacts specified in each user's profile. They can apply additional "spim" filter settings for each federated connection to reduce the number of unauthorized or unsolicited messages.

    Like Bill says, it's getting all about integrated communications solutions:

    • Rich presence. With presence awareness built into Microsoft software, information workers can view the context and availability of a person before initiating communication with her or him.
    • Unified experience. Integration among modes of real-time communication (e-mail, phone, IM, SMS, videoconferencing and Web conferencing) allows information workers to choose the most appropriate mode of communication based on the situation at hand, and enables them to seamlessly transition from one mode to another or use them together.
    • Built-in intelligence. With integrated communications, software can automatically handle communications based on knowledge of people's preferences, physical location, organizational relationship and topic of communication. Software intelligence allows users to control how incoming communications are routed to them based on their context and preferences, and who is calling.

    Anyway, it's really getting somewhere now!

    Wednesday, March 09, 2005 6:09:25 AM UTC #    Comments [2]  | 

     

    Microsoft Outlines Business Applications Strategy and Solutions Road Map#

    Via Paul's blog:

    The most interesting quote from the press release, would be:

    "Windows® and Office are a powerful foundation for productivity and a rich platform for partners to build great solutions and add value,"  Gates said. "The Microsoft Business Solutions group builds on that foundation to deliver world-class business applications that are simpler and less expensive, offering more companies new ways to enhance the way they work."

    Which shows MSFT is moving towards further integrating it’s Business Solutions with Office and selling it more and more as a platform as well as an application suite, see also VSTO 2005.

    One more quote:

    "Project Green," the code name for next-generation Microsoft Business Solutions' development efforts, will be delivered over the course of two waves. The first wave will occur between 2005 and 2007, and will include the release of a shared user interface based around 50 common configurable roles that people have within a company, all seamlessly integrated with Microsoft Office. Microsoft's business applications also will interoperate with service-oriented applications and include a common configurable reporting environment based on SQL Server (TM) Reporting Services and a common security-enhanced intranet and extranet environment based on Microsoft Office SharePoint® Portal Server to enable new levels of collaboration within and across companies. (Emphasize mine)

    Looking forward to see what improvements have been made, esp. in Microsoft CRM, est. RTM Q4 2005, since that isn’t the friendliest platform to base a solution on.

    Tuesday, March 08, 2005 4:36:14 PM UTC #    Comments [0]  | 

     

    Live Meeting 2005 Add-in: Microsoft Office Live Meeting Intranet Portal#

    Via Patrick's blog:

    The Live Meeting Intranet Portal makes it easier to deploy and manage Live Meeting. If your company has deployed Microsoft Active Directory directory services, you can use the Live Meeting Portal for Active Directory to:

    • Automatically create Live Meeting accounts for users once they are authenticated on your corporate network.
    • Allow authenticated Windows users to log in to Live Meeting without entering a Live Meeting user ID and password.
    • Permit users to change their Live Meeting passwords when authenticated by your Active Directory service.
    • As the administrator of the Live Portal for Active Directory, you can control the minimum length and complexity of Live Meeting passwords set from the portal to help ensure that users choose secure passwords.
    • Automatically synchronize a user's Live Meeting account settings with the user's Active Directory settings each time the user logs in through the Portal.
    • Allow users to access Live Meeting from your corporate network without knowing or managing their Live Meeting password.
    Tuesday, March 08, 2005 4:30:33 PM UTC #    Comments [0]  | 

     

    Istanbul beta program open for nominations#

    Via Bink.nu:

    Real-Time Collaboration Client Will Strengthen Connection Between Customers And Their Telephony, Line-of-Business and Productivity Applications; Beta Program Open for Nominations

    Today in his keynote address at the Fall 2004 VON Conference & Expo, Anoop Gupta, corporate vice president of the Real-Time Collaboration (RTC) Business Group at Microsoft Corp., outlined Microsoft's real-time collaboration vision and strategy for integrated communications, and announced plans for a next-generation client. Building on the recent success and rapid adoption of Microsoft® Office Live Communications Server and Microsoft Office Live Meeting, Gupta introduced the newest member of the Microsoft Office System, code-named "Istanbul," that will provide integrated communications capabilities including instant messaging, extensible presence, PC-based voice and video, and telephony integration.

    "Customers depend on real-time communications to make more informed, timely decisions, and to stay better connected with their customers and grow their business," Gupta said. "With 'Istanbul,' Live Communications Server and Live Meeting, we are providing pervasive real-time collaboration capabilities and empowering our customers to work together more effectively. 'Istanbul' represents a milestone by integrating various modes of communications in one unified desktop experience."

    ......
    The "Istanbul" beta program is open for nominations. Those interested in participating should contact their Microsoft account manager or sales representative for instructions on how to nominate their organization. "Istanbul" is scheduled for release in the first half of 2005
    . Full Story At Source

    Tuesday, March 08, 2005 4:19:41 PM UTC #    Comments [0]  | 

     

    Bart's blogging on IW solutions#

    Bart has taken a good start blogging on information worker solutions. He's written some interesting postings on dashboarding on portals and desktop search.

    About portal dashboards and OLAP cubes, there are some great things that you can do with them! I'll post some of that later this week.

    Anyway, great start Bart and can't wait to see more!

    Tuesday, March 08, 2005 4:10:59 PM UTC #    Comments [0]  | 

     

    [Sharepoint Tip] Search update types#

    During most of the Sharepoint deployments I did, administrators ask the question about what the different search indexing updates mean. Well here is a short explanation:

    Full Update:

    • Crawls all content on a site.

    Incremental Update:

    • Crawls only new and changed content.

    Incremental (inclusive) Update

    • Crawls new and changed content.
    • Detects deleted entries

    Adaptive Update

    • Crawls content that is likely to have changed based on the site history.

    Of course, this information is also available in the Administators Guide of SPS 2003

    Monday, March 07, 2005 9:01:58 AM UTC #    Comments [0]  | 

     

    SharePoint and Log: a simple way to analyse#

    Renaud Comte has some usefull info about analyzing statistic data in Sharepoint.

    Read full article

    Monday, March 07, 2005 7:52:09 AM UTC #    Comments [0]  | 

     

    Instanbul really close to release#

    From news.com:

    “Microsoft is beefing up its corporate instant messaging product lineup with new extras like firewall traversal and collaboration, as it prepares to launch its code-named Istanbul desktop communications client, possibly as early as Tuesday.

    ....

    “Microsoft on Tuesday is widely expected to unveil Istanbul, its new instant messaging and real-time communications client at a San Francisco event scheduled to be headlined by Chairman Bill Gates. Istanbul goes beyond IM by handling a variety of functions, such as viewing calendar information from Outlook, for example, to decide whether an incoming call should go to someone's desktop or mobile phone.”

    Look's like the messenger outlook integration (calendar) will be standard functionality :)

    Monday, March 07, 2005 7:17:06 AM UTC #    Comments [0]  | 

     

    BlogMap: blogs near me#

    I'm probably the last one in blogsphere that found this one (via angus), but I like it: chandu thota's blogmap. Using MapPoint, bloggers can entry their location so they can see which bloggers are located near them. Cool feature!

    and check the icon on the right side of my blog:

    Saturday, March 05, 2005 9:35:34 PM UTC #    Comments [0]  | 

     

    [Sharepoint Tip] Manage Sharepoint alerts in Outlook 2003#

    Besides the 'Alerts Summary' on 'My Site', it is also possible to manage alerts in Outlook 2003:

    • Go to 'tools' and 'rules and alerts...' in the Outlook menu 
    • Choose the tab 'Manage Alerts'. You'll find all the alerts which you're subscribed to.

    • You'll be able to add new alerts as well. Outlook helps by providing the sources you've visited and the option to subscribe to these sources.

    Again a nice example of the Office integration with Sharepoint I think!

    Saturday, March 05, 2005 2:27:19 PM UTC #    Comments [3]  | 

     

    VSTO Presentation: Working with Word Host Controls#

    From the VSTO team blog:

    “The VSTO team held a developer lab at the end of February where we delivered several presentations on the features of Visual Studio 2005 Tools for the Microsoft Office System.  We’ve created video presentations of the content delivered in the labs that we’ll be posting to this blog over the next several weeks.  In this presentation, I describe the host controls that are available for use on a Word document, how to add the controls to your document at design time and run time, and the differences that exist between a Bookmark control and the underlying interop object. This video is 30 minutes long and the file size is 23 MB. You can view this streaming video presentation at Working with Word Host Controls.”

    Read full article

    Office | VSTO
    Saturday, March 05, 2005 2:08:24 PM UTC #    Comments [0]  | 

     

    SQL Reporting Services SP2 comes with SharePoint web parts#

    From Greg Hughes' blog:

    From Microsoft, news announcing SQL Reporting Services SP2, which will include two web parts for SharePoint 2003 that can be used for displaying reports in the SharePoint portal or site:

    Along with security and product enhancements, SQL Server 2000 Reporting Services SP2 will include two SharePoint® Web Parts, which enable users to explore and view reports located on a report server through Windows® SharePoint Services or SharePoint Portal Server. The Web Parts will make it easy for customers to build business intelligence (BI) portals with SharePoint that include Reporting Services reports. This, in turn, will give their end users access to their enterprise information from one seamless interface. SP2 also will support a rich client-side report printing experience directly from Microsoft Internet Explorer, so customers can quickly print their reports by clicking on a single button.

    Good move. One of SharePoint's strongest points is that it can act as a "one-stop-shop" for finding, aggregating, viewing and using information across a company or organization, usable by both individuals and groups. The more web parts are made available to do this kind of thing out of the box, the better. It should be a requirement for any Microsoft business product, I think, and other companies should follow suit.

    Read full article

    Friday, March 04, 2005 1:57:01 PM UTC #    Comments [0]  | 

     

    Customizing List Item Forms in Windows SharePoint Services#

    A nice article on MSDN by Les W. Smith on Customizing List Item Forms in Windows SharePoint Services.

    “In this article, we suggested the following guidelines for customizing the forms used to work with list data in Windows SharePoint Services:

    • Use Web Parts and the Windows SharePoint Services object model to extend user interaction with list data, either bringing list views, for example, into the list item form, or bringing the list item form out to various locations in a site.
    • Customize ONET.XML to modify the top navigation area or to insert a Web Part by default within the home page of sites instantiated through the site definition.
    • Use custom Web server controls to consolidate code that you need to reuse in a deployment and insert the controls declaratively within the appropriate table cell of the page layout.
    • Customize the opening field collection of SCHEMA.XML to add special fields to the list and to change the order of fields as displayed in the list item form.

    You may also use the following advanced customizations, involving customization of the form content defined in SCHEMA.XML to modify form views. However, these customizations may not carry over to future versions of Windows SharePoint Services:

    • Modify DispForm.aspx to customize navigation areas, but be strategic in customizations, always considering the table layout of the page.
    • Customize the form definitions in SCHEMA.XML to modify the view of list items displayed in a form, embed a Web Part in the form in lists created through the list definition, modify the toolbar, or add script in the browser page to enhance user interaction.

    Considering these guidelines when you are customizing list item forms can help you extend user interaction with list data and help ensure code reusability in the deployment.”

    Friday, March 04, 2005 1:39:16 PM UTC #    Comments [0]  | 

     

    [Sharepoint Tip] Hack the Sharepoint SiteDirectory#

    Other then normal Area's, the Site Directory has been disabled for editing, managing webparts etcetera via the 'Modified Shared Page' link when you enter edit mode. This way, it is hard to customize the Site Directory in a normal way you would expect.

    There are however two 'hacks' to edit the page anyway.

    Hack the URL

    1. Go to the site directory (Sites) and click 'edit page'. (as you can see, you're not able to manage the page)
    2. Paste the following string behind the url: '&PageView=Shared' and hit enter
    3. Go to one of the webparts and click 'Modify Shared Web Part'
    4. You will go into the design mode where you can manage the webparts

    This way is quite easy, but there is no way to add a new webpart. When you want to add webparts, there is a second way to go:

    Hack the template

    1. Go to “Program Files\Common Files\Microsoft Shared\web server extensions\60\TEMPLATE\1033\SPSSITES”. This is the template of the SiteDirrectory
    2. When opening 'default.aspx' you will notice that this page redirects to a summary.aspx page.
    3. Open in SPSSITES\LISTS\SITESLST the ‘Summary.aspx’ page.
    4. Add somewhere in the page the <SPSWC:EditModeSettingsLink runat="server" /> server control.
    5. Save the page
    6. In the portal, go to the site directory, click edit page and voila!

     
    hack the sitedirectoy (in Dutch) :)

    Thursday, March 03, 2005 10:57:48 AM UTC #    Comments [1]  | 

     

    Using InfoPath as a Reporting Solution#

    A nice article by Larry W. Jordan Jr. in the March 2005 edition of MSDN magazine about Using InfoPath as a Reporting Solution.

    I based the solution on Microsoft® Windows® SharePoint® Services and on Microsoft InfoPath® 2003 SP1 because they're easy to use and deploy. Employees create, edit, and view reports in InfoPath, with SharePoint serving as a data and report repository. InfoPath makes it simple for the individual teams to deploy various project status forms to SharePoint sites. As a bonus, this allows us to maintain the security and privacy of the status data because SharePoint provides domain and user-level security. Plus, it is easy to administer. SharePoint also offers many data storage and reporting options, and InfoPath simplifies integration with Web services, SQL Server, and Visual Studio®.

    One of my main goals was to have the solution integrate across the development, test, and program management teams of MSDN® and TechNet. This required that the solution be maintainable by people who don't work in Visual Studio every day and it required that updates and changes to employee and project data could be made by anyone on the team.

    I also wanted to collect a number of metrics to use in resource allocation decisions, including active development projects, developer and tester activity in the defect tracking system, check-in e-mails to the change management systems (source control), and discussions with the leads on my team.

    I also had the following requirements:

    • The app should be written in managed code.
    • It should integrate our product defect and change tracking system metrics.
    • It should use the charting capabilities of the Office Web Components.
    • It should post the submissions to both a SharePoint site and a Web service interfacing to a SQL database.
    • The overall organizational reports should be generated from the database and implemented using SQL Reporting Services.

    Read full article

    Thursday, March 03, 2005 7:40:04 AM UTC #    Comments [0]  | 

     

    Customizing Microsoft Office Information Bridge Framework for Microsoft CRM#

    I really should be doing more on IBF for sure!

    from MSDN:

    Customize Microsoft Office Information Bridge Framework for Microsoft Business Solutions CRM to meet the unique needs of your business organization. This article describes how to modify the Information Bridge Framework to display additional Microsoft CRM account information. By following the techniques shown in this article, you can customize Information Bridge Framework for Microsoft CRM to display additional fields from Microsoft CRM objects in the Information Bridge Reference pane.

    Read complete article

    Thursday, March 03, 2005 7:31:59 AM UTC #    Comments [0]  | 

     

    Sharepoint, Office and VSTO 2005#

    Today, I did a presentation about in what way Office and the upcoming Visual Studio Tools for Office 2005 (VSTO 2005) could play a role in the solutions that are built by the Information Worker unit at Tam Tam.

     

    I tried to start a discussion on this topic by showing some examples. These examples could be used in real life, however in this case they are used for showing the options we have as developers to integrate InfoPath, Word, Excel and Sharepoint using XML Web Services and VSTO 2005. 

    For this presentation I created a simple case based on employee declarations. In many organizations, an Excel document is printed, filled in, receipts are attached and brought to the finance guy that puts them into a finance system. Now, this would be something that could be more efficient, right? :)

    InfoPath to Sharepoint

    So, what’s the case here? We have our Sharepoint Portal based intranet and Office 2003 applications such as Word and Excel. With Office 2003, InfoPath was introduced as an XML based application for creating forms and filling them out. Sharepoint supports this format using Form Libraries.

     


    An empty form library

     

    So, InfoPath is a very user friendly tool for filling out forms. Declarations are all about forms, so let’s create a declaration form and put it into Sharepoint. To do something more with the information that is stored in an XML file, I created a web service that posts the InfoPath data into a Sharepoint custom list (“Declaration List”). This web service runs under the Sharepoint virtual server.

     

    [WebMethod]

    public void InsertDeclaration(string title, string tammo, DateTime declarationDate, string type, string receiptUrl, double amount, string comment)

    {

          SPSite mySite = new SPSite("https://[server]/[wss site]");

          SPWeb myWeb = mySite.OpenWeb();

     

          myWeb.AllowUnsafeUpdates = true;

     

          SPList myList = myWeb.Lists["Declaration List"];

          SPListItem myItem = myList.Items.Add();

          myItem["Title"] = title;

          myItem["Tammo"] = tammo;

          myItem["Date"] = declarationDate;

          myItem["Type"] = type;

    myItem["Receipt"] = receiptUrl;

          myItem["Amount"] = amount;

          myItem["Comments"] = comment;

          myItem.Update();

    }

    As you can see, the web service has some parameters that determine the input type (string, DateTime, etc). The good thing about InfoPath is that uses this “schema” to generate the form items based on the web service. So, just create a submit form, connect to the web service for submitting the data. Drag and drop the data source on the form and let InfoPath do the work!


    Just drag and drop…

    To “finish” it, I mapped to our employee database, to pre-fill the user names. Simple but effective.

     

    Ok, ready to fill a form, click the submit button and the data is posted into the Sharepoint “Declaration List”, including the image of a receipt (that is stored in an image library)


    The InfoPath declaration form.


    The same item is stored in a Sharepoint list.

    Sharepoint in Office Research Pane

    In the part above, the data that is posted in an InfoPath form is stored into a Sharepoint list. Now, to do something more with this data, we can use the Word 2003 Research Pane to search trough this data and show it in task pane, where we can use this data in our documents.

     

    To do so, we have to create a research service, which is documented on MSDN as well. This research service basically is had two methods: the registration method and the query method. Use the registration method to register Word to the research service. There is a wizard for building that, but of course this is more fun to build ourselves:

     

    [WebMethod(CacheDuration=60)]

    public string Registration(string regXML)

    {

          MemoryStream ioMemStream = new MemoryStream();

          XmlTextWriter myXMLWriter = new XmlTextWriter(ioMemStream, System.Text.Encoding.UTF8);

     

          myXMLWriter.Indentation = 4;

          myXMLWriter.IndentChar = ' ';

          myXMLWriter.WriteStartDocument();

          myXMLWriter.WriteStartElement("ProviderUpdate","urn:Microsoft.Search.Registration.Response");

          myXMLWriter.WriteElementString("Status", "SUCCESS");

          myXMLWriter.WriteStartElement("Providers");

          myXMLWriter.WriteStartElement("Provider");

          myXMLWriter.WriteElementString("Message", "Declaration Research Taskpane has been intstalled!");

          myXMLWriter.WriteElementString("Id", "{3861168E-3162-4a2d-AF9D-ADBE1F6C0AD1}");

          myXMLWriter.WriteElementString("Name", "Tam Tam Declaration Research Taskpane");

          myXMLWriter.WriteElementString("QueryPath", "[the webservice url]");

          myXMLWriter.WriteElementString("RegistrationPath", "[the web service url]");

          myXMLWriter.WriteElementString("Type", "SOAP");

          myXMLWriter.WriteStartElement ("Services");

          myXMLWriter.WriteStartElement ("Service");

          myXMLWriter.WriteElementString("Id", "{363BF043-AE83-49d4-B624-A659F117A4AE}");

          myXMLWriter.WriteElementString("Name", "Tam Tam Declaration Research Taskpane");

          myXMLWriter.WriteElementString("Description", "Get user declarations!");

          myXMLWriter.WriteElementString("Copyright", "All content Copyright (c) 2005 Tam Tam B.V.");

          myXMLWriter.WriteElementString("Display", "On");

          myXMLWriter.WriteElementString("Category", "[the category]");

          myXMLWriter.WriteEndElement();

          myXMLWriter.WriteEndElement();

          myXMLWriter.WriteEndElement();

          myXMLWriter.WriteEndElement();

          myXMLWriter.WriteEndElement();

          myXMLWriter.WriteEndDocument();

     

          myXMLWriter.Flush();

          ioMemStream.Flush();

          ioMemStream.Position = 0;

          StreamReader iostReader = new StreamReader(ioMemStream);

          return iostReader.ReadToEnd().ToString();

    }

     

    Now, Office can connect and know how to use the research service. When entering a query, I want to let the service search though the Sharepoint list and returns the data that belongs to name that is given in the query. For example, when I query “Mart”, I want to get all declarations that belong to Mart.

     

    Then after I have the results, I want to have to options: insert the Sharepoint data into my document, or copy it to the clipboard. There are schema’s available for looking up which actions can be performed and how the results are given back in Word.

     

    So, the piece of code that builds the results from Sharepoint looks something like this:

     

    SPSite mySite = new SPSite("[WSS Site URL]");

    SPWeb myWeb = mySite.OpenWeb();

    SPList myList = myWeb.Lists["Declaration List"];

     

    foreach (SPListItem myItem in myList.Items)

    {

          if (myItem["Tammo"].ToString().ToLower() == queryTerm.ToLower())

          {

                myXMLWriter.WriteStartElement("Content", "urn:Microsoft.Search.Response.Content");

                myXMLWriter.WriteStartElement("Actions");

                myXMLWriter.WriteStartElement("Insert");

                myXMLWriter.WriteElementString("Text", "Insert Declaration" );

                myXMLWriter.WriteEndElement();

                myXMLWriter.WriteStartElement("Copy");

                myXMLWriter.WriteElementString("Text", "Copy Declaration" );

                myXMLWriter.WriteEndElement();

                myXMLWriter.WriteEndElement();

               

    myXMLWriter.WriteElementString("P", "[" + ((DateTime)myItem["Date"]).ToString("yyyy-MM-dd") + "] " + myItem["Title"].ToString() + " (" + myItem["Type"].ToString() + ")" );

                myXMLWriter.WriteElementString("P", "by " + myItem["Tammo"].ToString() );

                myXMLWriter.WriteElementString("P", myItem["Comments"].ToString() );   

                myXMLWriter.WriteElementString("P", "Amount: €" + myItem["Amount"].ToString() );

                myXMLWriter.WriteStartElement("Image");

                myXMLWriter.WriteAttributeString("source", myItem["Receipt"].ToString().Split((",").ToCharArray())[0].ToString() );                       

                myXMLWriter.WriteEndElement();

                myXMLWriter.WriteEndElement();

          }

    }

    myWeb.Close();

     

     

    This code just loops through the list and constructs the xml. Now we can register the web service in Word to do queries.

    1)      Select the research pane in the task pane

    2)      Click ‘research options’ and ‘add services’

    3)      Provide the URL of the service and click ‘add’. Now the service is registered.

    4)      In the research pane, select the research (in this case ‘Tam Tam Declaration Research Taskpane’)

     

    Now when I search on ‘Mart’ I get my declarations back in the results! Using ‘insert declaration’ I can insert is into my document. Great!


    The results and the insertion into the document

    This is not new, I know. But it’s fun how to see Word interacting with Sharepoint this way. And of course, in demonstrating office in the Information Workers world, it’s a good example how simple it is to use Sharepoint data in Word.

    Sharepoint to Office using VSTO 2005

    VSTO, now it is getting really interesting! We have our web service for inserting InfoPath data into Sharepoint, a research service for query Sharepoint data into the research pane in Word. Now, VSTO 2005 is offering a much more rich integration level using managed code and task pane extensions to build applications into your documents.

     

    Note that VSTO 2005 runs on ASP.Net 2.0. I’ve installed an instable version of Visual Studio 2005 BETA 1 to create the demos. However I was spending most of the time on restarting this BETA 1 I created two applications within a few hours.

     

    Sharepoint data into Word

    The basic idea of my declaration solution is to do something with the Sharepoint data in Word, like…well, like creating documents that are pre-filled with the declaration data from Sharepoint. Enough reasons to do so, right? ;)

     

    So, I created a task pane extension that has the option to load a web service (by clicking the button) that provides the data for a datagrid, in that same task pane extension. When walkingh through data in this datagrid, the data in the document will change, showing the correct declaration data for printing or saving or whatever I want to do with that. This is how it looks (don’t mind the colors, it’s ugly, I know):


    Task pane with the datagrid, and the data in the document

    This is a very simple example of how to use the Office task pane extension. But let’s take a look at the code. Visual Studio 2005 can use the Office components to create a, in this case, complete Word environment to program in.


    Office in Visual Studio

    Right now it is possible to create code in the “code behind” of the document. This solution is creating the task pane extension and loads the data in the datagrid into bookmarks in the document. It also processes the image from an url in Sharepoint to a picture box in the document.

     

    Adding a control (DataSourcePane) to the Actionpane:

     

    private void ThisDocument_Initialize(object sender, System.EventArgs e)

    {

          dataSources = new DataSourcesPane();

          ActionsPane.Controls.Add(dataSources);

    }

     

    Connect to web service and load into dataset:

     

    nl.tamtam.intranet.Declarations myDeclarations = new nl.tamtam.intranet.Declarations();

    myDeclarations.Url = "[web service url]";

    myDeclarations.Credentials = new System.Net.NetworkCredential("[username]", "[password]", "[domain]");

    myDataSet = myDeclarations.GetDeclarationDataSet();

     

    And load the data into a BindingSource and bind the bookmarks:

     

    myDataConnector = new BindingSource();

    myDataConnector.DataSource = myDataSet.Tables[“Declarations”];

     

    Bookmark1.DataBindings.Add("Text", myDataConnector, Title);

    Bookmark2.DataBindings.Add("Text", myDataConnector, Comment );

    Bookmark3.DataBindings.Add("Text", myDataConnector,Tammo );

    Bookmark4.DataBindings.Add("Text", myDataConnector, Amount);

    Bookmark5.DataBindings.Add("Text", myDataConnector, Receipt );

     

    Then now from the task pane, connect the BindingSource to the datagrid:

     

    dataGridView1.DataSource = Globals.ThisDocument.myDataConnector;


    The task pane control

    To summarize, with a few lines of code, I created a task pane extension, connected a web service to a datagrid in the task pane and then bind the data to bookmarks in a Word document.

     

    Sharepoint data in Excel

    Pretty much the same, I reused the same task pane in an Excel. But now, not binded to bookmarks, but to a List, which is a control in Excel. So, the data is bind to the List, now a Chart is automatically generated based on the values in the list.


    ..with just one line of code:

    this.List1.DataSource = myDataConnector;

     

    Conclusion

     

    To summarize, VSTO 2005 and web services make it really easy to do something more with Office documents. In this case, our finance man can dynamically process the declarations that are made with InfoPath, stored in Sharepoint, processed and analyzed in Office. All based on three web services (store declaration, research service and retrieve declaration list) Information Workers can work with real-time data from Sharepoint in Office.

     

    Resources

     

    Office Research Service SDK

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rssdk/html/rsconAboutRSSDK_HV01082263.asp

     

    Research XML schema’s

    http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rssdk/html/rsReferenceSchemas_HV01082292.asp

     

    VSTO 2005

    http://msdn.microsoft.com/office/understanding/vsto/

    Wednesday, March 02, 2005 2:51:34 PM UTC #    Comments [2]  | 

     

    [Sharepoint Tip] Fatal webpart error, what to do?#

    The last year and a half, I've been working on our company intranet a lot. From the beta release of Sharepoint 2003 until now, I've tried to communicate the things I've discovered while building webparts and configuring Sharepoint 2003. Anyway, I've been posting them into out knowledgebase which is searchable with Sharepoint search of course. Despite of that they are mostly known tips in the Sharepoint community, I thought it might be funny to re use these tips on my blog!

    So, please let me know I've you consider the postings that will start with “[Sharepoint Tip]” as SPAM or not and I will respond to that :)

    Anyway, this time, the first knowledgebase Sharepoint Tip on my blog: “Fatal webpart error, what to do?”

    -----

    It's not very common, but it happens when you're developing webparts and suddenly your Sharepoint page will turn back a fatal error in one of your webparts. Most of the time, a link is provided saying go to the webpart maintenance page to remove the webpart.

    However, it might occure that this link is not provided, because you've messed up things so bad... Anyway, when this happens, you can manually type the url to maintain the webparts in the following syntax:

    http://[servername]/[subsite/area]/_layouts/[landcode]/spcontnt.aspx?pageview=Shared&url=[relative path + page(aspx)]

    http://[servername]/[page(aspx)]?contents=1

    thanks Maurice, for this great tip :)

    This way, you will enter the maintenance webpart page if the link is not provided and you will be able to turn off the webpart!

     

    Wednesday, March 02, 2005 7:55:53 AM UTC #    Comments [2]  | 

     

    Coveo Enterprise Search for Microsoft SharePoint?#

    Yesterday, Coveo published a press release introducing Coveo Enterprise Search for Microsoft Sharepoint Portal Technologies.

    Customers recognized and requested the enhancements that CES can offer for the SPT user, including:

    • Intelligent summarization and concept extraction technologies, both of which help users optimize their search experience.
    • A “View as HTML” feature that provides cached HTML versions with highlighted query terms for Microsoft Office documents, Adobe PDFs and other non-HTML documents.
    • Improved relevance with query capabilities based on powerful syntax that supports spelling suggestion, stemming, exact phrase and Boolean operators.
    • Configurable search preferences that allow users to tailor the search experience to their liking.
    • Advanced handling of metadata and XML data to provide more accurate search results.
    • Plug-in-style integration with SPT so that users are presented with the familiar look and feel of the SPT environment.
    • Robust search technology that leverages existing SPT security to control access to sensitive company data.

    I wonder how this will be of more value then extending the Sharepoint Search such as Matthew is doing right now with his SPS Advanced Search Tools (SAST), which is currently in beta. In a small organisation where I work in (about 50 employees), the (Sharepoint) search catalogs contain about 50.000 documents right now. In this case we would pay a $15.000 price when using Coveo search, while the SPS Search is included in the licence... do I miss something here?

    UPDATE:

    I did miss something here yes. Yesterday I got an email from Coveo in where they explain why Coveo Search for Sharepoint could be good product to choose. They sent me a list of reason why their customers did choose for their product. Although I do not agree with all the points compared to Sharepoint search, they made a point on some of them. A (very brief) summary:

    • Licencing costs. “CES for SPT’s cost for the performance is negligible at 500,000 docs for USD $4,995 + user licenses.  I believe you were looking at the Coveo Enterprise Search pricing on the www.coveo.com site.” Yes I did look at the wrong pricing, sorry for that...
    • Performance. Lower resource impact, which results in a better ROI. “The increase in user efficiency by using our additional features (relevance handling, concept extraction, view as HTML, desktop search…) which yield more relevant results and implementation time to optimal results.“
    • Rich advanced and costimizable search, including boolean search, desktop search, highlighting and xml support, if you want.

    The standard Sharepoint Portal search webparts are not that extensible, but Sharepoint does provide a way to extend it the way you like using web services and the object model (see my referral to Matthew's project). My question to them if there is some sort of API available was satisfying.

    As far as an API to wrap CES into some app for searching its content, absolutely it has this capability. There is full API documentation that comes with the free 5000 download. SharePoint is a great example of how CES can integrate into an app. CES makes it a lot easier as we have ASP/COM/C#/.NET etc. We also are extensible in that we can pull in content from pretty much any content source, with various choices as to how to do that.“

    I _did_ miss some points on Coveo search. There are situations that this indeed could be a logical choice. I might download their free version to try their Sharepoint integration. Anyway, thanks Coveo for your usefull and explaining comment!

    Tuesday, March 01, 2005 7:40:23 AM UTC #    Comments [0]  | 

     

    All content © 2010, Mart Muller
    On this page
    Stress Testing SharePoint with Application Center Test (ACT)
    U2U CAML Query Builder and Execution Tool Released
    Extending and Enhancing the SharePoint Portal Server Search User Interface
    Sharepoint downloads on GotDotNet
    Sharepoit online training
    [Sharepoint Tip] HTML Viewer Service for Windows SharePoint Services
    Great NON-Sharepoint news!
    Longitude for Sharepoint
    Sharepoint v3 "facts"
    Webparts: from Sharepoint to ASP.Net 2.0
    SharePoint - Integrated BPM Evaluation
    Windows SharePoint Services SDK update
    Microsoft extends online collaboration by taking over Groove Networks
    12 things to expect in Office 12
    Sharepoint Search IFilter Overview
    Competencies in Sharepoint Portal Server
    Office Communicator 2005
    Microsoft Outlines Business Applications Strategy and Solutions Road Map
    Live Meeting 2005 Add-in: Microsoft Office Live Meeting Intranet Portal
    Istanbul beta program open for nominations
    Bart's blogging on IW solutions
    [Sharepoint Tip] Search update types
    SharePoint and Log: a simple way to analyse
    Instanbul really close to release
    BlogMap: blogs near me
    [Sharepoint Tip] Manage Sharepoint alerts in Outlook 2003
    VSTO Presentation: Working with Word Host Controls
    SQL Reporting Services SP2 comes with SharePoint web parts
    Customizing List Item Forms in Windows SharePoint Services
    [Sharepoint Tip] Hack the Sharepoint SiteDirectory
    Using InfoPath as a Reporting Solution
    Customizing Microsoft Office Information Bridge Framework for Microsoft CRM
    Sharepoint, Office and VSTO 2005
    [Sharepoint Tip] Fatal webpart error, what to do?
    Coveo Enterprise Search for Microsoft SharePoint?
    This site
    Calendar
    <July 2010>
    SunMonTueWedThuFriSat
    27282930123
    45678910
    11121314151617
    18192021222324
    25262728293031
    1234567
    Archives
    Sitemap
    Disclaimer

    Powered by: newtelligence dasBlog 1.9.7174.0

    The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

    Send mail to the author(s) E-mail

    Theme design by Jelle Druyts