.NET news » Search results

Recently a client made us question one of our fundamental assumptions about the.NET Framework and Web Services by asking, "Why should we use proxy class created by Visual Studio to connect to a web service?" In this particular project we were calling a web service to retrieve data, which was then sorted, formatted slightly and displayed in a web page. The client hypothesized that it would be more efficient to invoke the web service directly via the HttpWebRequest class, retrieve the XML output, populate an XmlDocument object, then use XSLT to output the result to HTML. Surely that would be faster than using Visual Studio's auto-generated proxy class, right?

Prior to this request, we had never considered rolling our own proxy class; we had always taken advantage of the proxy classes Visual Studio auto-generated for us. Could these auto-generated proxy classes be inefficient? Would retrieving and parsing the web service's XML directly be more efficient? The only way to know for sure was to test my client's hypothesis…

This article look at how to use the SqlBulkCopy class to efficiently execute bulk operations against Microsoft SQL Server.

To build realism into 3D scenes, you need to draw with the appropriate materials and transformations help make the drawing process much simpler.

This article tells you how to draw text and pictures correctly on your Vista form's extended glass area.

Single sign-on using ASP.NET Forms authentication is not a new topic. If you Google it, you’ll find a fair amount of articles talking about it. However, it does not appear to be easy enough to get a clear picture when you try to implement it. The concepts and implementation details are often scattered around, which requires adequate efforts to put pieces together. In this article, I’ll try to summarize my understandings through literature study as well as my own practice, and hope to make it easy for you if you ever need to implement it.

Create the famous game using only labels, panels and pictures

An article describing a C# Filmstrip control designed for Windows forms

This article shows two implementations of the same simple program. First, we examine the Windows Forms version, followed by the WPF version. The purpose of this article is to show WinForms programmers a simple example of creating a WPF application. Along the way, we compare and contrast working with the two platforms.

The controls in Windows Forms (.NET) don't support true transparency. In this article we show how to use transparent labels and images.

A generic class and two ToolStripSplitButtons provide navigational history, like in web browsers.