It seems you are possibly not understanding how most modules are actually packaged.

Without seeing the actually source code
- but at a pretty fair guess
 - this module will most like have been built as a seperate stand alone project called a WAP.

When you build a module this way - all of the SOURCE CODE is compiled into a .dll file that gets installed in the websites BIN folder.

As such - you could change all the  source code you like - but the website will never run the uncompiled source code since
it will be finding the compiled .dll code before it ever gets the chance to recompile your modified source code.

Westa

You have what you need to compile and make changes.

What is in the source package is a .sln file for the solution and a .csproj . You will want to open the kbdnn into visual studio using one of these 2 files. These files include what is needed for you to compile the changes.

There is still one more step....after you compile you must take the dlls that are in the bin folder of kbdnn and move them out into the bin folder of dotnetnuke so that your dotnetnuke portal can use the new updated dll's to run off of.

Now you can see your changes.