irob's blog. - All Comments

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Rmartin — Tue, 22 Sep 2009 10:06:12 GMT

In this way is possible to debug in real time the code?

thanks Rmartin

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Travis — Wed, 26 Aug 2009 15:27:38 GMT

Thanks for this post, it has been a great benefit!

I was wondering how you might resolve an issue of having two separate compiled modules reference a GAC assembly for the same DNN site?

In my case, I have two standard modules that I would like to convert to compiled modules that both use a charting library that is installed in the GAC.

How can I avoid having a web.config in both compiled module projects and still resolve the GAC reference?

If I can figure this out, I can abandon non-compiled modules completely...

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Ian Robinson — Tue, 25 Aug 2009 16:14:00 GMT

Hey Dan,

Glad the post helped! Thanks for the kind words.

Take care,

Ian

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Bryan — Fri, 21 Aug 2009 20:13:23 GMT

I too appologize for tacking on to an old blog post, but this is the first place I've seen address how to create a DNN module in a Web Application Project.

My questions is two fold:

1. How do you handle items in the App_Code folder?

2. You must have missed something about references. You'll need to reference the various DotNetNuke libraries in order to compile properly, right?

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Dan F — Thu, 11 Jun 2009 10:26:24 GMT

I know this is an old blog post, but it stopped me tearing my hair out today, so thanks! I've got a project that is broken up much like DNN (main web site, secondary sites with user controls) that I've recently upgraded to .net 3.5 and studio 2008. Debugging was fine and dandy back in the 2003 days, but since upsizing I was having hells own trouble debugging. In desparation I hit up google for the 456th time and came across your post. A couple of quick clickety clicks later and I'm hitting breakpoints again. Yay!! Thanks Ian!

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Ian Robinson — Fri, 20 Feb 2009 20:42:54 GMT

There are two Visual Studio solutions. The first is the DotNetNuke solution. The second is the module solution. I never open the first one for development purposes. The second solution (and it's project file) all live within the module's directory under the DesktopModules directory (i.e. everything about this module is contained within that folder, the only exception is the assembly that it outputs to the website's bin directory).

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Store Integrator — Sat, 10 Jan 2009 11:46:05 GMT

Hi,

I was wondering how the DNN is setup? As a project file in the solution or as a web application in the solution (without project file) ?

Could you add screenshot of the final look in VS2008 for this?

re: Creating DotNetNuke Modules using a Web Application Project (WAP)

Dave Armstrong — Sat, 13 Dec 2008 17:45:56 GMT

Ian - thanks for the help - it took me several hours to finally find the answer here to the "~" path problem I was having with the setup of a new WAP module. Thanks again, Dave

re: Microsoft just installed my DotNetNuke!!

chanva — Wed, 03 Dec 2008 09:52:32 GMT

Yes, it's really cool. I will try too.