探索與發現

          研究java技術

            BlogJava :: 首頁 :: 新隨筆 :: 聯系 :: 聚合  :: 管理 ::
            83 隨筆 :: 0 文章 :: 109 評論 :: 0 Trackbacks
          Enterprise Library 4.1 - October 2008
          Logging QuickStart

          The Logging QuickStart demonstrates the following scenarios:

          The QuickStart uses a top-level handler to catch any exceptions that occur during any of the scenarios. The handler displays a dialog box with the exception message.

          The QuickStart is provided in two versions. The first version uses the factory approach to create Enterprise Library objects and the static methods. For example, it uses the static Write method of the Logger class to write log messages and the static Tracer class to trace operations such as data access and write messages to a file.

          The second version demonstrates integration with the Unity Application Block. It creates and populates a UnityContainer instance with the data from the <unity> section of the configuration file. This loads the Enterprise Library Core and Logging Application Block extensions. This QuickStart also generates the main form instance using the Resolve method of the UnityContainer, which causes Unity to create and inject an instance of the LogWriter and non-static TraceManager classes in the form constructor. The QuickStart then uses the methods of these two instances to perform the tasks required. For example, it uses the Write method of the LogWriter class to write log messages and the StartTrace method of the non-static TraceManager class to trace operations such as data access and write messages to a file.

          For information about integration with the Unity Application Block, and how you can create instances of Enterprise Library objects using Unity, see Creating Objects Using the Unity Application Block.

          The QuickStart ships as source code, which means that you must compile it before running it. You use Visual Studio to build the QuickStart.

          To build the Logging QuickStart

          1. Ensure the Enterprise Library Source Code is installed.
          2. Open the Enterprise Library Source Code folder in Windows Explorer or from the Start menu. To open it from the Start menu, click Start on the taskbar, point to All Programs, point to Microsoft patterns & practices, point to Enterprise Library 4.1October 2008, and then click Enterprise Library 4.1 Source Folder.
          3. To run the factory version of the QuickStart, open the QuickStarts folder, open the Logging folder, and then open the CS folder (for C#) or the VB folder (for Visual Basic .NET).
          4. To run the version of the QuickStart that demonstrates integration with the Unity Application Block, open the QuickStarts folder, open the Logging folder, and then open the CS - UnityIntegration folder (for C#) or the VB - UnityIntegration folder (for Visual Basic .NET).
          5. Double-click the LoggingQuickStart.sln icon.
          6. Visual Studio opens, displaying the solution file. On the Build menu, click Rebuild Solution. By default, this is a debug build.
          7. Press F5 to run the QuickStart.

          The default configuration for the Logging QuickStart has the following attributes:

          • General settings:
            • Tracing is enabled.
            • The default category is General.
          • Filters:
            • The category filter will allow all categories except UI Events.
            • The priority filter will only allow events with a priority value of 2 or higher
          • Categories:
            • Events in category Data Access Events are delivered to the Flat File Destination listener.
            • Events in category Debug are delivered to the Debug Destination listener.
            • Events in category General are delivered to the Event Log Destination listener.
            • Events in category Troubleshooting are delivered to the Event Log Destination listener.
            • Events in category UI Events are delivered to the Flat File Destination listener.
            • Events in category Trace are delivered to the Flat File Destination listener.
          • Special sources:
            • Events that occur due to an error are delivered to the Event Log Destination.
          • Listeners:
            • The Event Log Destination uses the Text Formatter to format the message and writes the result to the Application Event Log.
            • The Flat File Destination uses the Text Formatter to format the message and writes the result to the file named trace.log.
            • The Debug Destination uses the Text Formatter to format the message and writes the result to the Visual Studio Output Window.
          • Formatters:
            • The Text Formatter constructs a string with name value pairs for the LogEntry properties.

          The Logging QuickStart ships with a defined configuration, which is included in the App.config file. This file is located in the same folder as the QuickStart project file. Each time you build the code, Visual Studio copies the App.config file to the output directory for the project (the same directory where the QuickStart executable is created), and renames it to LoggingQuickStart.exe.config.

          To change or view these settings, use the Enterprise Library configuration tools to open the App.config file in the directory that contains the QuickStart project file. The App.config file contains the configuration data.

          You can also change the application configuration when you do not plan to recompile the application by opening the LoggingQuickStart.exe.config file with the Enterprise Library configuration tools. However, these changes will be overwritten during the next successful build.

          posted on 2009-02-11 07:20 蜘蛛 閱讀(1245) 評論(1)  編輯  收藏 所屬分類: 日常瑣事

          主站蜘蛛池模板: 沅陵县| 科技| 揭西县| 德兴市| 陆川县| 铜陵市| 综艺| 龙游县| 台北市| 临江市| 成武县| 江北区| 荆门市| 浦北县| 隆回县| 汉源县| 凤凰县| 峡江县| 通州市| 西和县| 南部县| 获嘉县| 梅河口市| 莎车县| 枝江市| 浦东新区| 皮山县| 仙桃市| 宜兰县| 新乡市| 林周县| 杭锦旗| 大姚县| 乌拉特后旗| 南皮县| 通城县| 丹棱县| 东莞市| 仁化县| 万州区| 渝北区|