I'm new with DNN, and I need to extend some modules. I've installed the source code for DNN, and it works as it should. However when I tried to debug it, I found I was unable to debug modules' code. This seems to be caused by the fact that I'm not compiling them correctly; in fact I have the dlls, but if I try to remove them and compile them again, it fails to find the dlls.

Now, I could be wrong, but I've come to think the problem is that most of the modules are not made to work under VS2005 (infact their solutions are for VS 7.1), and this seems confirmed by the fact that there are no vb under the App_Code subfolder. Is this right? What should I do to quickly convert the modules in VS2005/DDN4 format?

You can check out my tutorials (the link is in the sig) on how to develop modules for DNN4, as well as you can check out my resources page (link in the sig), there you will find another tutorial from a fellow community contributor on how to convert DNN3 modules to DNN4.

If you still have problems after reading these, let us know the behavior you are experiencing and we will try to help you.

 

---

Thanks,
Vladan Strigo
NETMedia

My website: Vladan.Strigo.NET

Vladan.Strigo.NET: Projects
* Advanced VS2005 development approach - BlankModule
* DNN & Microsoft Ajax best practices guidance

Vladan.Strigo.NET: Resources
* Comprehensive list of DNN 4 Module development resources

Ummm that was kinda the point - DNN4 is still built in largely around VS2003 last I checked - and you could count on one hand the commercial modules that provide source code that is prebuilt and ready to EDIT in VS2005.

And that after all is what we are talking about here - we are not discussing if the modules RUN - but instead if they are ready to edit as VS2005 projects.

As more people move to VISTA like platforms and discover that VS2003 and vista dont mix - then we are much more likely to finally see a full move to VS2005 ... or maybe VS2007 / ORCA.

But till then - developing in VS2005 can be a bit of a challenge for new users - especailly given the problems and confusing so many of them seem to have about how to even get started given the various and not nescessarily compatible development methodologies currently being offer from WAP to DYNAMIC to your own DNN stub soliuton.

Which is where this thread started - with a user asking why there wasnt any CODE in the \APP_CODE\ folder for the module he wanted to experiement with ...

When of course there propably wont be any APP_CODE source - if its a WAP module.  But the varying methodologies only seem to get people more confused than ever.

Westa