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
View Complete Post
We introduce you to the EDI functionality within BizTalk Server 2006 R2, illustrating schema creation, document mapping, EDI delivery and transmission, and exception handling.
MSDN Magazine August 2008
Jay Flowers demonstrates how to set up and use a Continuous Integration server using both discrete tools and the more comprehensive CI Factory solution.
MSDN Magazine March 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
In this article the author focuses on one critically important Web services specification that has been largely overlooked: the Business Process Execution Language for Web Services (BPEL4WS, or BPEL). He describes why BPEL is important and what it offers you if you are implementing Web services today or planning to in the future. Concrete examples using BizTalk Server 2004 are presented in the article.
MSDN Magazine March 2005
Once you've addressed security in your code, it's time to look at the environment it runs in. Firewalls stop unauthorized traffic from getting into your network, and smart Web service-specific firewalls, like the one that comes with Internet Security and Acceleration (ISA) Server 2004, bring XML intrusion prevention to your system for that added layer of safety.
MSDN Magazine November 2004
Many organizations analyze their business-critical data using Online Analytical Processing (OLAP) technology. OLAP-based data mining provides a way to query multidimensional data sets and drill down into the data to find patterns. ASP.NET and the Microsoft Office Web Components (OWC) enable Web-based OLAP reporting. The OWC controls include PivotTable and Chart components that can be embedded in a Web page and scripted by programmers. In this article, the authors build a Web-based OLAP reporting app using ASP.NET, OWC, and SQL Server 2000 Analysis Services to illustrate the process.
Jeffrey Hasan and Kenneth Tu
MSDN Magazine October 2003
Fortunately for developers, threading in ASP.NET is a lot easier than it was in ASP. In this article, the author takes a look at threading in the ASP.NET HTTP pipeline, and explains how threads are managed efficiently without the involvement of the developer. The article considers how the common language runtime threadpool is used by ASP.NET to service requests, looks at the pooling mechanisms used for handlers, modules, and applications, and covers both IIS 5.0 and IIS 6.0 and how they differ in their approach to request processing and thread allocation. Finally, how and when to use asynchronous handlers is discussed for developers who still need to use threads in their own applications.
MSDN Magazine June 2003
The adoption of wireless devices continues to spread unabated, and organizations are looking for new ways to get in touch with customers through these new mobile devices. In the past, unsuccessful ideas such as push technology were used to send targeted information to customers. Now, SQL Server Notification Services uses the SQL Server 2000 database engine and the .NET Framework to promote a new breed of notification applications that will allow relevant, consensual communications to be sent to any subscriber device.Here the author provides an architectural overview of the core features that make up SQL Server Notification Services. Along the way he discusses how they can be used for pushing Web content.
MSDN Magazine November 2002
XML is becoming the ubiquitous data format on the Web, and XML support in SQL Server is evolving to meet the additional demand. Using XML, SOAP, HTTP, and SQL Server, you can now build powerful Web Services easily. To show just how simple it is with SQLXML 3.0, this article walks the reader through the process step by step, from setting up a virtual directory enabling data access via HTTP to executing queries and building Web Services. Finally, the author illustrates the creation of two Web Services clients-one with C# that works with the Microsoft .NET Framework and one with the SOAP Toolkit 2.0 for anyone still using earlier development tools.
MSDN Magazine May 2002
SOAP opens up a new world of Web Services, letting you make function calls across a network or the Internet. But this flexibility creates new problems when your app needs to wait for calls to return from halfway around the world. What you need is an asynchronous SOAP client that takes advantage of threading to continue execution while waiting for calls over the wire. This article covers the basics of building such a client with ATL.
Pranish Kumar and Bogdan Crivat
MSDN Magazine April 2002
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
I need to find out the definitive answer to building 64 bit applications on a 32 bit build server.
For the final output of the build process I am trying to build MSI installers for x86 and x64, Debug and Release for my application.
I have read the post below, and it contains what seem to be many relevant points indicating that this is possible, the post does seem to be slightly older, hence I raise the question again.
My application is mostly managed code with some calls via PInvoke and COM to Native features of the target OS (Vista and Windows 7, 32 and 64 Bit versions).
I am building with VS2010.My local build machine is 64 bit Windows 7 but the TFS build server is Windows Server 2008 32 Bit.
What is the best configuration?
Should I build separate configurations for x86 and x64, Debug and Release?
Or should I just build just one configuration for AnyCPU?
Or should I just build just one configuration for x86? In this case the application will run anyway on a 64bit client OS? This is perhaps the most appealing solution.The reasons are given be