I have been beating my head against the wall all day trying to figure out why I can not install custom modules into my new 4.4.1 installation. When I point the installer to my zip file, and click 'Save' I get the following error at the very end of the install process:

StartJob   Creating files   Info   Created M:\web\users\V007U42TUF\html\DNN\DesktopModules\JHSMH/Buell/ContactForm\Providers\DataProviders\SqlDataProvider\01.00.00.SqlDataProvider   Failure   ExceptionSystem.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\inetpub\webs\Jewish_DNN\DesktopModules\JHSMH\Buell\ContactForm'. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.Directory.InternalCreateDirectory(String fullPath, String path, DirectorySecurity dirSecurity) at System.IO.Directory.CreateDirectory(String path, DirectorySecurity directorySecurity) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.CreateModuleFile(PaFile File, PaFolder Folder) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.CreateFiles(PaFolder Folder) at DotNetNuke.Modules.Admin.ResourceInstaller.PaDnnInstallerBase.Install(PaFolderCollection folders) at DotNetNuke.Modules.Admin.ResourceInstaller.PaInstaller.Install()

It seems to be bombing because there is a <path> element in my manifest file that is pointing to a directory on my local development site. Obviously, that directory doesn't exist on the server and it appears to be what's causing all my troubles.

(I checked, and in our 4.3.7 site, the mainifests don't have this <path> element in them. So, why is it there by default in 4.4.1?)

I tried to find what is causing the <path> element to be written out, but had no success. I thought it was the ~/Components/ResourceInstaller/*.xsd files, but I removed the <path> element from those files, recreated my module package, and the resulting mainfests still had the <path> elements in them!

I'm at a loss. Can someone point me in the right direction?

Thanks.

-JA