You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/BUG_REPORT.yml
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ body:
5
5
id: bitmono_version
6
6
attributes:
7
7
label: "BitMono Version"
8
-
description: Please enter the used version of BitMono with the bug
8
+
description: Please enter the used version of BitMono with the bug. You can find the version by choosing your downloaded version [here](https://github.com/sunnamed434/BitMono/releases), or using the BitMono.CLI.exe --version command
Copy file name to clipboardExpand all lines: CHANGELOG.md
+18-90Lines changed: 18 additions & 90 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
| Versions: |
2
2
| - |
3
+
|[v0.11.0-alpha](#v0110-alpha20)|
3
4
|[v0.10.0-alpha](#v0100-alpha19)|
4
5
|[v0.9.0-alpha](#v090-alpha18)|
5
6
|[v0.8.0-alpha](#v080-alpha17)|
@@ -21,11 +22,27 @@
21
22
|[v0.1.0](#v010)|
22
23
23
24
---
25
+
### v0.11.0-alpha.20:
26
+
2023-02-016
27
+
#### Added:
28
+
* BitMono ASCII Art in CLI
29
+
* Hiding of the pathes (file path, directory path, etc)
30
+
* Documentation.
31
+
32
+
#### Fixed:
33
+
* Error when use mono BitMono.CLI.exe [#93](https://github.com/sunnamed434/BitMono/issues/93)
34
+
35
+
#### Changed:
36
+
* Major changes in whole API of BitMono.
37
+
24
38
### v0.10.0-alpha.19:
25
39
2023-02-013
26
40
#### Added:
27
41
* Command line arguments [#82](https://github.com/sunnamed434/BitMono/issues/82)
28
42
43
+
#### Fixed:
44
+
* DotNetHook protection
45
+
29
46
### v0.9.0-alpha.18:
30
47
2023-02-09
31
48
#### Changed:
@@ -111,93 +128,4 @@
111
128
112
129
#### Fixed:
113
130
* Obfuscation process
114
-
* Manipulations and saving of Module optimized, most of things store in memory then writes in file instead of every time writing in file and loading module
115
-
116
-
### v0.4.2-alpha.11:
117
-
#### Fixed:
118
-
* Assembly resolving information and exceptions handling
119
-
120
-
### v0.4.1-alpha.10:
121
-
#### Changed:
122
-
* DotNetHook Protection workflow
123
-
* StringsEncryption Protection workflow as well as data encrypting
124
-
125
-
#### Fixed:
126
-
* Obfuscation process
127
-
128
-
### v0.4.0-alpha.9:
129
-
#### Added:
130
-
* BitDateTimeStamp Protection
131
-
132
-
#### Fixed:
133
-
* Obfuscation process
134
-
135
-
### v0.3.3-alpha.8:
136
-
#### Changed:
137
-
* BitDotNet protection greatly improved
138
-
139
-
#### Fixed:
140
-
* Obfuscation process
141
-
142
-
### v0.3.2-alpha.7:
143
-
#### Fixed:
144
-
* Specifying file
145
-
146
-
### v0.3.1-alpha.6:
147
-
#### Changed:
148
-
* Guarantees loading libraries directly as bytes
149
-
150
-
### Fixed:
151
-
* Now BitMono.CLI catches errors and outputs it properly [#31](https://github.com/sunnamed434/BitMono/issues/31)
152
-
* Protections now outputs logs properly
153
-
* Protections bugs fixes
154
-
155
-
### v0.3.0-alpha.5:
156
-
### Added:
157
-
* Feature that allows to protect types/methods with the specified namespace in obfuscation.json configuration [#27](https://github.com/sunnamed434/BitMono/issues/27)
158
-
159
-
### Changed:
160
-
* FieldsHiding protection currently is deprecated and shouldn`t be used anymore
161
-
162
-
#### Fixed:
163
-
* AntiDebugBreakpoints Protection
164
-
* BitMethodDotnet Protection
165
-
* FullRenamer Protection
166
-
* CallToCalli Protection
167
-
* NoNamespaces Protection
168
-
* ObjectReturnType Protection
169
-
* StringsEncryption Protection
170
-
171
-
### v0.2.2-alpha.4:
172
-
#### Fixed:
173
-
* CLI + GUI
174
-
* Obfuscation process
175
-
176
-
### v0.2.1-alpha.3:
177
-
#### Changed:
178
-
* A lot of configurations moved from appsettings.json to separte configurations (obfuscation.json)
179
-
* Optimized obfuscation process
180
-
* Now libraries as well known as dependencies should be in directory `libs` instead of base
181
-
182
-
#### Fixed:
183
-
* DotNetHook Protection
184
-
* obfuscation.json configuration
185
-
* Module drag-and-dropping
186
-
* GUI version.
187
-
188
-
#### Removed:
189
-
*`base` directory
190
-
191
-
### v0.1.3-alpha.2:
192
-
#### Added:
193
-
* Now it is possible to obfuscate only specific namespace(s) [#27](https://github.com/sunnamed434/BitMono/issues/27).
194
-
195
-
#### Fixed:
196
-
* DotNetHook Protection
197
-
198
-
### v0.1.2-alpha.1:
199
-
#### Fixed:
200
-
* DotNetHook Protection
201
-
202
-
### v0.1.0:
203
-
* Pre-Release of BitMono.
131
+
* Manipulations and saving of Module optimized, most of things store in memory then writes in file instead of every time writing in file and loading module
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+57-45Lines changed: 57 additions & 45 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,26 +1,33 @@
1
1
# Special Thanks
2
-
For great CONTIRUBITNG.md file that "pasted" from [AsmResolver](https://github.com/Washi1337/AsmResolver/blob/master/CONTRIBUTING.md)
2
+
For great [CONTIRUBITNG.md](https://github.com/Washi1337/AsmResolver/blob/master/CONTRIBUTING.md) file which was "pasted" from [AsmResolver](https://github.com/Washi1337/AsmResolver)
3
3
4
-
# Contirbuting
4
+
BitMono Coding Style and Licensing
5
+
======================================
5
6
6
-
## Important for all Contributors
7
-
When contributing to this repository, please first discuss the change you wish to make via issues or any method with the owners of this repository before making a change.
7
+
## Aims
8
+
9
+
This guide is for developers who wish to contribute to the BitMono codebase. It will detail how to properly style and format code to fit this project.
10
+
11
+
Following this guide and formatting your code as detailed will likely get your pull request merged much faster than if you don't (assuming the written code has no mistakes in itself).
12
+
13
+
If you make any changes to BitMono, you are agreeing to the license conditions as specified in [LICENSE.md](LICENSE.md).
8
14
9
-
If you make any changes to BitMono, you are agreeing to the license conditions as specified in [LICENSE](LICENSE).
10
15
11
16
## General Workflow
17
+
12
18
The BitMono project generally follows the principles of [Git Flow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow), with a few variations. Below a summary:
13
19
14
-
- Prefer to create a branch based on `dev`.
15
-
- Do not branch from `main` unless it is a serious bug and requires a hotfix. `main` is supposed to be always in sync with the nuget feed.
20
+
- Prefer to create a branch based on `dev`.
21
+
- Do not branch from `main` unless it is a serious bug and requires a hotfix. `main` is supposed to be always in sync with the nuget feed.
16
22
- Prefix your branch accordingly, depending on what kind of change you are trying to make.
17
-
- For new features, use `feature/name-of-feature`.
18
-
- For issues and/or bug fixes, use `issue/name-of-issue-or-bug`.
23
+
- For new features, use `feature/name-of-feature`.
24
+
- For issues and/or bug fixes, use `issue/name-of-issue-or-bug`.
19
25
- Push your changes on this branch.
20
-
- Make sure you are following the coding style guidelines as described in this document below.
26
+
- Make sure you are following the coding style guidelines as described in this document below.
21
27
- Open a [Pull Request](https://github.com/sunnamed434/BitMono/pulls), setting the `dev` branch as a base branch to merge into.
22
28
- Wait for your pull request to be reviewed and accepted.
23
-
- Pull requests into `dev` will only be accepted if all unit tests succeed and follow the guidelines as described in this document.
29
+
- Pull requests into `dev` will only be accepted if all unit tests succeed and follow the guidelines as described in this document.
30
+
24
31
25
32
## C# Coding Style
26
33
@@ -41,21 +48,20 @@ For editors that support EditorConfig, there is an `.editorconfig` file for you
41
48
42
49
Below an overview of the naming conventions used within the project.
0 commit comments