Overall good and nice project , props for that mate.
i got one cristism point, you list "- Doesn't support WPF .exe !" as feature, that makes no sense to me ,of something that does "not" improve or has "not" extra to it , can't really be called a feature.
(Sep 15, 2014 02:13 AM)TheBarret Wrote: Overall good and nice project , props for that mate.
i got one cristism point, you list "- Doesn't support WPF .exe !" as feature, that makes no sense to me ,of something that does "not" improve or has "not" extra to it , can't really be called a feature.
Thx TheBarret. ;)
There are plenty of original topics that I would like to edit but I can't do this with a simple account like mine .. 🙃
[img]http://imabox.fr/a3/1415091130eJRYzb58.png[/img]
(Sep 15, 2014 02:32 AM)sh@rp Wrote: Thx TheBarret. ;)
There are plenty of original topics that I would like to edit but I can't do this with a simple account like mine .. 🙃
[img]http://imabox.fr/a3/1415091130eJRYzb58.png[/img]
ugh the "do this, and you can't do that" on freaking forum... oh well you get my point ^^
(Sep 15, 2014 02:34 AM)TheBarret Wrote: ugh the "do this, and you can't do that" on freaking forum... oh well you get my point ^^
That and the PM space is why I upgraded to l33t, so wurf.
(Sep 15, 2014 03:40 AM)Cornflower Blue இڿڰۣ-ڰۣ— Wrote: That and the PM space is why I upgraded to l33t, so wurf.
Or it's also possible to create as many topics as there are version of my software with an account like mine ... 🤦♂
thanks for share seem really good i will try for sure
Oct 20, 2014 02:42 AM
(This post was last modified: Oct 20, 2014 02:43 AM by sh@rp.)
Updated to 1.1.3 :
- BugFix : the Assembly is loaded into an AppDomain to be unloaded correctly
- Added : loading Assembly Infos via reflection
https://bitbucket.org/3dotdev/dotnet-renamer
sick release bro <3 im gonna try it sometimes thx for sharing
Seems like an interesting project! How does it handle applications that have complex object oriented structures, like overridden or inherited methods ? Back in the days when I wrote an obfuscator, I had quite a bit of trouble with this.
(Oct 20, 2014 12:32 PM)Washi Wrote: Seems like an interesting project! How does it handle applications that have complex object oriented structures, like overridden or inherited methods ? Back in the days when I wrote an obfuscator, I had quite a bit of trouble with this.
It's very complex to set up so the tool doesn't manage it like Reflection and so on ! I mean that it doesn't rename overriden methods ..... and corrupts the binary file if it contains Reflection calls.
Your obfuscator : TUP Obfuscator or DotNetSuppress ??
Good release sir 🤝 to keep this thread alive
I don't get it, a user posted something similar and he got flammed because it's a simple "methods/fields etc" renamer. How is this different? As you said, it also corrupt method calls that use reflection. EX: GetMethod("MyMethod")
Oct 23, 2014 02:10 PM
(This post was last modified: Oct 23, 2014 03:03 PM by sh@rp.)
(Oct 20, 2014 12:22 PM)๖ۣۜDødøsky Wrote: sick release bro <3 im gonna try it sometimes thx for sharing
I keep up the good work. Thank you.. ;)
(Oct 23, 2014 10:34 AM)Cook John Wrote: Good release sir 🤝 to keep this thread alive
Thanks bro. 🙂
(Oct 23, 2014 01:15 PM)0xBB Wrote: I don't get it, a user posted something similar and he got flammed because it's a simple "methods/fields etc" renamer. How is this different? As you said, it also corrupt method calls that use reflection. EX: GetMethod("MyMethod")
It's up to you Ibennz...... 🙂
Quote:a user posted something similar and he got flammed because it's a simple "methods/fields etc" renamer
humm ..where can I find it ???
To be honest some of basic Obfuscator/Renamer are corrupt file without method calls that use Reflection.....
Quote:As you said, it also corrupt method calls that use reflection. EX: GetMethod("MyMethod")
...have you got any recomandation to fix that ..???
Quote:How is this different?
I just do my best to improve my private one (DotNet Patcher v4) :
DotNet Patcher v4 is based on my DotNet Renamer project :
[img]http://www.imabox.fr/a4/1423102132I0WIpV57.png[/img]
Never mind but compared to some project on this board,
I don't think it's ridiculous or considered unnecessary......
Oct 26, 2014 01:40 PM
(This post was last modified: Oct 27, 2014 01:25 AM by sh@rp.)
Updated to 1.1.4 :
- Modified : ICore20Reader Interface
- Added : Cls_Task to improve and simplify the use of the assembly Renamer
How to simply use the tool :
Code Dim _param = New Cls_Parameters(TxbSelectedFile.Text, TxbSelectedFile.Text & "-Renamed.exe")
If _param.isValidFile Then
Dim _paramArgs As New Cls_RenamerState() With { _
.Namespaces = True, _
.Types = True, _
.Methods = True, _
.Properties = True, _
.CustomAttributes = True, _
.Events = True, _
.Fields = True, _
.Parameters = True, _
.Variables = True, _
.RenameMainNamespaceSetting = Cls_RenamerState.RenameMainNamespace.NotOnly, _
.ReplaceNamespacesSetting = Cls_RenamerState.ReplaceNamespaces.Empty, _
.RenamingType = Cls_RandomizerType.RenameEnum.Chinese, _
.RenameRuleSetting = Cls_RenamerState.RenameRule.Personalize}
Dim _Task = New Cls_Task(_param, _paramArgs)
_Task.StartTask()
MessageBox.Show("Renamed :" & vbNewLine & vbNewLine & _
"Namespace(s) : " & _Task.Result.Item("Namespace").ToString & vbNewLine & _
"Type(s) : " & _Task.Result.Item("Type").ToString & vbNewLine & _
"Method(s) : " & _Task.Result.Item("Method").ToString & vbNewLine & _
"Parameter(s) : " & _Task.Result.Item("Parameter").ToString & vbNewLine & _
"Generic Parameter(s) : " & _Task.Result.Item("Generic Parameter").ToString & vbNewLine & _
"Variable(s) : " & _Task.Result.Item("Variable").ToString & vbNewLine & _
"Property(s) : " & _Task.Result.Item("Property").ToString & vbNewLine & _
"Event(s) : " & _Task.Result.Item("Event").ToString & vbNewLine & _
"Field(s) : " & _Task.Result.Item("Field").ToString _
, "Completed", MessageBoxButtons.OK, MessageBoxIcon.Information)
End If
https://bitbucket.org/3dotdev/dotnet-renamer
Just received a crack-me protected with DotNet Renamer : Lot of improvement since I last checked it, now decryption stuff are not static anymore and the whole obfuscated output is very complex, so this is definitively a very good obfuscator !
Assert failure(PID 10704 [0x000029d0], Thread: 10960 [0x2ad0]): pBuffer != NULL
|