It has been a long time coming and I was finally able to find a diamond in the rough by locating a wrapper for the “challenging” yet powerful Lists.asmx service provided by WSS 3.0. On my current project we had the need to interact with WSS to pull back some document templates that reside in a document library. It only made sense for the implementation of this repository to use Lists.asmx or interact with a custom service that uses the SharePoint object model. I figured by now someone had created...
This past week I was reminded of the “fun” in which hosting an application within SharePoint can present. We are developing a custom application for our client in which some areas must reside within a SharePoint environment. We did quite a bit of our development in this first iteration within a web application in order to pull things together and present the client with a working end-to-end “prototype.” The architecture is composed of several layers all of which will be “in process” communications...
If WSS is free then what are the limitations? There is nothing good that is completely free, right? According to what I have found, if you setup WSS using SQL Server Embedded Edition (on the same server and not Express), then there is not a size limit. You have to setup WSS with the Basic option in order for it to install SQL Server EE (not Express); otherwise Express is installed and there is a 4 GB limit. Some are saying 500 GB may be a size constraint with EE, but I am not sure. SQL Server EE...