DNN Blog

Aug 16

Posted by: Chris Hammond
8/16/2010 11:52 PM  RssIcon

A few weeks ago (heck it’s been a couple of months now, my how time flies) I put together a couple of blog posts about module development using the WAP project type. They were how to setup your environment, how to customize a visual studio template, and how to use NANT to automate packaging of your projects.

Well, it took me some time but I finally got a VB.Net template together using the same approach as my C# template. I’ve also put together a new C# template (with a minor change to the location of the uninstall.sqldataprovider file). If you are looking to get started with DNN module development be sure to check out the posts!

Be sure to read those three original blog posts, you’ll get some good info on how to:

If you missed the free Basic Module Development webinar I delivered a couple of weeks ago, check out the video from that to get you jump started with some module development.

You can get the two free templates from codeplex.

I’ve been told these templates will work in VS2008 Express, though I haven’t tested them myself. I also believe that these will work in VS2010 if you want to try them there as well.

One question that comes up when I talk about the Templates that I’ve created is why they aren’t in the DotNetNuke Starter kit that you can download from Codeplex. I intend for them to be rolled into that package, but they didn’t make it into the upcoming DNN 5.5 release, I hope to get them into a future release here soon.

I’m also working on a sample project for DNN restful web services for some demonstrations for the St. Louis Hackathon (you can watch and enter the contest even if you aren’t in St. Louis!), it will be hosted on codeplex as well. I hope to have some of that sample code (developed using the C# template of course) on Tuesday.

15 comment(s) so far...


Gravatar

Re: New release, VB.Net DNN module development template

Thank You Chris!! I'm eagerly awaiting the web services sample.

By Chuck Rizzio on   8/17/2010 7:57 AM
Gravatar

Re: New release, VB.Net DNN module development template

For VS 2010 in the build file change the MSBuild location from

To



But otherwise, cool stuff ;)

By Leigh Pointer on   8/19/2010 6:46 AM
Gravatar

Re: New release, VB.Net DNN module development template

Leigh, send me whatever you're trying to post, it's getting stripped from the comments.

By Chris Hammond on   8/19/2010 6:46 AM
Gravatar

Re: New release, VB.Net DNN module development template

Cool stuff, Chris!

By Matthias Schlomann on   8/30/2010 12:58 PM
Gravatar

Re: New release, VB.Net DNN module development template

Chirs, I thought that might be so, so I blogged about it www.dotnetnuke.com/Community/Blogs/tabid/825/EntryId/2749/Continuous-Integration-Scripts.aspx

By Leigh Pointer on   8/30/2010 12:44 PM
Gravatar

Re: New release, VB.Net DNN module development template

Hi Chris,

I got you C template to work fine.
The VB template says I need to run VS2010 in admin mode.
When I do that It creates the project but It will not build,
lots of not defined errors such as.
Error 44 Type 'IPortable' is not defined.
Did you try it in VS2010?

By dougc on   8/26/2010 9:50 AM
Gravatar

Re: New release, VB.Net DNN module development template

Doug, I haven't tested this with VS2010, but will try to do that today.

By Chris Hammond on   8/26/2010 9:50 AM
Gravatar

Re: New release, VB.Net DNN module development template

Dougc, I think I found a bug in the VB template, working on testing the fix and getting a new package up here shortly

By Chris Hammond on   8/26/2010 10:13 AM
Gravatar

Re: New release, VB.Net DNN module development template

Alright folks, just released a new version 00.00.04 that fixes a couple of issues.

By Chris Hammond on   8/26/2010 10:36 AM
Gravatar

Re: New release, VB.Net DNN module development template

Hi Chris,

I almost have it. The project builds succesfully in VS2010 but fails in Nant with the following:

vbc : Command line error BC2026: warning number '42353' for the option 'nowarn' is either not configurable or not valid
[exec] vbc : Command line error BC2026: warning number '42354' for the option 'nowarn' is either not configurable or not valid
[exec] vbc : Command line error BC2026: warning number '42355' for the option 'nowarn' is either not configurable or not valid
[exec] Done Building Project "C:\inetpub\dnndev\DesktopModules\SicamTest21\SicamTest21.vbproj" (default targets) -- FAILED.
[exec] Done Building Project "C:\inetpub\dnndev\DesktopModules\SicamTest21\SicamTest21.sln" (default targets) -- FAILED.

By dougc on   8/26/2010 12:05 PM
Gravatar

Re: New release, VB.Net DNN module development template

Thanks Doug, I forgot to test the build for VB in 2k10, will make some additional changes.

By Chris Hammond on   8/26/2010 12:04 PM
Gravatar

Re: New release, VB.Net DNN module development template

Hi Chris,

Any luck with the VB template?

By dougc on   8/30/2010 12:43 PM
Gravatar

Re: New release, VB.Net DNN module development template

@dougc, check out Leigh's post (in comments link) about how to fix the VB template. I'll try to include this in a new release this week

By Chris Hammond on   8/30/2010 12:44 PM
Gravatar

Re: New release, VB.Net DNN module development template

Hi Chris,

Any luck with the VB template?

By dougc on   11/22/2010 11:19 PM
Gravatar

globalization issues with template dev environment

hi,
thank you for a great starter with this vb.net template. i would like to make others aware that with the way the dev environment it setup they will find issues with globalization (date formatting) if you are non en-US. although the dnn instance web.config is set to have the cultures as en-GB when i print out the actual culture used by the new module i get a surprise - it's en-US. i used the following server side code in the markup to print it out:-System.Globalization.CultureInfo.CurrentCulture.DisplayName
System.Globalization.CultureInfo.CurrentUICulture.DisplayName
System.Threading.Thread.CurrentThread.CurrentUICulture.DisplayName
System.Threading.Thread.CurrentThread.CurrentCulture.DisplayName

all showed as english US although the dnn site was running with UK culture settings.
I have used a work around which sets the cultureinfo programmatically within the view.ascx page_init routine while the http context is set as debug (it won't be run in compiled released code). If others have found a better solution please do post.

alan

By alan davies on   10/23/2011 10:17 AM
Attend A Webinar
Free Demo Site
Download DotNetNuke Professional Edition Trial
Have Someone Contact Me
Have Someone Contact Me

Like Us on Facebook Join our Network on LinkedIn Follow DNN Corporate on Twitter Follow DNN on Twitter

Advertisers

Sponsors

DotNetNuke Corporation

DotNetNuke Corp. is the steward of the DotNetNuke open source project, the most widely adopted Web Content Management Platform for building web sites and web applications on Microsoft. Organizations use DotNetNuke to quickly develop and deploy interactive and dynamic web sites, intranets, extranets and web applications. The DotNetNuke platform is available in a free Community and subscription-based Professional and Enterprise Editions with an Elite Support option. DotNetNuke Corp. also operates the DotNetNuke Store where users purchase third party apps for the platform.