Dream AIO
Simple file downloader and binder.
Features
- Multi-file binder
- Multi-file downloader
- Encrypt binded files
- Compress binded files
- Custom Assembly
- Custom Icon
Disclaimer
This source code was written for educational purposes. Do not expect the outputs to be not detectable by antivirus solutions. This source is here to help you get an idea.
Screenshot
Original Thread :
https://hackforums.net/showthread.php?tid=5667979
GitHub
ENJOY
(Jul 28, 2017 01:03 AM)Paskowsky Wrote: Dream AIO
Simple file downloader and binder.
Features
- Multi-file binder
- Multi-file downloader
- Encrypt binded files
- Compress binded files
- Custom Assembly
- Custom Icon
Disclaimer
This source code was written for educational purposes. Do not expect the outputs to be not detectable by antivirus solutions. This source is here to help you get an idea.
Screenshot
![[Image: E1nnWmW.png]](https://i.imgur.com/E1nnWmW.png)
Original Thread :
https://hackforums.net/showthread.php?tid=5667979
GitHub
ENJOY
You are valuable to this community. Thank you.
(Jul 28, 2017 05:57 AM)Goldmouth Wrote: You are valuable to this community. Thank you.
Thank you for the support 🤝
Will release some interesting stuffs in the future 🤝
(Jul 29, 2017 09:10 AM)Kewin Wrote: Awesome release! 🤝
Thanks man!
If anyone have some ideas of what i could code, let me know.
Regards,
Paskowsky
DO NOT DEAL WITH THIS MEMBER
(Jul 31, 2017 08:55 AM)Paskowsky Wrote: Thanks man!
If anyone have some ideas of what i could code, let me know.
Regards,
Paskowsky
Code me a girlfriend
(Jul 31, 2017 09:14 AM)Ninja Wrote: Code me a girlfriend
Nice idea 🤣
I would sell many i think ✌
Code public class Girl{
public string Name {get;}
public int Age {get;}
public int SexyRate {get;}
}
public class Girlfriend : Girl{
public bool Wet{get;}
public bool Horny{get;}
}
public static class GirlfriendFinder{
List<Girl> _girls;
public static Girlfriend FindGirlfriend(string name, int sexyRate){
foreach(Girl g in _girls)
{
if(g.Age < 18)
{throw new UnderageException();}
if(g.SexyRate >= sexyRate)
{
if(g.Name == name)
{
return g;
}
}
}
throw new GirlNotFoundException();
}
}
(Jul 31, 2017 09:21 AM)Paskowsky Wrote: Nice idea 🤣
I would sell many i think ✌
Code public class Girl{
public string Name {get;}
public int Age {get;}
public int SexyRate {get;}
}
public class Girlfriend : Girl{
public bool Wet{get;}
public bool Horny{get;}
}
public static class GirlfriendFinder{
List<Girl> _girls;
public static Girlfriend FindGirlfriend(string name, int sexyRate){
foreach(Girl g in _girls)
{
if(g.Age < 18)
{throw new UnderageException();}
if(g.SexyRate >= sexyRate)
{
if(g.Name == name)
{
return g;
}
}
}
throw new GirlNotFoundException();
}
}
😏
Aug 1, 2017 07:18 AM
(This post was last modified: Aug 1, 2017 07:19 AM by Milan Hermanus.)
Hey Paskowsky, just some constructive criticism:
I would refrain from compiling source code as runtime to create your outputs.
Not only is this slow, this is also easily dumped (i know this is a release, but in the future you might do the same in a paid, private project).
Look up dnlib, it can create small, fast executables with ease.
I am not a fan of your codestyle, but it's subjective and as long as you're consistent it doesn't matter.
(Aug 1, 2017 07:18 AM)Milan Hermanus Wrote: Hey Paskowsky, just some constructive criticism:
I would refrain from compiling source code as runtime to create your outputs.
Not only is this slow, this is also easily dumped (i know this is a release, but in the future you might do the same in a paid, private project).
Look up dnlib, it can create small, fast executables with ease.
I am not a fan of your codestyle, but it's subjective and as long as you're consistent it doesn't matter. (Aug 1, 2017 07:18 AM)Milan Hermanus Wrote: I would refrain from compiling source code as runtime to create your outputs.
Dont worry. In private paid projects i know how to do things properly.
(Aug 1, 2017 07:18 AM)Milan Hermanus Wrote: I am not a fan of your codestyle, but it's subjective and as long as you're consistent it doesn't matter.
What do you mean? Can you explain what in particular you don't like. I'm always looking to improve my coding style. Please let me know.
Thank you for your opinions 🤝
(Aug 1, 2017 08:30 AM)Paskowsky Wrote: Dont worry. In private paid projects i know how to do things properly.
What do you mean? Can you explain what in particular you don't like. I'm always looking to improve my coding style. Please let me know.
Thank you for your opinions 🤝
Well for starters being "free" doesnt mean you should do things non-properly.
Codestyle shit:
"if (blabla) return;"
Using classes instead of structs for simple shit like BinderSetting etc
overall spartan programming
(Aug 1, 2017 08:39 AM)Milan Hermanus Wrote: Well for starters being "free" doesnt mean you should do things non-properly.
I use codedom in my paid project. Just i compile the stub on a server and later add resources with dnlib.
(Aug 1, 2017 08:39 AM)Milan Hermanus Wrote: Codestyle shit:
"if (blabla) return;"
Using classes instead of structs for simple shit like BinderSetting etc
overall spartan programming
About this, nothing to say. You are right i usually don't use structures but just for lazyness.
About spartan programming what do you mean? to my knowledge spartan means essential, is it right? How could i improve this aspect in your opionion? 🤝
(Aug 1, 2017 08:47 AM)Paskowsky Wrote: I use codedom in my paid project. Just i compile the stub on a server and later add resources with dnlib.
Don't do that
(Aug 1, 2017 08:47 AM)Paskowsky Wrote: About spartan programming what do you mean? to my knowledge spartan means essential, is it right? How could i improve this aspect in your opionion? 🤝
The discipline of spartan programming means frugal use of variables:
Minimize number of variables. Inline variables which are used only once. Take advantage of foreach loops.
Minimize visibility of variables and other identifiers. Define variables at the smallest possible scope.
Minimize accessibility of variables. Prefer the greater encapsulation of private variables.
Minimize variability of variables. Strive to make variables final in Java and const in C++. Use annotations or restrictions whenever possible.
Minimize lifetime of variables. Prefer ephemeral variables to longer lived ones. Avoid persistent variables such as files.
Minimize names of variables. Short-lived, tightly scoped variables can use concise, terse names.
Minimize use of array variables. Replace them with collections provided by your standard libraries.
you're using one-letter variables in some places, makes readability bad
(Aug 1, 2017 08:57 AM)Milan Hermanus Wrote: Don't do that
The discipline of spartan programming means frugal use of variables:
Minimize number of variables. Inline variables which are used only once. Take advantage of foreach loops.
Minimize visibility of variables and other identifiers. Define variables at the smallest possible scope.
Minimize accessibility of variables. Prefer the greater encapsulation of private variables.
Minimize variability of variables. Strive to make variables final in Java and const in C++. Use annotations or restrictions whenever possible.
Minimize lifetime of variables. Prefer ephemeral variables to longer lived ones. Avoid persistent variables such as files.
Minimize names of variables. Short-lived, tightly scoped variables can use concise, terse names.
Minimize use of array variables. Replace them with collections provided by your standard libraries.
you're using one-letter variables in some places, makes readability bad
Ok ok, i see this in my coding style. I tend to be minimalist and i always try to write less code possible. I don't know if it's a feature or a bug of my coding style 😧
Regards,
Paskowsky
(Aug 1, 2017 09:32 AM)Paskowsky Wrote: Ok ok, i see this in my coding style. I tend to be minimalist and i always try to write less code possible. I don't know if it's a feature or a bug of my coding style 😧
Regards,
Paskowsky
Write for readability, it'll help you in the long run.
No one likes a co-worker that codes like you
|