View Complete Post
SharePoint 2010 introduces a number of new ways to access business data and present it to the user. We'll show you several options that range from no-code solutions to fully integrated Office add-ins.
Donovan Follette , Paul Stubbs
MSDN Magazine July 2010
The Model-View-ViewModel (MVVM) design pattern describes a popular approach for building Windows Presentation Foundation or Microsoft Silverlight applications. Robert McCarter shows you how the ViewModel works, and discuss some benefits and issues involved in implementing a ViewModel in your code.
This article explains how you can use Active Directory Federation Services (AD FS) 2.0 to claims-enable Windows Communication Foundation (WCF) services and browser-based applications. The focus is on the token issuance functionality in AD FS 2.0. You'll find out how to use AD FS 2.0 as an identity provider; set up an AD FS 2.0 security token service (STS) to interact with WCF; federate AD FS 2.0 with your custom STS or another AD FS 2.0; enable Web single sign-on and federation with WS-Federation and SAML 2.0 protocols; and externalize authentication logic through Visual Studio. You'll come away appreciating how AD FS 2.0 and Windows Identity Foundation make programming identity solutions in Windows less of a chore.
MSDN Magazine November 2009
The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.
Here we summarize a number of best practices for developing SharePoint solutions.
E. Wilansky, T. Stojecki, P. Olszewski and S. Kowalewski
MSDN Magazine March 2009
Mike Volodarsky demonstrates the IIS 7.0 extensibility model by extending the Response Modification into a configurable Web server module and a custom management page for IIS Manager.
MSDN Magazine Launch 2008
With Visual Studio Tools for Office you can easily build Office-based services that harness the power of Windows Communication Foundation, Windows Presentation Foundation, and LINQ.
MSDN Magazine December 2007
Use BizTalk Server to monitor e-mail for new messages, trigger confirmations, and persist e-mail and attachments to a custom database.
MSDN Magazine December 2006
Microsoft Visual Studio Tools for the Microsoft Office System is a new technology that brings the advanced features of Visual Studio .NET and the .NET Framework to applications built for Microsoft Office Word 2003 and Microsoft Office Excel 2003. Deploying solutions built with this technology requires that you understand how runtime security is enforced in managed applications and how to configure users' systems to run your solutions without introducing security holes.To promote that understanding, this article will demonstrate how to establish trust, explain policy considerations and permissions, and explain what trusted code is all about. Secure assembly deployment is also covered in detail.
Brian A. Randell and Ken Getz
MSDN Magazine March 2004
Microsoft Visual Studio Tools for the Microsoft Office System is a new technology that brings the advanced features of Visual Studio .NET and the .NET Framework to apps built on Microsoft Word 2003 and Excel 2003. Now you can use Visual Basic .NET and C# to write document-centric, managed code solutions that run in-process with Word 2003 or Excel 2003, taking advantage of the rich object models they expose. Along the way you get the benefits of the managed environment in which a fully compiled .NET-based application executes, including code access security.
Ken Getz and Brian A. Randell
MSDN Magazine September 2003
Using XML for data access allows you to separate the data from the presentation, and promotes reuse, extensibility, and division of labor. XML also has a simplified data model, which promotes easier testing. This article presents and compares five data access approaches, using a variety of technologies including ASP and ADO, XSLT, and DirectXML. Once built, the solutions are compared on the basis of their speed and efficiency.
Scott Howlett and Darryl Jennings
MSDN Magazine January 2002
The combination of XML and XSL can provide a powerful alternative to ASP development. This article presents arguments for building even small-scale Internet applications on the XML model. An example written with traditional ASP programming is compared to the same example written with XML and XSL in order to show the benefits of this approach. The example is followed by nine good reasons to make the switch. These reasons include separation of presentation and data, reusability, extensibility, division of labor, enhanced testing, and legacy integration. The XML/XSL solutions described hold the promise of greater simplicity, flexibility, and durability than ASP solutions built the traditional way.
Scott Howlett and Jeff Dunmall
MSDN Magazine November 2000
MSDN Magazine August 2000
Recently I've been busy with a research on accessibility of Web Content ManagementÃÂ solutions based on SharePoint 2007. My outcome is: SharePoint 2007 WCM solutions can be accessible and depending on the approach you canÃÂ score up to 95% WCAG 1.0 Priority 2.0 compliancy without any toolkit.
I've been wondering whether anybody else shares my opinion or has his/her own...
I am trying to migrate from my moss 2007 installation from server 2003 r2 servers to server 2008 r2 servers, in order to get ready for the migration to sharepoint. I have everything installed and have restored backups of my content databases to the
new servers as well as brought over the 12 hive.
When I go to install a solution, it tells me the feature as already been installed (Im guessing because it sees its folder in the 12 hive that I brought over), but when I try to use the feature it bombs out, because I believe its not really installed.
Whats the best way to go about this? I have tons of pages, images, resource files in my 12 hive, and believe the only realistic way to get all that stuff over to the new farm is to copy over the whole 12 hive.