Lifesaver. FACT.

Only other thing to mention is that as well as the moving the dlls from bin\Debug to DNN\bin you have to move the ascx files from the compilation directory to teh appropriate place in DotNetNuke (should be obvious if the module you're modifying is already installed in the website.

Thanks.

Stu

At this point, I'm kind of stuck. Modifying the dlls works nicely, but changing the ascx files does not.

I don't know much about the way .NET works but from what I've been able to work out, *.ascx deals with web controls and things, while *ascx.cs is the back-end and *.resx is the resource file. I can change some text in the site with the resource file but changing the ascx directly doesn't work.

This may be a learning .Net problem for myself to worry about but at the moment, any changes to CategoryAdmin.ascx, for example, do not appear on the live website. It doesn't help that I can't use the "Design" interface in VS2005 because the ascx files for Store development are in a completely different place from the core files (and therefore can't get to some of the standard buttons and labels and things). Do you have to declare elements added to the .ascx in the .cs file (i've tried)?

I'm going to ask the .NET guy about it later but in the mean time, I'll see if there's any way to move the development project so that it is kept in and compiles to the installed website (would a lot of time copying files in 3 different directories each time I want to try it).

Ultimately, I'm trying to add some features to the standard store cart and have be able to modify them on the web page.

Havea part-solved this.

Rather than removing the DNN website  from the store solution, include it (I had to rename it's location and refresh but that's just my setup - it expects http://localhost/DotNetNuke). This means when you switch to design view, most of the DNN web controls can be found (some can't, they seem to reference ~/controls so I'm guessing they're using absolute references and not pointing to a dll or something). This means you can either: change the ascx in the Store.Webcontrols project more easily (using the design view and then copying them to the website folder) or change them in the Website project within the Store solution.

The only issue with this is adding methods to the code behind: If you want to add functionality you would change the ascx files in the Store.Webcontrols, then modify the corresponding .cs and then copy things over to the website. The problem with this is it seems stupid (would be nice to have ascx files copied out to the website during a build) and you don't have access to all the DNN webcontrols in the design view. I don't know how important the particular controls are (~/controls/SectionHeadControl.ascx).

Stu