http://blogs.msdn.com/arpans/archive/2005/11/17/494143.aspxAt IT Forum, I presented CMS and SPS futures. That's right, CMS futures. :-) Session feedback was very positive... The only place I got dinged was for attempting to cover too much: SPS, Search and CMS in 75 minutes to be precise. I did about 30 minutesen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/arpans/archive/2005/11/17/494143.aspx#494242Fri, 18 Nov 2005 05:23:39 GMT91d46819-8472-40ad-a661-2c78acb4018c:494242ConradThis sounds interesting. So will ALL of the public API's for a WSS site and server be exposed through the WSS web service (as of today, only a limited set are available)? <br> <br>Since WSS stores all of the site content in the SQL DB, will this now store custom ASP.NET based application/content as well?http://blogs.msdn.com/arpans/archive/2005/11/17/494143.aspx#494294Fri, 18 Nov 2005 08:26:27 GMT91d46819-8472-40ad-a661-2c78acb4018c:494294arpansWeb content will be stored in a SharePoint list. So this will be accessible via web service just like list data is accessible today. Not all your custom ASP.NET application will be stored in WSS... but items like Master Pages and Page Layouts (the analogy to CMS Templates) will be stored in SharePoint galleries allowing you to apply workflow to them, for example. <br> <br>As for all public APIs for WSS exposed via XML web services... not sure what the final list of out of the box web services looks like yet.http://blogs.msdn.com/arpans/archive/2005/11/17/494143.aspx#577695Mon, 17 Apr 2006 21:36:56 GMT91d46819-8472-40ad-a661-2c78acb4018c:577695Andrew Connell [MVP MCMS]