Wanting to deploy a DNN 4 only module as a pre-compiled PA with custom named rather than "mangle"-named dll (s), I took some time today to review all the threads and blogs relating to the new VS 2005 Web Application Project and Web Deployment Project models and while feeling that I was close to using a combination of these to produce the desired result finally gave up in frustration. I was able to add a WAP for the module to the DotNetNuke solution, create a class library project as needed, resolve all needed DNN references, ect.  What I was not able to accomplish was including the module view, editing, settings .ascx and their associated codefile/codebehind .ascx.vb files in the WAP. In order for them to see various dnn controls (such as label, url control, etc) they had to be placed in a sub-folder of DesktopModules in the DNN 4 website project. This meant that they would either be dynamically compiled with the other modules rather than into a single assembly with the rest of the module code in the WAP.  I then tried adding a Web Deployment Project but soon came away with the impression (hopefully incorrect) that this would change the way the entire DNN solution was compiled/deployed rather than just that of my modules WAP.

Has anyone come up with a way to set up the VS 2005 environment to produce a pre-compiled PA using Web Applicsation Projects and/or Web Deployment Projects?  I'm still trying to come to grips with the changes in compilation models of ASP.NET 2.0 and VS 2005 as it specifically relates to DNN and feel totally lost!

---

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

I think I have figured it out.

In addition to my above post, I changed webdeploy projects setting to build with 1 assembly... and it gave me an error... it said that there was a duplicate type DotNetNuke.Modules.Admin.Authentication.Login. I checked out DesktopModules\AuthenticationServices\DNN\Login.ascx.vb and BINGO! I renamed the class in Login.ascx.vb file to DNNLogin and corrected Inherits value in Login.ascx. Compiled with 1 assembly and the site is working, then I changed my webdeploy settings back to folder based libraries and it is still working.

 So there it is... a solution for my own problem. Not quite sure why right off the bet DNN has same class names... I guess it was not meant to be precompiled.