When creating a package using the built-in DotNetNuke Package wizard, the second dialog selects the files present in the folder you select. It is my opinion that this needs a little work.

I frequently keep html files in the project that contain the text for the ModuleHelp that eventually gets pasted into the resource file in the App_LocalResources folder of each module.

I set the file as excluded by right-clicking on the file in Visual Studio and selecting the Exclude from Project option. This renames the file with a .exclude extension. See below...

App_LocalResources\EditAllowances.ascx.resx
App_LocalResources\EditAllowances_Help.htm.exclude
App_LocalResources\ExportAllowances.ascx.resx
App_LocalResources\ImportAllowances.ascx.resx
App_LocalResources\ListAllowances.ascx.resx
App_LocalResources\ListAllowances_Help.htm.exclude
App_LocalResources\SettingsAllowances.ascx.resx
App_LocalResources\SettingsAllowances_Help.htm.exclude
EditAllowances.ascx
EditAllowances.ascx.vb
ExportAllowances.ascx
ExportAllowances.ascx.vb
ImportAllowances.ascx
ImportAllowances.ascx.vb
ListAllowances.ascx
ListAllowances.ascx.vb
SettingsAllowances.ascx
SettingsAllowances.ascx.vb

I don't believe that the files with the .exclude extension should EVER appear on this list. I would imagine that most of the developers building sites and controls for DotNetNuke use Visual Studio as their design environment, and it would make sense that the wizard would exclude files in a similar fashion to Visual Studio.

I am constantly cutting these files out of packages as they are rebuilt. It would be nice if they were never included in the first place...

Core Team thoughts?