Hans Muster's Library tagged webservice →  View Popular

Microsoft SharePoint contains functionality for Records Management, which essentially is a storage for documents that you would like to store and manage in a separate records center to meet certain legal or other requirements or just to make backups of certain document revisions. To be able to create a Records Center you need to have Microsoft Office SharePoint Server 2007 (MOSS). On the other hand you only need Windows SharePoint Services 3.0 (WSS) to send documents to the Records Center.

You configure the Records Center connection in the Central Administration. When connecting to the Records Center all you do is specify a Url to a web service and a name. The Url points to a special MOSS web service called OfficialFile.asmx (http://server/_vti_bin/OfficialFile.asmx). Your receiving Records Center server does not have to be in the same farm as from where you send the document (and it should probably not be either). Another thing is that the receiving Records Center does not even have to be a SharePoint server. It's just a web service and we can implement it anywhere we like.

I thought why not implement it using the Windows Azure technologies? This would be a great solution when you do not want to invest in either MOSS or a new MOSS farm, when you really want your important documents to be stored on a completely different physical location etc.

www.wictorwilen.se/...SharePoint-Records-Center.aspx - Preview

azure cloud sharepoint moss recordsmanagementcenter programming webservice

Recently I had a client request an animated carousel or filmstrip like player for displaying both images and embedded .wmv videos on their SharePoint intranet. The idea is to display many images and videos without taking up a ton of screen space in the process. Also, they wanted to be able to manage what images and videos get displayed via a standard SharePoint list, i.e. they could add links and descriptions in the SharePoint list and those would display appropriately in the filmstrip.

sharepoint.microsoft.com/...Post.aspx - Preview

silverlight sharepoint moss webservice

app-store.appspot.com - Preview

itunes webservice apple

For a Web service to act as a Records Center Web service for Windows SharePoint Services, it must implement the methods defined in the Records Center Web service description. This service description defines the following methods:

msdn.microsoft.com/...aa979507.aspx - Preview

moss webservice msdn recordsmanagementcenter

If you've ever designed and deployed a form that will be frequently used or require significant data analysis, you have probably looked into maintaining data in a SQL database. With InfoPath 2003 and the InfoPath 2007 rich client, you get what you expect. You create a main database data connection to the SQL server and pick tables and columns that meet the requirements for submit functionality. When you open your form and click the "Run Query" button, you see the data pulled from the database as you'd expect. You then happily insert, update, or delete records and, when the time is right, hit "Submit". Luckily for you, the InfoPath client took care of maintaining the list of changes that you made while editing your form. With this list of changes intact, your updated data streaks back to the database to await the next query.

blogs.msdn.com/...n-infopath-forms-services.aspx - Preview

infopath blogarticle webservice submit database .net programming

Windows Communication Foundation (WCF) Hands-on Lab

Encouraged from the positive feedback in terms of number of participants and attendees’ comments, this week the Swiss MSDN Team hold once again another Hands-on Lab here in Wallisellen. This time the topic was Windows Communication Foundation (WCF), the powerful Microsoft technology to built service-oriented systems, based on connected services and applications.

The lab was divided into 2 parts. In the first part, after a short introduction about the technology, people where required to build a service that exposes 2 endpoints: one available for external communication, for clients on platforms others than windows, accessing the service using HTTP and SSL (to guarantee confidentiality); and another one for internal windows clients (for communication inside an organization within a windows environment) accessing the service using TCP.

In the case of the TCP Endpoint people were asked to use Windows Integrated Security as authentication mechanism, while for the HTTP Endpoint, basic authentication in combination with SSL was used.

The last part of the lab showed attendees how to host a service inside Internet Information Server 7 with WAS (Windows Activation Services), which offers for the first time support for non-HTTP Protocols inside IIS.

blogs.msdn.com/...undation-wcf-hands-on-lab.aspx - Preview

wcf hands-on_labs microsoft blog gettingstarted knowhow .net programming webservice

blogs.msdn.com/...een-asmx-and-wcf-services.aspx - Preview

.net .net30 blogarticle interop programming wcf webservice

www.toodledo.com/index.php - Preview

free gtd onlineservice organizing todo web2.0 webservice