BugTracker. NET Software Error Tracking)

Introduction

Previously, the company recommended BugTracker.net (Error Tracking Management) in the project team.★Open Source★They are still using) Recently, I need to track and manage Errors for a website project. Naturally, I think of it again. Download the latest version 2.1.4 () online ).

Because you need to deploy it on a public Web server so that common users can use the BugTracker to report errors, you must normalize it and adjust its default security policy.

Introduction

BugTracker.net is an open-source project written in C # Based on ASP.net. It is easy to use.Error Tracking ManagementSoftware.

Installation

1. Decompress all the downloaded compressed files to a folder (for example, "E: \ BugTracker ").
2. Create a database (such as "BugTracker"), and then open "SQL query analyzer" to download "setup. SQL" in the compressed file.
3. Open "IIS Information Service Manager" and create a virtual directory (for example, "BugTracker") under "default website", and correspond to your physical directory (for example, "E: \ BugTracker "). Add "default. aspx" to the default file list.
4. Open your browser and enter "http: // 127.0.0.1/BugTracker" in the address bar. Use the default system administrator (Admin) account to log on.

Chinese

The source code and page labels of the BugTracker project are mixed together without using Codebehind, just as they have returned to the ASP era. So you should never look for code files everywhere like me. I thought it didn't provide source code. Frankly speaking, the design and code implementation of this project are not good.(It seems that foreigners are not all strong people)It is far from being as beautiful as ASP.net Forums (Chinese version). Of course, it may also be because the complexity of the two projects varies greatly, resulting in different design ideas.

The resource document is not used in this project. Various text/Link resources are hard-coded in the ASPX page files, so we must open the relevant ASPX files one by one, find the displayed English content, change one to Chinese, and save it. Because the code is mixed, this step can be omitted after compilation ("Visible").

This project contains two pages that may cause security risks:

1. Query. aspxThe page is used to directly run SQL statements, which causes serious security risks. In particular, when deploying the project on a public server, you must delete the page file, otherwise, malicious users can execute dangerous SQL commands !!!
2. View_web_config.aspxThe page can view the Web. config content, which is really bad. Because the database connection strings are directly stored in the Web. config file without encryption, if you have not deleted the page, what are the consequences ?!

In this Chinese version, I changed some options in the configuration file to more secure settings. The Web. config configuration file is changed to the UTF-8 encoding method to support Chinese. In addition, the "UploadFolder" and "LogFileFolder" keys in the configuration file must specify absolute physical paths rather than virtual paths. Therefore, if you want to deploy the project to a public server, you may need to write a test page to obtain the physical path corresponding to your current virtual directory (for example, [C #]: Response. write (Server. mapPath (". ");), and then update the physical path to the key value in the configuration file.
After a period of testing and running, it is found that the log file is growing rapidly, the Web. set the Enable logging option (LogEnabled = "0") in the config configuration file to disabled.