.NET news » Search results

I'm sure by now you've read more than your share of books and articles describing new ASP.NET 2.0 features. Master pages, themes, providers, etc., are all great, but have you read anything regarding custom Web control development and what has changed in 2.0? Well that's what I'm here to tell you. If you've become involved in control development, either through my articles or on your own, I'll describe some very cool enhancements that you can put to work right away in your controls using ASP.NET 2.0..

AspLib component library is solution that includes 25 different controls: grid, navigation and input controls; which let you considerably speed up development of web-application and get high-usability interface.

If you were hoping for some new widgets to make repetitive development tasks simpler in Sharepoint, the new 3.0 version did not disappoint. With the new Visual Studio 2005 Extensions things like creating list and site definitions no longer have to be done from scratch.

At a minimum, a Mobile PC application is expected to efficiently manage the power needs, communication environment, inking and form factor constraints of the platforms it supports. This article shows how to easily incorporate ink awareness, power awareness, power awareness and size awareness into otherwise Mobile PC agnostic Windows Form applications, bringing then much closer to conformity as Mobile PC applications. The Mobile PC agnostic Windows Form application used for this demonstration is the VB.NET version of the Black Jack Card Game Starter Kit sample application with either Visual Basic 2005 Express Edition or Visual Studio 2005 as the development environment. The idea is to combine several distinct classes that manage screen size, ink, power and network connectivity separately into one Windows Form class that is easily inherited by a Mobile PC agnostic application. This article highlights some of the benefits of this approach.

Sometimes an application needs to interact with the user interface (UI) of a second application. The first application might be a test application that drives the UI of the target to run through some automated tests. It might describe the UI out loud, as an aid to users that are blind. It might be a speech application that allows users to give vocal commands. In each of these cases, the application needs a way to inspect and interact with the UI of the system and other running applications.

This article demonstrates a quick and easy-to-use implementation for cross-AppDomain communication in .NET by leveraging Windows native messaging. The XDMessaging library is based on code developed to aid rapid development for a recent Vista project that required a lot of cross-AppDomain communication in a locked-down environment. It proved to be extremely useful in a number of scenarios where .NET Remoting would have been impractical, if not impossible, and actually solved more problems than I could have imagined due to its simplicity. The library is intended to send messages between multiple applications in a same-box scenario. For example, a task-tray application might want to communicate with or monitor a separate desktop application. The library does not implement cross-domain communication across a network, for which case .NET Remoting is sufficient.

How does Visual Studio 2005 Team System and Team Foundation Server facilitate the process of agile development and continuous integration? Here Ben Waldron explains it all.