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.0About compile a sigle moduleAbout compile a sigle module
Previous
 
Next
New Post
8/20/2006 10:36 PM
 

Each time i compile a new module, the VS 2005 go thought all modules. That's take very long time.

Is there some way create a single module and compile just itself.

I know we can creative a project for a module in VS2003. And it's just compile itself.

 

Thanks!

 
New Post
8/21/2006 9:40 AM
 
The following is the answer to this question that I received from Cathal:

"Simple answer is that you shouldn't need to recompile the entire core, unless you're making core changes. If you're creating modules like Shaun's post i.e. in the app_code folder, then the code is automatically background compiled by vb.net - theres no need to force a full compile to test it. If you're running vs.net, then you can just use debug->attach to process, when you want to debug code. If you're using VWD, it doesn't support attach to process, so you'll have to do a full compile.
 
The alternative to this is to create a class library, and add any necessary references (note: VWD doesn't support class libraries....)"


Declan

 
New Post
8/21/2006 12:34 PM
 

Go to the property pages of your website in visual studio

select "build" tab

Put the value on "No build"


Edit your Skin.xml and Container.xml files with:
Yannick's SXE
 
New Post
9/3/2006 7:33 PM
 
Thanks! I found out there is a "build page" for each page.
 
New Post
9/4/2006 3:10 PM
 
When you hit build page it doesn't produce a DLL in the bin.

Also, it seems that when we add the module we're working on to DNN, the module IS built automatically and we get the DLL -- but how do we tell it to do a release DLL and not a debug DLL? I wish this were documented somewhere... I don't know what DNN is doing...

Jason Honingford - Web & Software Developer
www.PortVista.com
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0About compile a sigle moduleAbout compile a sigle module


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