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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0IActionable questionsIActionable questions
Previous
 
Next
New Post
6/1/2007 5:47 PM
 

Ok, so I did some testing, and am not sure where to go from here:

1)  I went to "Build -> Rebuild Website" in the Visual Web Developer 2005 Express menu. 

2)  After the site was done rebuilding, I logged in to the DNN instance created on my ASP.Net Development Server and navigated to my custom  module.  No change in how the Action items look.

3)  So, I closed the site and opened the /bin file of my project, then checked the date of the .dll.  "Modified" date is 1/10/07. No change here either.

4)  I ran a search on my hard drive for the .dll and could not find any other versions.

5)  I double-checked the "Development Environment" specified in the DNN "Modules" pdf as you suggested, and I'm pretty sure I've got it set up as specified.

Any suggestions on where to go from here?

 

 

 
New Post
6/1/2007 7:55 PM
 

I believe the DNN document tells you how to setup in Visual Studio.  I will tell what I am doing, but I am not sure that it conforms to best practice as I have not read anything on the subject in some time.  I migrated my project from Visual Studio and had to use both VWD 2005 Express and VB 2005 Express.  Here's what I've got setup:

VWD 2005 Express

Simply a web project over the DotNetNuke folder and is only used for debugging.

VB 2005 Express

A solution with two projects:

1. My Project 

a.  The files are in DotNetNuke/DesktopModules/MyProject

b. This project references Dotnetnuke, Dotnetnuke.webutility, system.web, etc.

c. Builds to it's own \bin

2. _BuildSupport

a. This project references My Project

b. The output for this project is set to go to DotNetNuke\Bin

It is a bit of a pain, but it works.  Maybe someone else out there can make a better recommendation or reference documentation.

 

 
New Post
6/8/2007 3:25 PM
 

smcclure11,

Thank you VERY much for your help, and sorry it took me so long to reply (busy week)!  Your solution to my problem was spot-on.  I took a bit of a shortcut on your proposed setup, but I'm sure either way would work. 

I only created the first project you suggested, then added the appropriate references, then added my .vb files as "Existing Items".  Next, I  edited the "My Project" properties to make sure the "Name", "File" and "Assembly" versions of the old and new .dll would match  Finally, I go to the VB Express Main Menu and select "Build -> Build MyCustomModule".   It dumps the new .dll into the project's \bin directory, so I still have to Copy & Paste it into my DNN\bin, but it does the job and now changes made to my .vb files are working!  Perhaps I'll look into implementing your setup now that the site is functioning correctly again.

Thanks again for the help.

 

 
New Post
6/8/2007 11:04 PM
 

bryan,

You're welcome. 

Steve

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0IActionable questionsIActionable questions


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