I have downloaded and compiled many open source projects and I am really surprised and annoyed that they usually do not run out of the box. There's always some gotcha and the workaround is documented in some dark cave and I have to spend time troubleshooting installation and compilation issues like the author was using his own hard coded paths. If the source package needs to be in compiled in release mode then why aren't the .sln and .csproj files have that set up for that? At least put some readme.txt to alert developers about that. Anything that alerts the developer a DNN installation won't work in debug mode.

I am aware that release and debug are not exactly the same but if some ddrmenu files need to be in some folder for dnn to work properly then just put the files there and don't depend on MSBuild to do  the work. Usually the source is opened in Visual Studio for debugging purposes by a developer and the developer expects it to compile, run and work out of the box. Several developers ran into the issue including one of the know commercial module developers. So never assume the developer knows everything or they're aware what needs to be done. If if this mentioned somewhere on the site, don't assume the developer has a network connection all the time. Could be trying to install in a long plane trip. Put a little text file in the zip and explain it in a few lines. It has been my nitpick for tens of open source projects. The developer of the app just codes, zips the source and puts it online without making sure it can run with their own dependencies.