<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Case Study</title>
<link>http://dotnet.sys-con.com/</link>
<description>Latest articles from Case Study</description>
<copyright>Copyright 2008 .NET DEVELOPER&apos;S JOURNAL</copyright>
<lastBuildDate>Thu, 22 May 2008 17:30:00 GMT</lastBuildDate>
<generator>.NET DEVELOPER&apos;S JOURNAL</generator>
<ttl>10</ttl>
<docs>http://backend.userland.com/rss</docs>

<item>
<title>Integrating Content and Search Results with SharePoint</title>
<guid isPermaLink="true">http://dotnet.sys-con.com/read/497159.htm</guid><link>http://dotnet.sys-con.com/read/497159.htm</link>
<pubDate>Sat, 16 Feb 2008 12:00:00 GMT</pubDate>
<description>Have you ever needed to integrate an external system with SharePoint, showing content from each system within the other? What if you needed to integrate search between SharePoint and an external system? How do you keep the user experience seamless if the systems use different authentication mechanisms? Have you wondered if this can be done if the external system is written in Java?</description>

</item><item>
<title>Extending SourceSafe for Internet and Cross-Platform Development</title>
<guid isPermaLink="true">http://dotnet.sys-con.com/read/478963.htm</guid><link>http://dotnet.sys-con.com/read/478963.htm</link>
<pubDate>Thu, 27 Dec 2007 10:45:00 GMT</pubDate>
<description>Shipped as a part of Microsoft Visual Studio, SourceSafe sells more than $40 million (US) per year (Source: IDC) and is a very popular version control program for Windows developers. As the teams go distributed and cross-platform, the limitations of SourceSafe rise to the surface. In fact, there has been a lot of negative press about the drawbacks of SourceSafe.</description>

</item><item>
<title>How SI International Leveraged Microsoft SharePoint &amp; CorasWorks</title>
<guid isPermaLink="true">http://dotnet.sys-con.com/read/478932.htm</guid><link>http://dotnet.sys-con.com/read/478932.htm</link>
<pubDate>Sat, 22 Dec 2007 16:00:00 GMT</pubDate>
<description>SI International (www.si-intl.com) is a provider of information technology and network solutions, primarily to the United States government, But due to its continued success in defining, designing, building, deploying, and operating mission-critical solutions for the Department of Defense and several federal civilian agencies, business at SI International (SI) has been strong and growing.</description>

</item><item>
<title>Mercado Eletr&amp;ocirc;nico Case Study</title>
<guid isPermaLink="true">http://dotnet.sys-con.com/read/461418.htm</guid><link>http://dotnet.sys-con.com/read/461418.htm</link>
<pubDate>Mon, 19 Nov 2007 12:00:00 GMT</pubDate>
<description>Mercado Eletrônico is the leading B2B company in Latin America. Founded in 1994, it provides services for supply chain management, such as e-procurement, catalog, sourcing and collaboration, based on an advanced technology platform supporting more than 30,000 transactions a day and a complex buyer/supplier user community.</description>

</item><item>
<title>SharePoint 2007 - Best Practices for Collaborative Portals</title>
<guid isPermaLink="true">http://dotnet.sys-con.com/read/461380.htm</guid><link>http://dotnet.sys-con.com/read/461380.htm</link>
<pubDate>Fri, 16 Nov 2007 02:00:00 GMT</pubDate>
<description>It was the usual story: a short deadline and a tight budget. The client&apos;s internal staff said &apos;No way&apos; to build the Web-based application in fewer than six months, with any fewer than three full-time resources. The project needed to be completed in two months. It included custom authentication, collaboration, business rules, and forums. Therefore we chose SharePoint 2007 as the development platform and configured the solution to handle 80% of the functionality. Where SharePoint could not meet the requirements through configuration, we developed custom code to complete the other 20%. Herein we&apos;ll detail some best practices and lessons learned from our implementation.</description>

</item></channel></rss>