.NET news » Search results

A circular motion control

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)..

In a previous PBDJ article, we looked at using a third-party control, a ribbon control in particular, in a PowerBuilder WPF target. One of the other “most requested” features people have asked for is the capability to provide docking windows in their PowerBuilder applications. In this article, we’re going to look at how we can do that in a PowerBuilder WPF application using a third-party docking manager. The particular docking manager I’m going to use is the AvalonDock, an open source project on CodePlex (http://avalondock.codeplex.com/). At the time of this writing, the current version is 1.3.3571. However, that one has some dependencies on Visual Studio 2010 and .NET Framework 4.0 libraries. PowerBuilder .NET 12 is based on the Visual Studio 2008 isolated shell, so I’m using an older build (1.1.1509) that doesn’t have these dependencies. First, we’ll add the AvalonDock assembly and a reference to a new WPF application. Create a new WPF window and add the AvalonDock namespace to the Usings property for the new window. I called that new window w_frame, and coded the open event of the application object to open it. I then dropped a DockingManager control onto the window. Next create a menu (I called mine m_menu) and associate that menu with the new window as well.

read more

A circular progress control in WPF.

Google has provided a very reach Google Maps API to use it in our own application. But we need some short of javascript knowledge in order to use it. I don't know about others, but for me it was a little difficult to use javascript along with google apis in ASP.Net pages, specifically if you want to use server side functions to draw google map dynamically. For example, in my case I wanted to pull latitude longitude information from a SQL Server database and then use them to insert pushpins on google map. If you are familiar with Ajax framework, you know the answer. You will have to call asp.net server side function from javascript and use retrieved data to draw a google map. How simple is that? :). Atleast not for me. So I have decided to write a user control which can take care of javascript part and allows me to concentrate on serverside functions.

One complaint about Microsoft Windows SharePoint Services (WSS) 2.0 and Microsoft SharePoint Portal Server 2003 was the difficulty in making changes to the environment after it was deployed. Officially, changing a site definition isn't supported after it has been used to create other sites.

Now, Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server (MOSS) 2007 offer many ways to make changes to sites after they have been provisioned. The introduction of SharePoint Features has opened up an entire world to changing master pages, page layouts, and pages themselves. Further, SharePoint now includes a new technique—delegate controls—that allows for more fine-grained control over parts of the page.

The easiest Inversion of Control framework in town.

This article explains how to make a custom Windows Tab Control in C#.

The article describes a simple folder navigation control.

An example of a Silverlight Drag And Drop / Or Browse File Upload Control using View Model / MVVM