Tuesday, December 28, 2004
Monday, December 27, 2004
Friday, December 24, 2004
"Today's reliance on e-mail has changed the nature of vacation," said James E. Katz, director of the Center for Mobile Communication Studies at Rutgers University.
If you do clean your in-box, he said, you're "defeating the purpose of vacation, which is to get away from the office and do something different."
If you don't, "you have to work twice as hard when you come back," he said. "And while you are responding to those, new ones come flooding in." In some ways, he said, "you are punished for taking vacation, by out-of-control e-mails."
Thursday, December 23, 2004
Wednesday, December 22, 2004
Tuesday, December 21, 2004
" Space Name: portalgeek
Space URL : http://spaces.msn.com/members/portalgeek
Photo Album: Sketches
Photo Description: Inappropriate content (pornography)
If you remove the said materials, your space will be again in compliance with the MSN Code of Conduct and will remain open for your access. Otherwise, we will be forced to close down your space.
We hope you could bring your space into compliance as soon as possible.
MSN Spaces Customer Support "
By the way, check them out anyway on my other blog http://jopxpaints.blogspot.com
Sunday, December 19, 2004
Friday, December 17, 2004
Thursday, December 16, 2004
Wednesday, December 15, 2004
Tuesday, December 14, 2004
Monday, December 13, 2004
This weekend I took a look at the Office Business Scorecards Accelerator and I have to tell that I'm pretty impressed. Most of the BI solutions that I know require very high end ( and also high price) products but for people who have already an existing Microsoft based infrastructure with Windows 2003 and SQL Server, this solution is a very nice starting point to deploy a flexible scorecard solution. I'm under the impression that this accelerator is not very known within the market although it is a very good value solution. I think that the next couple of weeks I'm going to write a little bit more about how you should implement a scorecard solution based on Office Business Scorecards accelerator. So lets start of with a quick introduction...
The Microsoft Office Business Scorecards Accelerator enable employees at all levels of the organization to simplify the measurement and management of key performance indicators (KPIs) and business strategies. It does this by simplyfying the creation of so called scorecards, the mapping of real data to the measures in these scorecards and providing a customizable visualization of these scorecard. The solution is targeted at decision makers at different levels in your organisation.
II would love to hear of people who have project experience with this solution. So if you have some nice tips and tricks, sample code, ... do not hesitate to comment on this posting.
Saturday, December 11, 2004
Maybe these shortcomings are only so conspicious when you have already some experience with SharePoint, but anyway this is not an excuse, these MOCS definitely need improvement. Of course,if your trainer is good, it makes a world of difference ;-) ...
This posting does not reflect the views of my employer
and is provided as is with no warranties, and confers no rights.
Tuesday, December 07, 2004
Monday, December 06, 2004
Thursday, December 02, 2004
Navigation and UI enhancements
Wednesday, December 01, 2004
But this time it is different, although the newslines seem to be the same see Browser Wars Back On. This is not a for profit company, this is Open Source. And it looks as if Firefox is actually gaining ground... I just took a look at which browsers people are using to visit this blog. Amazing....
Something that is however not discussed in most articles is the fact that people are not only using browsers but also news aggregators to surf the Net. Since I read a lot of blogs, I think that the majority of the time I use RSS Bandit when accessing the Internet.
But the hype about SOA will revive the interest in webservices because web services are one of the enablers of SOA. Web services are currently the first universally accepted interface, every software vendor or product has SOAP support. Web services allow us to define a software architecture in which the services are the core.
A while ago, I blogged about SOA, but lets recap, what is SOA? Actually it is nothing more then a design philosophy, a philisophy which is governed by 4 tenets:
1. Services have explicit boundaries : only interaction possible at the service boundary - e.g. Asmx webservices
2. Services are autonomous : no assumptions about how the service is implemented, loosely coupling
3. Services share schema & contract not objects : "pass by value" - the WSDL contains both the service and the data contract
4. Services are policy based : policies describe the rules for interaction, transactions, security, wire protocol
These tenets have also some technical consequences however, such as:
when you have to implement a custom wire format (For more elaborate discussions, take a look at Clemens Vasters blog). One fo the reasons you should avoid Remoting is because it uses SOAP encoding differently from web services
Sunday, November 28, 2004
When a .vsdisco file is requested, the .NET framework analyzes the directory in which the .vsdisco file is located, as well as that directory's subdirectories and returns markup that contains references to all web services in that directory and the directory's subdirectories (It is however possible to exclude some directories from being searched).
A vsdisco file would look this
<?xml version="1.0" ?>
<exclude path="_vti_cnf" />
<exclude path="_vti_pvt" />
<exclude path="_vti_log" />
<exclude path="_vti_script" />
<exclude path="_vti_txt" />
Dynamic discovery is however disabled by default. With the .Net framework you had to remove the comments from the following lines in your machine.config. With the .Net framework 1.1 these lines are removed from the machine.config so you have to add them yourself.
<!--<add verb="*" path="*.vsdisco"
System.Web.Services, Version=1.0.3300.0, Culture=neutral,
As you can see dynamic discovery is accomplished in ASP.NET by mapping the file name extension VSDISCO
to an HTTP handler that scans the host directory and subdirectories for ASMX and DISCO files. For more info about http handlers definitely take a look at Using HTTP Modules and Handlers to Create Pluggable ASP.NET Components
Saturday, November 27, 2004
Is WIFI finally becoming mainstream? From personal experience I find it still not very easy to use and I actually got some problems after upgrading Windows XP to SP2. Before SP2, the connection speed switched between 1MB, 10 MB,... up untill 54 MB. Now, it just stops at 1MB and don't changes... anybody any ideas?
Well, one thing that has changed with SP2 for the better, is that you can actually repair your connection now. If you right clicked your connection pre SP2 and clicked repair, it just stalled... now it works.
Wednesday, November 24, 2004
Tuesday, November 23, 2004
Monday, November 22, 2004
Sunday, November 21, 2004
Microsoft KB820328: "SharePoint Portal Server 2001 will not function on Windows Server 2003 because of incompatibilities between the versions of the Microsoft Web Storage System and Microsoft Internet Information Services (IIS) 6. There are currently no plans to release an update to the Web Storage System in SharePoint Portal Server 2001 to make it compatible with Windows Server 2003."
There are some tools available to ease a migration, such as SPIN and SPOUT. SPOUT is a document library Export Tool for SharePoint. SPOUT will export the workspace document library content as an XML manifest file and the individual content files. The XML manifest files is used to describe the different objects and properties of the documents. After running, SPOUT will generate 3 files:
I did some testing with SPOUT a while ago, just to get an idea how fast it would be. I ran it in a test environment with Windows 2000SP4, 512 MB RAM,SharePoint Portal Server 2001 SP2a, .Net Framework 1.1. On average I got export times between 1 and 3 secs per file with file size as the most important factor. Even when this would run twice as fast in a production environment time is still a limiting factor, exporting about 100000 files would take about 27 hours. You should also take into account the size of manifest.xml file, since XML parsing can become quite troublesome when your XML files contain a lot of data. (Tip : use Xpath queries since XMLDom manipulations can be very memory intensive, qua memory usage can run as high as 10 times the original filesize.)
|Number of files||Size manifest.xml||MBs exported||Duration|
|Test 1||69||96K||42.9||41 sec|
|Test 2||154||216K||48.6||55 sec|
If you want to try out some alternative tools for export and import you should definitely check out this GotDotNext workspace. Before starting a migration, take a look at the following links:
Saturday, November 20, 2004
Friday, November 19, 2004
The concept of ghosted pages is something that you have to understand when customizing SharePoint. All items in SharePoint are by default stored in the database, but some aspx pages are not stored in the SharePoint database but on the file system, e.g. default.aspx for each site and also the search.aspx page for SharePoint Portal Server. These pages are called ghosted pages. These pages are pulled from the cache at runtime and therefore it will increase the scalability from the system since all uncustomized pages are reused accross all of the sites and there is no unnecessary data storage or retrieval.
But these ghosted can become unghosted when they are modified with e.g. FrontPage. However FrontPage is not the only culprit, when you modify one of these pages through webfolders with notepad, then the page will also become unghosted. These unghosted pages are stored in the database. Normally if a page which is used in a site definition is changed, this change will apply to all sites created with this site definition,but if you're page is unghosted this will not happen. There is also a slight performance impact of about 10% between ghosted and unghosted pages because the files are being read from the database instead of the cached filesystem. You can check if a page has become unghosted with ghosthunter utility or by checking the vti_hasdefaultcontent field obtained through the Properties property of the SPFile object.
There have been a lot of postings about ghosted and unghosted page and the role of Frontpage in this issue, take a look at them, they will provide more detail about for example the difference in parsing, so check them out
Wednesday, November 17, 2004
When we think about developing on the SharePoint platform, the first thing that comes to mind is webpart development but there are actually more development tasks with SharePoint:
- Web part development : one of the SharePoint development topics which gets the most attention
- Developing with SharePoint lists : involves creating xml schema definitions, writing SharePoint Object Model code, adding your own UI
- Writing custom workflow: SharePoint does not provide workflow out of the box but allows you to add your own workflow through the use of eventhandlers
- Customizing SharePoint UI : starts from simple things like changing stylesheets, images and logos to create completely new site templates
- Extending and customizing SharePoint search
In the coming weeks I will write more postings about SharePoint but in this first posting I'm going to focus on webpart development. You should approach webpart development as any other programming task.
- Make sure you understand the basics. A good article to start with is A developers introduction to webparts on MSDN or The definitieve hello world webpart from John Durant
- Think about the design, what you want to accomplish. Since webparts are basically enhanced ASP.Net server controls which live in SharePoint context, the number of options are immense. But you also have to think about the enhancements which are provided by the webpart framework. So if you want to just display data maybe think about using the dataviewwebpart for the moment and don't immediately start with a datagrid. Know the potential of connectable webparts. Definitely check out the 3 articles from Patrick Tisseghem:
- Webpart basics
- Webparts and usercontrols : this is definitely the fastest way to develop webparts, instead of writing everything yourself, you can use usercontrols which are loaded by the webpart
- Connectable webparts
- Webpart basics
- Developing and debugging For debugging definitely check out this posting
Debugging Web Parts - a full explanation of the requirements Something which is also easily forgotten is that you can also force a debug from within your code with the following statement System.Diagnostics.Debugger.Break()
- Deploying and testing: Deploying webparts isn't that simple, but there are some nice tools out there to help you with the deployment such as InstallAssemblies. I recommend however doing all the steps manually a couple of times, this will help your understand how SharePoint works. One of the nicest tools to aid in deployment is wppackager. WPPackager will create MSIs to install the webparts. For testing your webparts you should take a look at
Testing webparts checklist on MSDN
Tuesday, November 16, 2004
Monday, November 15, 2004
I have been using the .Net application blocks for quite a while now and it is great to see that they will have a successor in the future, check out the blog of Scott Densmore,Enterprise Library 'The Day After'.For those of you who don't know the application blocks, take a look at them. Application blocks are basically parts of code which can be freely downloaded from MSDN, they contain samples and source code so you can easily extend them. They are written with best practices in mind and are nicely documented.
Overview application blocks
Sunday, November 14, 2004
If you want to know what other people say about it, take a look at
Saturday, November 13, 2004
Office Information Bridge Framework (IBF) is a new solution that provides a standardised way for developers to integrate data from enterprise applications (CRM,HR, ERP,...) into Office. IBF is an example of a service oriented architecture in which your LOB applications are connected to Office through a webservices layer. At the clientside IBF leverages the smart tag and smart document functionality of Office 2003 Professional.
will includes the familiar Microsoft Office 2003 programs as well as an updated version of Microsoft Office Outlook 2003 with Business Contact Manager and Microsoft Office Small Business Accounting—a new, comprehensive financial management package. So also take a look at http://msdn.microsoft.com/isv/technology/sba/ I guess that when Microsoft will get the localization issue right, it will even become popular worldwide. But don't put your bets on it yet , II overheard saying that Microsoft seems to think that localization is the difference between English UK and English US, ... :-)
Friday, November 12, 2004
The last couple of months I have been doing a lot of Microsoft Content Management Server (MSCMS) development and I think it definitely allows you to do some cool stuff. For those of you who don't know, MSCMS allows users without any html knowledge or special tools to publish content to a corporate website while maintaining a common look and feel and supporting an approval process for all of your published content.
The product has however some shortcomings and last week the functional analyst of our project stumbled on one of them. For every posting you can define an approval process with authors, editors and moderators, so after an author creates a posting, the editor first approves the layout and then the moderator approves the content (This is a very quick overview). So for about every change, you need to go through this approval process EXCEPT for deletion of postings
The obvious thing todo to disable the delete for authors was to add an ASP.Net panel control around the delete section in the defaultconsole.ascx and put it to visible false when a user had no editor or approve rights. Well this doesn't seem to be very simple:
So basically I'm stuck, anybody any ideas....
Thursday, November 11, 2004
Tuesday, November 09, 2004
Sunday, November 07, 2004
One of the hottest topics lately seems to be Service Oriented Architecture and how to implement it. But it is also a major source of confusion and I think that for most developers, SOA is still a big mystery. The main problem seems to be that we have to translate these high level concepts to low-level code, because in the end we just like to write code. However I still think that SOA is an important concept that every developers needs a basic understanding about, so the next couple of weeks I'm going to try to write some posting about SOA, providing some summaries of presentations that I saw and links to interesting sites and blogs.
Lets start with the basics, what is SOA? At PDC 2003 Pat Helland gave a presentation about SOA. The key message was the following:
Definitely check out Pats blog if you want to read more interesting stuff...
A couple of months later I saw a presentation from Clemens Vasters, he mainly talked about the same concepts but things got a little clearer. There are only 2 types of services, message producers and message consumers. The messages flow through "pipelines", a pipeline is a sequence of services and each service transforms the message. He also gave some concrete tips :
Now if you want to know more about it, check out:
java.lang.RuntimeException: Unable to load blog object for blogID: 7753577
.... and so on.
Friday, November 05, 2004
Thursday, November 04, 2004
Wednesday, November 03, 2004
The last couple of days I worked at a customer who was using Citrix Metaframe Presentation Server 3.0, it was the first time that I saw this product and I have to admit that I'm impressed. It enables user to start their everyday applications from within a browser environment. It was great to see that the web interface used ASP.Net and the nice thing is that you can completely customize it. If you run into problems, definitely check out the Citrix support site .
After developing the UI we deployed it to a production server on which a previous version of Metraframe was running as well so we didn't do an install but copied the directory with the files and created the necessary virtual directories. Everything worked except the ICA files were not correctly handled. It seemed that we still associate the ICA extension with the aspnet dll in IIS.
After installing ASP.Net, we however noticed that some of the users which were still using the Citrix 1.5, had problems logging into the web applications. They got a very strange error "error while encoding a gif file". It seems that while installing ASP.Net some userrights were removed. If you encounter this error, just give the anonymous user access to the nfuseicons directory
One of the most posed questions lately seems to be how do we integrate SharePoint and Content Management Server. People often start working together on documents in SharePoint and later want to publish this document in an easy way to CMS (That authors can't work together on a CMS posting - because of the locking principle - is definitely a missing feature in CMS). With the release of SharePoint Connector for Content Management Server (Previously codenamed Spark) in february 2004- some things were solved.
In short the connector enables the following :
- Content from CMS can be displayed in SharePoint webparts
- Documents in SPS can be exposed to MCMS managed sites
- Integrating SPS search with the content in CMS
- Emmanuel Desigaud wrote a paper that shows how to integrate SharePoint Server 2003 Search into a MCMS site using a WebService
- If you need more info about CMS in general, check out the blog of Stefan Gossner and Mark Harrison. These are definitely resources you can't affort to miss.
- Review of the MCMS Connector for SharePoint Technologies by Stephen Huen. He also added a set of user controls to Code Project, which are used to Search CMS with SharePoint
- How to maintain a Microsoft Content Management Server database
Tuesday, November 02, 2004
Monday, November 01, 2004
When you are living in a country which has 3 official languages like me - yes we have Dutch, French and German in Belgium - multilanguage definitely becomes an issue when doing a portal implementation. Unfortunately multilanguage is not a very strong feature in SharePoint. Windows SharePoint Services allows you to choose a different language at the moment of site creation when you install language packs, once the site is created it is not possible to switch the language anymore. For SharePoint Portal Server it is even worse, it only support the language of the SharePoint installation, so if you want to have a French Portal you have to install the French version of SharePoint Portal Server. There are however some articles which can guide you, but better multilanguage functionality is definitely something I want to see in the next version of SharePoint. One of the things I noticed which were very hard to find where the way of working of thesaurus files in SharePoint.The best documentation is found in the SPS 2001 Resource Kit and still seems to be correct. Another interesting document is the one on Technet which describes the international features of SharePoint 2003.
I tried out the feature of expansion sets in SharePoint 2003 and how it works with files which have different languages and different formats. SharePoint uses thesaurus files to enhance its search functionality. The thesaurus allows you not only to search for the search term, but also for synonyms and other matching words, like words with the same stem. You can expand the thesaurus by adding tags to the thesaurus file(s). For example, when a user searches for ‘apple*’, you want to automatically search for ‘pomme*’ and ‘appel*’ as well so that documents containing the French and Dutch translations of the word ‘sugar’ will be added to the search results. This is an example of stemming. An expansion set for the word "author" is for example that it searches for documents containing "writer"
There are different thesaurus files for every language, these are xml files - e.g. tsneu.xml is the neutral thesaurus file,tseng.xml is for English, tsnld.xml is for Dutch. The easiest way to test it, is to modify the xml files at local_drive\Program Files\SharePoint Portal Server\Data\Applications\Application UID\Config and then restart the service Microsoft SharePointPS Search.
I added the following lines to the xml files
Well it seems that depending of the file type a different thesaurus file will be used, this happens because of the way how iFilters are implemented.
Then I tried the search for different file types :
Miscellaneous SharePoint links:
Thursday, October 28, 2004
I presented some workshops around SharePoint technologies the last couple of months and one of the things that I always include is a quick overview and some demos of InfoPath . It seems that this is still one of Microsofts best kept secrets - both developers and IT decision makers seem to have little or no knowledge about this tool. For those of you who haven't heard about it, InfoPath is a tool for designing electronic forms and the coolest thing is that underlying it uses nothing but XML.
I demo it in SharePoint workshops because of the excellent way it integrates with SharePoint through form libraries but you can also use it without SharePoint. Mostly I start off with the Microsoft Office InfoPath 2003 HL7 CDA Demo. It is easy and understandable, just as a demo should be.
One of the major downsides of this product is however that every user needs a complete installed version. I think it would be much more popular if there would be a developer edition (to actually create the forms) and a freely distributable runtime for users who only use InfoPath to fill out forms. The InfoPath Viewer application that Mark Bower created is a good start but it is not enough especially because InfoPath is not standard available in all Office 2003 versions, only in the Professional Enterprise version.
Yesterday I saw another Technet presentation - this time about InfoPath and SharePoint, the presentation was done by Jelle Druyts and Yves Kerwyn. Microsoft positions InfoPath as "The smart client for webservices". Well it seems that it is still lacking some features to be a really smart client. The first missing feature is support for different devices - there's for example no InfoPath for Pocket PC. The other feature is missing Offline support. Microsoft says that InfoPath supports offline scenarios through the use of Outlook outbox but this is not really an ideal scenario. Jelle Druyts presented a solution for supporting offline usage by showing us some code. I can't wait until we can download this code, must be very interesting.
- InfoPath 2003 labfiles
- MSDN article about the File Attachment control in InfoPath 2003 SP1, how to include it in a form, and how to work with it programmatically,....
- Posting from Mark Bower, about choosing between InfoPath and Smart Document Solution
- John Durant has a listing of InfoPath resources as well.
Tuesday, October 26, 2004
Monday, October 25, 2004
I saw a MSDN evening session in june 2004 on SharePoint customization from Patrick Tisseghem but only found the time to
start playing around with Frontpage and SharePoint today,... well better late than never. It seems that there are a lot of things you have to think about when doing SharePoint customization, luckily I found a lot of information on the Internet.
- Of course the first thing I stumbled upon when playing around with SharePoint was the "Initializestrings method returned an incorrect number of strings" error when trying to modify the webpart properties from within Frontpage. Luckily Microsoft has a support article about this issue. And another one which can be helpfull as well. (It seems that once you start fooling around with SharePoint the problems keep on coming,... luckily most of it can be avoided once you know them.)
- Next I found this article describing the problems with Frontpage customisation, the author of this article, Barry Kouda, has on the member pages of his site a word document which clearly describes the inner working of SharePoints site definitions.
- Daniel McPherson also has some nice blog entries which can help amongst them How to create a footer in SharePoint
- Serge van den Oever wrote a blogentry about the DataView webpart , this is indeed a great webpart to quickly create views upon XML data and you definitely need FrontPage if you want to work with it. There is also a great article on MSDN about this subject - Building XML data driven websites with Frontpage 2003
In the meantime I have messed up my SharePoint VPC image so much that I think I need a rollback,... well at least it has been fun....
Sunday, October 24, 2004
- Web capture : with the page viewer webpart and the webcapture webpart (not standard installed but can be downloaded as part of the Office 2003 webparts), SharePoint can display information of LOB (Line of Business) applications such as SAP, if these applications have a webinterface. The most important limitation of this scenario is the limited level of interactivity.
- Point to Point connection : through the SAP .Net connector - available for SAP systems starting from release 4.0B so for all SAP R/3 systems as well as the SAP Web Application Server - it is the point to create a direct connection to SAP. This is however not always feasible nor desirable from a security standpoint.
- Data cache : by creating a datawarehouse which centralises all information for different LOB systems when can create a more secure and scalable solution than the direct connection. However all data has to be replicated and this scenario is perhaps best suitable for readonly access.
- Application/Integration server : through the Biztalk SAP adapter it is possible to exchange data with SAP.
Mid august Microsoft released through their “shared source” program a couple of new “enabling technologies” which can help in realising some of the scenarios described. These are the WSRP Web Part Toolkit for SharePoint (WSRP =Web Services for Remote Portlets) and the SAP iViews Web Part Toolkit. These toolkits enable sytem integrators to create a customer specific solution based on the toolkit framework.The iView webpart makes it possible to display information from SAP directly into SharePoint The WSRP toolkit is directed towards providing SharePoint functionality through an enhanced webservices layer to 3d party LOB applications.
Lately Microsoft seems to be putting a lot more effort into integration with the SAP platform, a lot of documentation you can find on their joint website, http://microsoft-sap.com
Thursday, October 21, 2004
Monday, October 18, 2004
A clear explanation about it is found on Microsoft Monitor, read the full article at Google Desktop Search and Microsoft. Some other interesting ideas are described in a blog posting of Patrick, Google Desktop - What next?
Sunday, October 17, 2004
C# Gets Edit-And-Continue? BOOOO!!!!!
Saturday, October 16, 2004
Some other blogger who seem to have discovered this awesome tool,Jay Nathan, Lamont, Bryant Likes, Chris Meirick, Computer Zen, LongHornBlogs and Cyrus. All raving reviews...
Friday, October 15, 2004
Thursday, October 14, 2004
Tuesday, October 12, 2004
Friday, October 08, 2004
" System.Runtime.InteropServices.COMException: Server ODBC error. Contact the site administrator."
Stack Trace :
[COMException (0x80041b67): Server ODBC error. Contact the site administrator.]
Microsoft.ContentManagement.Interop.Publishing.IRcwPosting.__BeginWrite(Boolean ignoreMarkedForActions) +0
Microsoft.ContentManagement.Publishing.Posting.BeginWrite(Boolean ignoreMarkForActions) +47
Today I noticed the following blog posting about the mystery ODBC error on the blog of Mei Ying. The solution seems quite trivial but its something we tend to forget quite easily : if you use CMSApplicationContext in your code, call the dispose method when you have finished using it.
Tuesday, September 28, 2004
Mondosoft today announced the availability of a new .NET Search Kit that facilitates deployment of enterprise and site search in .NET environments. The Search Kit consists of a .NET search control and three easy-to-use search templates developed to complement MondoSearch’s .NET capabilities, and offer significant time and productivity benefits for our customers and partners.
All three search templates included in the .NET Search Kit categorize search results, display the results in differing contexts and represent a style and interface that is easily tailored to fit any functionality and design specification. One template is suited for multi-lingual sites, another is fashioned after popular global search result pages, and a third provides a clear, legible layout based on a three column format. Using an html or text editor, the Mondosoft .NET Search Kit allows easy deployment and tight integration of MondoSearch in .NET environments.
The .NET Search Kit is currently available for download at no charge to partners and customers with a valid support agreement. It installs on top of existing MondoSearch 5.1b installations only, and is ready to deploy in a matter of minutes. For more information and illustrations, and to download the Mondosoft .NET Search Kit, please go to www.mondosoft.com/SearchKit.
You can also sign up for a free webcast for a demo of the .NET Search Kit. Please sign up at www.mondosoft.com/webcasts.asp
Thursday, September 23, 2004
Mondosoft uses full text indexes to store the content it indexed from Content Management Server. If you forget to publish these indexes you will get the very unfriendly error shown above. Remember that you have to publish the index for every language that you setup in MondoSearch.
- All the functionality is completely programmable in .Net
- It works very fast
- The administration console is easy to use and completely webbased
- Support from mondosoft is excellent - I got a response by email for a problem in less than 15 minutes... amazing
There are however some downsides as well:
- The price tag is pretty steep
- When you make some configuration errors - your code will crash with not so helpfull error messages
- You have to change a lot of security settings to make the product work
- The information in the knowledgebase on their site needs some updating
In the next couple of postings I will explain some issues we ran into.