Regarding above, I hate GitHub, but hey im definitely part of the few that do, maybe you'll like it. I recommend that or possibly a cloud service that supports regular backups or file versions (although that stuff is a pain since it's not made for code).
Regarding your Visual Studio stuff (which is coding in general), you can do a bunch of things:
- Static classes or whatever that's called in VB.
You can store static variables and methods in the class which would be a lot like having the code typed directly where you're working, but, it's in an entirely
files, has its own scope etc.
- OOP, create a, for example, "CodeInserter" class thats not static, give it a contstructor that will define what mod it's supposed to do, within its class it will get the code for the mod and apply it. Then it's as simple as: When build is clicked, foreach checkbox that's check create a new instance of CodeInserter that will apply the mod.
- If you use a piece of code 3 or more times, make it a method.
- Don't put all of your code in the Button_Click event, make the event call a function or something that's in a more organized spot.
- Regions. Use
#region <Region Name> and
#endregion to create collapsible regions in VS. very handy.
- Code things with a dynamic influence. Dont make a method that only adds a specific mod for example. Store the mods in a .txt or something and code something that will read that and handle what was read, not hardcoded.
- A lot more that I can't think of

I hope i made sense lol