soda3x
Creation of Debugger and Linking Existing logging
Contributing to the ArmaReforgerServer Project
I was interested in understanding the application's logs and how they could assist in resolving issues experienced by patrons using the software. We could direct troubleshooting away from the application and towards the environment in which the application is hosted.
Commit: [b5de6d](https://github.com/Henry-Cahill/ArmaReforgerServerTool/commit/b5de6d10512659d2e9fb9f28ffc56b6a331d3045)
Could you clarify the purpose of this work and what will be/has been done? It's not clear to me what the benefits for the app & users is.
To maintain functionality as is, allow for more diagnostics when users interact with the app to determine what their issue is.
How I've gotten to this point in asking for collaboration,
This Adventure started on April 6th: Commit d1a2315
- With a commitment to update the packages,
PackageReference Include="HtmlAgilityPack" Version="1.11.59" / PackageReference Include="Serilog" Version="4.0.1" / TO PackageReference Include="HtmlAgilityPack" Version="1.12.0" / PackageReference Include="Serilog" Version="4.2.0" /
- Then, some modifications to the Mod.cs file were made to remove this. —prefix to the mod attributes.
- Added namespaces to the following file to connect methods and attributes to their intended destinations. Since I moved the managers. Cs files into their folder for better organization of the application.
Next Commit added the Code: Commit 6f450e1
TargetFramework>net6.0-windows</TargetFramework TO TargetFramework>net9.0-windows</TargetFramework
- I also reformatted the line spacing of the ReforgerServerApp.csproj file to make it more inline.
3rd Commit 3b64e9b
- Added a console button: // // btnConsole // btnConsole.Location = new Point(1077, 721); btnConsole.Name = "btnConsole"; btnConsole.Size = new Size(110, 24); btnConsole.TabIndex = 52; btnConsole.Text = "Console"; btnConsole.UseVisualStyleBackColor = true;
4th Commit 96d74d6
- Added the debugger and three files.
- With initialization logging, when the application launches, it checks for the newest version of the software.
5th Commit 9b8b4e0
- I found a bug that needed to be rooted using the following code.
[DesignerSerializationVisibility(DesignerSerializationVisibility.Visible)] [Browsable(true)] [EditorBrowsable(EditorBrowsableState.Always)]
6th Commit ae92d21
Update FileIOManager.cs
- Refactored and added logging to all of the methods within this file.
7th Commit b5de6d1 Refactored the Configuration.cs
- Added more logging and refactored most of the code to make the application more efficient.
- It was a successful implementation of the Logging I'd like to add throughout the application.
From April 11 - 18, commits. Then, I went through some meandering troubleshooting to add more logs and found that when trying to refactor Windows Form files, I broke more things than I fixed.
I have reverted to my 7th Commit and would like to move forward, adding log flags or text readouts to this code.
