.NET news » Search results

SharePoint users have known how useful Web parts are for a long time, but it wasn't until recently that every .NET developer had access to the ease and grace of Web parts using ASP.NET 2.0. Find out how you can use these handy content containers to create Web sites that put routine content sharing capabilities into the hands of your end users.

The wizard - a standard user interface element in desktop applications - takes the user through a series of discrete steps in order to accomplish some task. A wizard step typically includes instructions, input controls, and an interface for moving between the wizard's steps (typically Next and Previous buttons, with a Finish button at the last step). Furthermore, wizards often include different steps depending on the inputs chosen in previous steps.

Wizards have typically been the domain of desktop applications, but have recently become more prevalent in web applications. In ASP.NET 1.x, developers who wanted to implement a wizard-like user interface would often use multiple Panel Web controls, one for each Wizard step. As they user progressed through the wizard by hitting the Next and Previous buttons, the appropriate Panel could be displayed (have its Visible property set to True), while the others hidden (have their Visible properties set to False).

ASP.NET 2.0 makes creating wizard interfaces a lot less work thanks to its new Wizard control. With the Wizard control, we can define a series of Wizard steps and specify the content - static HTML and Web controls - that belongs in each step along with the function of the step, whether it's the first step, one step in the series of steps, the final step, or a summary step to appear after the wizard has completed. The Wizard control automatically includes the appropriate navigation elements for each step, remembers the values entered into the Web controls in each step, and includes a rich event model from which programmatic logic can be added to perform the desired task upon finishing the wizard (among other tasks)..

Web Parts is the brand new feature in ASP.NET 2.0. This feature supports personalized content and layout of a web page. This new feature or rather controls allows the user Change, Edit, Move the content of the web page as per their choices.

If you use DataAdapters and love their automatic connection-opening and closing capabilities—and ever use transactions, you should first understand what's really going on underneath the covers.

Find out how to use reflection to build real-world extensible applications that accept snap-in modules from third-party developers.

It wasn't all that long ago that biometric authentication seemed like the kind of sci-fi technology that might never be practical outside of top-secret government laboratories. But believe it or not, you can build a fingerprint scanner into any .NET application you like just by following these simple instructions.

Explains how to customize ASP.NET pages on different mobile device types, how to support CSS and how to make user friendly ASP.NET mobile sites.

Uncaught exceptions in your .NET applications can turn an otherwise high-performance application into a snail, especially those that are allowed to be "eaten" by subsequent code. Find out how to use very handy "First Chance" exception feature in the .NET debugger to root out nasty hidden exceptions.

Explains how to make ASP.NET mobile applications by using ASP.NET Mobile Software Development kit (Mobile SDK).

Data is the blood in your system; it sits in its comfortable home of a database, and camps out in the tent of XML, but it deserves to be worked with in a reliable and consistent manner.But why should only data-related operations be reliable? Shouldn't you want to write reliable code for your other operations? The introduction of System.Transactions in .NET 2.0 brings a paradigm shift of how you will write reliable transactional code on the Windows platform. This article dives deep in the depths of how System.Transactions works, and how you can use it to your advantage. You will also see how you can leverage existing System.Transactions integration within ADO.NET, and why you need to really understand what is under the magic carpet.