DGrund,
Please be patient with these people.
At a quick glance, everyone that answered you has already given you good usable answers, IF YOU TAKE THE TIME TO STUDY WHAT THEY SAID!
Here is a very simple example of how this can work.
(1)
In your text files that you are using (if so), replace each letter and each number with a different letter or number. Your choice. You do not need some (supposedly secure, but not) encryption algorithm designed by someone else that is already broken and crack-able by someone else. Just code a text replacement program (yourself) that replaces each letter and number, (one at a time) as I said. Read the text file into your program (If small enough in length, then use one string to hold it all); Parse the text file for each letter and number in that string one at a time; Change each letter and number one at a time and save to a second string; When done, save that second string to a file, and use THAT file in your resources that you send along with your exe. If you cannot do that then do not read any further and you need to learn to do that now.
Step 2 and 3, if you get so that you can do step 1, then you should have already learned close to how to do this backward and un-encrypt the included file. Of course each of your exe's will have the same encryption pad (and it will be used over and over again), but you can supply multiple versions of your exe's for variations. Also, you do not have to learn how to use anyone else's (supposedly but not secure) encryption algorithms.
Once you get to be able to do this, then you might have a greater understanding of what the other (far smarter than myself) posters have already told you.
I hope that this helps you.
post script:
You said, "I understand that a seasoned hacker can disassemble a .Net program, and get to anything I have written." That is very misleading and potentially damaging to someone later learning the truth. .Net is a JIT system. That means that it is a Just In Time compiled mess. It is designed intentionally to send the raw code along with whatever is sent including the exe. The exe that is sent is NOT intended to be used by the receiving computer. The raw code is to be used. It does NOT require a "seasoned hacker" to "disassemble a .Net program" as it includes ALREADY NOT-assembled code along with any exe that is sent, by DESIGN.
post post script:
I just now read your original posting again it suggests one of your possible problems.
"I am writing a word game, and my word lists are copied from an external text file during development time, and embedded within the program (the .EXE file). How do I hide these word lists from prying eyes who browse the .EXE file?
Thank you!"
"Embedded within the program (the .EXE file)" suggests that you are not sending along to anyone else an external text file. Meaning that it looks like you are saying that the external text file is compiled into the .EXE file, and thus not being sent along as an additional file.
If this is so, then you should not have to encrypt that text file, as it is not being received by the end user.
I say "should not" because I do not know C#, and what version that you are using, and what compiler that you are using, and what operating system that you are using, all of which might break the "should not" part.
Differently I say "should not" because I do not know by your original question/statement if you are using .net ,which as I explained earlier, is a JIT system and the supporting/original code which created a locally-usable-only .EXE is fully open to being read, line by line, command by command, by a receiving computer.
"How do I hide these word lists from prying eyes who browse the .EXE file?" suggest that you are not using a compiler that has the ability and/or that you are not using that compiler's ability to fully compile the exe. If you look at the exe, and if you see your text in it as you wrote it, then your options are: get a better compiler; or study how to use the compiler to obfuscate those texts in the exe; or scramble those text before you include them in your exe (as I described earlier in this answer) and make your exe to unscramble them itself automatically; or dump C# and use clean and secure C++11 as written by Stroustrup without all that .net mess and Visual Studio mess.
I hope that this is helpful.