The library name never has to be typed-in; you just select it in 'Components' and its in - forget about it. If the library name was fifty characters in length, you would still just browse to it and click. Do you mean something else?
If you change the name of all 3 files *.dll, *.cs and *.chm it works.
But as Zenerdiode allready said: What for ?
I wouldn't do it either. I'm shure that this will bring you more trouble than advantages, especially when you want to update the libraries.
You can't rename a library dll and then use that dll in a compiled application because the original filename of the library is compiled into the library dll as the name of the .NET assembly it represents. The compiled application knows which assemblies it needs and locates them by assuming that the filename is the same as the assembly name. If the actual filename and the compiled assembly name don't match then the the compiled application cannot locate the required assembly at runtime.
If the source is merged at compilation then this does not apply as there is now no need to locate the library as an external assembly because the code is compiled into the final application.
You can't. The filename is burnt into the library like I said above. It's part of .NET security that you can't change the filename of a compiled assembly.