How to create a DNN 4.0 module with VS 2005?

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading ... Loading ...

I have added a new section to my website - “Projects” - It’s been long awaited for me, simply because I wanted to have a section through which I can “formalize” my techological ideas.

First in a row is a new development approach for DotNetNuke 4.0 and it’s modules when developed in Visual Studio 2005

You can find out more info by visiting the projects page…. here, or by clicking in the main navigation on the “Projects” tab.

hope you enjoy it!


Filed under: Uncategorized
Written on: 31 May 2006 ·

kick it on DotNetKicks.com

7 Responses to “How to create a DNN 4.0 module with VS 2005?”

  1. Anonymous wrote:

    Hello Vladan

    Great work - I am still deciding what model to go for (have not analysed them all in great detail - but I was hoping someone on the core team would make some desicions as to what the best method to use was. Have you had any feedback from them on this method? Ps - you may want to check your login module - when you login it stays on the same page so I kept trying to log in thinking I had entered the wrong details.

     June 14th, 2006 at 8:32 am
  2. Vladan Strigo wrote:

    hi Rodney,

    thanks! :)

    I had feedback from different people that it’s a good idea, I saw that also Bertcord had some similar suggestions, but his idea was more in the direction of implementing the WAP and not speeding up development and such. To me personally this method has shown itself to be best also in the VS2003, so this is actually a natural improvement to the new platform.

    Just for a teaser, I’m improving it day by day… I did now a sepeare MSBuild script which build all projects in a given solution and deploys them to central dnn - it works like a charm and is 100% generic. Also I’ve started working on Visual Studio templates, when they are out they should help people even more.

    that’s it for now…

    btw. the Login is fixed now :) forgot to put Home as a Home page in Site Settings

    Vladan

     June 14th, 2006 at 9:13 am
  3. Anonymous wrote:

    I’d like to help. I don’t have much time to do programming but I have used all the templates that existed for VS2003/DNN and can offer feedback and suggestions through testing and experience.

    Brian
    (brian@friscowebsolutions.com)

     June 16th, 2006 at 8:05 pm
  4. Anonymous wrote:

    Hi Vladan

    I’m setting up my 4.x dev environment now - and ‘m trying to decide between using yours or Bert’s - what are the major differences between the two? I assume the end result is the same - my main requirement is dev productivity, but I also need package modules as source and PA only - with the source version I need to decide on the WAP file structure or the core VS one.

    We can take this onto email if you wish? rod smart-thinker . com

     June 21st, 2006 at 5:14 pm
  5. Anonymous wrote:

    One more thing (from your Project page):
    You can also have more than one module per DNN dev. environment - This one actually great, simply because it allows you to limit your development installations to a minimum (for all smaller modules of my company I implement this approach – I do some 5-10 modules by one dev. environment - the trick is only to put them either on different pages so that they don’t bother one another, or on different portals)

    I don’t understand why you need to put them on different pages or portals? In 2003 I hade 5-6 projects in a solution and all of them on the same page in cases?

     June 21st, 2006 at 6:53 pm
  6. Vladan Strigo wrote:

    Well as I see it the major differences between our solutions is that mine is a complete thing that gives you oportunity to expand the whole thing and develop your modules in a self-contained. Also one major difference is that my solution does not contain DotNetNuke project in it’s solution, which is a major productivity enhancement simply because you can work on your projects allot faster that usual.

    I’m sure there are other difference too, these are the ones of the top of my head,

     June 26th, 2006 at 7:32 am
  7. Vladan Strigo wrote:

    You don’t need to have them on different pages, but if you do - you have a chance of only seeing what you are currently working on, and not other modules as well, this has some major advantages:

    1. You can set up your start url to point directly to that page
    2. If youre other modules contain errors, your current development will not be blinded by them
    3. If you work in a company which develops allot of modules simultaneously, you won’t even see what other developers are cooking, and their errors, their problems or anything… you are only seeing what you are developing

    previously I’ve done this with different portals on one host (one per module), but in some cases (smaller modules) the multiple pages idea works as well.

     June 26th, 2006 at 7:36 am

Leave a Reply