Hi,

I'm new to DNN and I've inherited a DNNv4 WSP module. I brought down the code in DesktopModules folder from our Staging Environment. I've manage to set it up on our development environment. I open the modules directly from VS2010, apply enhancements, rebuild the project then test the site on local. All is ok. But How do I now deploy it to the staging site now?

I have msbuild community and nant installed. But the project has neither a DNN file nor a build script for nant. And I don't know what to put in a DNN file yet.

And how come that changes gets reflected on my local environment easily just by rebuilding, and when I upload the whole folder to the staging site, it does not get updated?

Initially I though that by just copying the whole folder back on the DesktopModules folder on the staging site, my fix will get reflected on that staging site. I was wrong.

If my understanding is correct, I need to update the module definition with my new build? Would this be correct? I would really appreciate all the help I can get right now.

Thanks.

It has a bin and a dll folder.
My understanding is it's a WebSite project module. But I may be wrong. I don't even know how to distuingish the difference between the two.


Actually, I just added some functions on 1 file and called that function from an existing function. It just hides certain controls depending on the login.

I already tried uploading just the file I modified, but it didn't work. My changes were not reflected. I'm thinking that the old dll file on the bin or dll folder should be replaced with the new one?

If the module code is being compiled into an assembly (dll file), then the module is not a dynamically compiled website project (WSP) but rather a compiled website application project (WAP). In case you had changed project types in modifying the module I would suggest you confirm the following on the original site:

A. Website Project (WSP):

• The original module did not have an assembly (dll file) located in the site's /bin folder?
• The original module has code files (.vb or .cs) located either within the module's sub-folder under /DesktopModules or in a sub-folder of the site's /App_Code folder?
• The original modules .ascx files use the attribute CodeFile = "   ....  " in the @Control directive at the top of the file?

B. Website Application Project (WAP):

• The original module had an assembly (dll file) located in the site's /bin folde?
• The original module does not have any code files (.vb or .cs) located either with the module's sub-folder under /DesktopModules or in a sub-folder of the site's /App_Code folder?
• The original module's .ascx files use the attribute CodeBehind=" . . . " in the @Control directive at the top of the file?

If the module is a WAP (as it sound's like it may be if there is a assembly in the /bin folder), then you will need to upload the newly compiled assembly to the site's /bin folder and any modified .ascx files to the modules /DesktopModules folder. There should be no code behind  files (.vb or .cs) in the module's /DesktopModules folder (or a sub-folder) or in a sub-folder of the site's /App_Code file.

If the module is a WSP, then you need to upload any modified .ascx and code files (.vb or .cs) to their original locations.

---

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