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.0Building Outside Core FrameworkBuilding Outside Core Framework
Previous
 
Next
New Post
12/2/2006 4:53 PM
 

Is there a way to build a module outside the core framework?

I am currently buidling modules according to the tutorial: http://forums.asp.net/1114393/ShowPost.aspx

It has you create a folder inside the template.  Well anytime I change anything in my App_Code folder it recompliles EVERYTHING.  Even the predefined modules DNN includes with the core.

This takes forever to compile!  I need to make this faster... so either 1) Stop other modules from complining or how can  I create a new project that has only my module in it.

 
New Post
12/2/2006 9:43 PM
 

I'm not an expert in code, I don't do it, and I might be leading you up the garden path on this one but I did hear when using something like WAP to create your projects, if you make sure not all the DLL's are selected and only 2 - that's all you need to use.- I am not sure which ones  but one was the membership role I thought and the other was the main DNN dll.. then it compiled very fast and was enough to build modules on.

Now again, I could have totally misheard, but it was in reference to a talk that Phil Beadle lead last week at a developer meeting when talking about using VS2005 & WAP for projects.. And he indicated by using this method it was faster and that's how the team of developers were working.

So not sure if it's any help at all, but I just saw this post coming through and it reminded me of what I heard.

Nina Meiers

 


Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
12/3/2006 12:36 AM
 
Check out Michael Washingtons Blog at www.dotnetnuke.com/Community/BlogsDotNetNuke/tabid/825/EntryID/1154/Default.aspx. This gives you a way to create an environment using the install package instead of the source package.  This really speeds up compiling time.  Although the blog is about using VWD, it will also work the same way using VS.Net.
 
New Post
12/3/2006 2:57 PM
 

Check out http://www.webacuity.com/Solutions/CustomModulesforDotNetNuke/AcuitiModuleCreator/tabid/93/Default.aspx and see if this might work for you. I've been using this successfully since the 2x days of creating modules without any problems. We recently converted it for 4x and have some people using it without problems (Robert Collins - could you maybe please chip in if you read this post)...

This is a free module and I would NOT recommend installing it on a production site. This tool has allowed me to create a module (for DNN 4x) which creates it's own projects, etc and builds it's own dll's for the module. This is similar to how we've been doing it in the 3x world of DNN. I know there are people out there who are for using the APP_CODE folder etc (ie. VS 2005 way) and I'm not saying that my way is better. It's just an alternative.

Sanjay

 


AcuitiDP - Oracle Data Provider for DotNetNuke
 
New Post
12/3/2006 4:18 PM
 
overmetal61 wrote

Well anytime I change anything in my App_Code folder it recompiles EVERYTHING.  Even the predefined modules DNN includes with the core.

I use these WSP (WebSite Projects) methods and it takes only 30 seconds to recompile a page in App_Code (if you alter a page that is not in App_Code you only have to "Build Page" not the entire site)

Setting-up Your Development Environment

obviously the reason it's so fast is that you strip DNN down don't install all the core modules (just the HTML module).

You can use the Using Web Application Projects (WAP) and it is faster. The problem is you have to recompile every time. With the WSP methods above you actually never have to recompile (I only recompile when I trying to find a build error).

Using the WSP method you simply save the page (this includes pages in the APP_Code folder) and reload the page in the web browser.

In practice both methods take about the same amount of time. I prefer the WSP method because it works with Visual Web Developer Express.



Michael Washington
http://ADefWebserver.com
www.ADefHelpDesk.com
A Free Open Source DotNetNuke Help Desk Module
 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Building Outside Core FrameworkBuilding Outside Core Framework


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