Some of the features of NetAdvantage AppStylist include

• Styling similar elements – such that when a graphics artist wants the column headers on a table to appear like the column headers in a list or tree without having to re-specify these setting for each control, they now have that ability from within their own IDE.

• Target components by type – will let a regular appearance to be applied across all controls of a particular control type without the developer having to tediously go in and change all of the properties within an application.

• Target individual instances – lets you change individual instances of a control type to look different than the others all without the developer having to change anything within the application.

• Coexistence with the Infragistics Object Model – In Windows Forms it merges its style settings with those of the control at appearance resolution time. On the Web, it is based on the client machine as part of their browser's routine CSS class resolution.

NetAdvantage AppStylist For Windows Forms will make the graphics artist feel right at home and allow them to become productive much more quickly through tooling that has been designed to work like the graphics media programs that they are already familiar with.

To work with NetAdvantage AppStylist you create/open a style library and base a new style library on an existing template. You can then customize the color palette of the style library. In the past, these color changes would need to have been coordinated between the graphics and applications designers, which really means that when the graphics designer wanted a change, the developer would have to stop work and make these modifications.

Then, to see the results of the changes, the graphics designer would have to wait until a test build has been completed to see the results. Now, in NetAdvantage AppStylist the graphics designer has access to every control and UI interface available so they can see what things will look like.

Once everything is complete, the graphics designer saves the style as an .isl file which the application designer then includes into the Windows Forms code. The developer then can implement it with as little as a single line of code: Infragistics.Win.Appstyling.StyleMangager.Load("MyStyle.isl");