Feedback is a compiled module (web application project aka WAP). In addition to making changes in Feedback.ascx and Feedback.ascx.vb you will need to recompile the module code and place the resulting DotNetNuke.Modules.Feedback.dll assembly in the site's /bin folder.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

By placing the various component vb files into an App_Code/Feedback folder you are converting the module from a website project (WAP) which has a project file and when compiled will produce a DotNetNuke.Modules.Feedback.dll assembly to a dynamically compiled Website Project (WSP) which has no project file. Making such a conversion in module project types is not recommended as other changes such as removing the .ascx.designer.vb files, changing the @ Control directives to make use of a CodeFile not CodeBehind attributes will also be necessary. I suspect that the errors you are encountering are related to missing imports statements and/or assembly references which would have been included in the project file.

To work with the source code in Visual Studio (as far as I recall, Feedback uses a VS 2008 not VS 2010 solution file), it would be best to install the source package into a working DotNetNuke site of version 5.2.3 or later. Then, prior to opening the DotNetNuke.Modules.Feedback.sln solution file in Visual Studio, open it in a text editor such as NotePad. You will note several references to the IIS site alias "DNN5Test". Change all occurances of "DNN5Test" to that of your IIS site alias.

The Feedback project file makes use of a custom MS Build script and imports the MSBuild.Community.Tasks.targets script and requires MSBuild.Community.Tasks.dll which is included in the packages _buildfiles folder but which does not get automatically installed along with the rest of the source package. You will need to copy the _buildfiles folder of the source package into your DesktopModules/Feedback folder if you want to make use of the custom MS Build script for re-packaging the module. If not, edit the DotNetNuke.Modules.Feedback.vbproj project file to remove the following two elements:

<Import Project="$(MSBuildProjectDirectory)\_buildfiles\MSBuild.Community.Tasks.targets" />
  <Import Project="$(MSBuildProjectDirectory)\_buildfiles\PackageModule.targets" />

After saving the modifications, start up VS and open the DotNetNuke.Modules.Feedback.sln solution file. You should then be able to make your code changes, recompile and if desired re-package the module for install on a different website.

Keep in mind that modifying the Feedback module may make it difficult or impossible to upgrade to later releases of the Feedback module in the future. At the least, it will be necessary to reapply the code changes that you are making after such an upgrade. You may wish to consider whether to increase the module version number and/or change all namespaces from DotNetNuke.Modules.Feedback to whatever you use for your own projects.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner