Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreDevelopment in VisStudio5 and ASP.NET 2.0Development in VisStudio5 and ASP.NET 2.0
Previous
 
Next
New Post
8/3/2006 7:19 AM
 
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
 
New Post
8/3/2006 8:52 PM
 
Stuart.Ladd wrote
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


Cool, glad to hear that it worked :)

Yes if you change the any .ascx, then you must copy it to website/desktopmodules/store ..

Another thing, if you follow the steps given, then debugging is also very easy (copy .pdb and .dll instead of just .dll, to website/bin)

JK

You know your website is cool, so why not let your users help you by spreading the word on social networking sites - get the DotNetNuke Social Bookmarks Module with 57 different ways to add social bookmarks to your site ... or download the FREE demo right now
 
New Post
8/4/2006 5:20 AM
 
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.
 
New Post
8/7/2006 12:26 AM
 
Stuart.Ladd wrote
At this point, I'm kind of stuck. Modifying the dlls works nicely, but changing the ascx files does not.

... 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)?



Hi Stuart,

I've been able to modify .ascx files and see the changes.  Not sure how you have tried, but I just open the .ascx from the source dir, make the changes and then copy it to the install dir  (btw if you go to buildsupport/bin, you will find all .dll files in one place ... so you only have to copy from one dir, not several)

Your 2nd point about design mode .. yes it is a problem.  I'm not sure how to handle it yet as I am still using C# express - which doesnt even support .ascx, so no design mode at all!)  Once I get my copy of VS2005 I might be able to say what is the correct thing to do, or perhaps someone else knows in the meantime..

Putting the source files in the install dir may not work, because ASP.NET 2.0 compiles everything it finds in the website dir when you start the site ... so it could find the .dll and the .cs and say that all store classes are defined twice -- but I havent tried so this is just my guess as to what will happen :)

JK

You know your website is cool, so why not let your users help you by spreading the word on social networking sites - get the DotNetNuke Social Bookmarks Module with 57 different ways to add social bookmarks to your site ... or download the FREE demo right now
 
New Post
8/8/2006 8:58 AM
 
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
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStoreDevelopment in VisStudio5 and ASP.NET 2.0Development in VisStudio5 and ASP.NET 2.0


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out