• Search for:
    16Jan, 2012
    Client Application Development

    Client Application Development

    Client applications are the closest to a traditional style of application in Windows-based programming. These are the types of applications that display windows or forms on the desktop, enabling a user to perform a task. Client applications include applications such as word processors and spreadsheets, as well as custom business applications such as data-entry tools, reporting tools, and so on. Client applications usually employ windows, menus, buttons, and other GUI elements, and they likely access local resources such as the file system and peripherals such as printers.
    Another kind of client application is the traditional ActiveX control (now replaced by the managed Windows Forms control) deployed over the Internet as a Web page. This application is much like other client applications: it is executed natively, has access to local resources, and includes graphical elements.
    In the past, developers created such applications using C/C++ in conjunction with the Microsoft Foundation Classes (MFC) or with a rapid application development (RAD) environment such as Microsoft® Visual Basic®. The .NET Framework incorporates aspects of these existing products into a single, consistent development environment that drastically simplifies the development of client applications.
    The Windows Forms classes contained in the .NET Framework are designed to be used for GUI development. You can easily create command windows, buttons, menus, toolbars, and other screen elements with the flexibility necessary to accommodate shifting business needs.
    For example, the .NET Framework provides simple properties to adjust visual attributes associated with forms. In some cases the underlying operating system does not support changing these attributes directly, and in these cases the .NET Framework automatically recreates the forms. This is one of many ways in which the .NET Framework integrates the developer interface, making coding simpler and more consistent.
    Unlike ActiveX controls, Windows Forms controls have semi-trusted access to a user’s computer. This means that binary or natively executing code can access some of the resources on the user’s system (such as GUI elements and limited file access) without being able to access or compromise other resources. Because of code access security, many applications that once needed to be installed on a user’s system can now be deployed through the Web. Your applications can implement the features of a local application while being deployed like a Web page.

    15Nov, 2011
    How to Use the Out of Office Assistant

    How to Turn On the Out of Office Assistant
    1. On the Tools menu, click Out of Office Assistant.
    2. In the Out of Office Assistant dialog box, click I am currently Out of the Office.
    3. In the AutoReply only once to each sender with the following text box, type the message that you want to send while you are out of the office.
    How to Create a Rule
    1. On the Tools menu, click Out of Office Assistant.
    2. In the Out of Office Assistant dialog box, click Add Rule.
    3. In the When a message arrives that meets the following conditions box, specify the conditions that you want the message to meet.
    4. Click to select the Do not process subsequent rules check box to specify that this rule must be the last one applied.
    5. To specify more conditions, click Advanced, select the options that you want, and then click OK.
    6. In the Perform these actions box, select the options that you want.
    How to Delete a Rule
    1. On the Tools menu, click Out of Office Assistant.
    2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to delete.
    3. Click Delete Rule, and then click Yes.
    How to Edit a Rule
    1. On the Tools menu, click Out of Office Assistant.
    2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to edit, and then click Edit Rule.
    3. Make changes to the conditions and actions for the rule.
    How to Change the Order in Which Rules are Applied
    1. On the Tools menu, click Out of Office Assistant.
    2. In the These rules will be applied to incoming messages while you are out of the office box, click the rule that you want to move up or down in the list.
    3. Click Move Up or Move Down.
    How to Turn a Rule On or Off
    1. On the Tools menu, click Out of Office Assistant.
    2. In the These rules will be applied to incoming messages while you are out of the office box, click to select or click to clear the check box next to the rule that you want to turn on or off.
    How Rules Are Applied
    Rules are applied in the order in which they appear, going from top to bottom, in the list of rules in the Out of Office Assistant box.
    If you select more than one condition in the Edit Rule box, only messages that meet all of the conditions have the rule applied to them. For example, if you specify “Bob Green” as the sender (condition), and “Marketing Meeting” (condition) in the Subject box, the rule only applies to messages that meet both conditions.
    If you set multiple conditions in one rule, messages that meet any of the conditions in the rule are found. For example, if you specify “Bob Green; Jeffrey Weems,” in the From box, the rule applies to messages from either Bob Green or Jeffrey Weems.
    To specify that a rule must be the last one applied, click to select the Do not process subsequent rules check box (in the Add Rule or Edit Rule dialog box).
    When you specify an action for a rule and the action cannot be performed, an error message appears with an “X” next to the rule. To fix the error, click Edit Rule, and then make any necessary changes.