Last post Apr 12, 2005 11:30 PM by wallew
Apr 10, 2005 06:09 PM|photo_tom|LINK
Apr 10, 2005 10:18 PM|ecktwo|LINK
Apr 12, 2005 06:26 PM|thecrispy1|LINK
This might not be the best way to handle this simply because of reference issues. Consider creating a seperate build project to handle this for you.
Apr 12, 2005 11:30 PM|wallew|LINK
I've obviously missed something, but when creating a custom PA,
How do you configure the project so that the DLL automatically goes to the main BIN directory so that you do not have to manually copy the dll file from the project directory to the main bin directory?
Go to the http://dnnjungle.vmasanas.net/ and download the plug-in for VS.NET. It will create Module Projects, SqlDataProviderProjects and skinobject projects from templates. Go through the tutorial. You may
have to fix a couple of references from the templates (missing dll references), but it will save you some time.
Also, use the project in the DotNetNuke folder called... DotNetNukeCore located in the DotNetNuke\Solutions\DNN.Core folder. Make a copy and start with that base.
You need to have a 'project' reference in the Build Support project to automatically copy and debug your module. If you follow the instructions on the site, it is fairly simple.