Register | Login
Talk to me
ReMIX '08
Search My Blog
My Twitter                        

Blog Archive
Blog List                                   
My Logos                                  

 

MVPLogo.gif
2004-2007

Lorraine Young's DNN Site

Readify - Microsoft Technical Readiness Specialists

philbeaker.jpg

dnn_ct__130x49_border.gif

 

dnn_pt_help_130x49_border.gif

DotNetNuke Platinum Benefactor

 logo_aspnet.gif

microsoftcertifiedprofessional.gif

vicnet_logo.gif

 

Adsense
View_Blog
Author: Philip Beadle Created: Monday, July 10, 2006 1:23 PM
This blog is more general than my Blog at http://www.dotnetnuke.com/Community/Blogs/tabid/825/Default.aspx. You'll find mostly technical tips and tricks and things i am doing in the MS user group community.

By Philip Beadle on Wednesday, June 25, 2008 7:38 AM

Last year I saw Nikhil Kothari do a session called - Enhancing Ajax Applications with Silverlight.  One of his demos was using the OpenFileDialog and a webservice to transfer chunks of data up to the webserver which I downloaded and worked out how it all fit together.  Now that beta 2 is released I thought I'd update the demo to call the webservice using a Service Reference and the Async event model.

So lets see how it works.

  1. The web page has a single button and a div that works as the progress bar.
  2. The user clicks the button which opens the OpenFileDialog
  3. User selects as many files as they want
  4. The files are sent one at a time by breaki ... Read More »

By Philip Beadle on Sunday, June 01, 2008 11:05 AM

By Philip Beadle on Monday, May 26, 2008 8:44 AM

I have just posted the slides and code from my ReMIX sessions here.

Building Rich Internet Applications using Microsoft Silverlight 2 - Philip Beadle
Learn how to use Microsoft Visual Studio 2008 to create applications, including how to create UI using XAML markup and code, how to build a custom control, how to retrieve data from a Web service, and how to manipulate data with XML and LINQ.

By Philip Beadle on Tuesday, April 29, 2008 3:37 PM

By Philip Beadle on Thursday, April 24, 2008 10:20 AM

Our 300 year old Chinese Marriage bed is nearly finished being restored.  Here's a pic so you can see how its going.

 

By Philip Beadle on Wednesday, April 23, 2008 3:54 PM

Ill be speaking at Code Camp Oz this weekend in Wagga Wagga, check out the details here

http://www.codecampoz.com/

By Philip Beadle on Friday, April 04, 2008 9:43 AM

Im very happy to have been reawarded my MVP status again, makes all teh late nights worthwhile.  I also just hit 1000 posts on DNN.  I have tried to make sure i only post meaningful content and not just ramble or "ditto" peoples posts.

By Philip Beadle on Sunday, March 16, 2008 2:32 PM

Set up my workstation again with all my toys connected together.  Now I can work, play records, mix dance tracks and mix in Ableton Live for all my digital mixing as well.

Check it out.

By Philip Beadle on Friday, March 07, 2008 10:16 AM

By Philip Beadle on Friday, February 15, 2008 7:23 AM

DotNetNuke now has the DNN Forge where anyone can setup a CodePlex project.  The CodePlex team released this blog post http://blogs.msdn.com/codeplex/archive/2008/02/12/codeplex-dotnetnuke-partnership-in-dotnetnuke-forge.aspx about it and you can see all the projects here http://www.dotnetnuke.com/tabid/824/default.aspx

DotNetNuke Blog

New DotNetNuke Book - DotNetNuke Websites, Problem Design Solution

New book out for DNN on Wrox Press, DotNetNuke Websites, Problem Design Solution.  I tech edited this book and thought it was pretty good in its creation of a story of building a site from scratch to a functioning DNN site.

Cheers

 Posted by | Permanent link to this post Sun, 03 Aug 2008 23:52:00 GMT |  Comments (0)

We dont need a LAMP we've got WISDOM :)

I came up with this acronym the other day and thought I'd share it with you all.

What do you think?

 Posted by | Permanent link to this post Sun, 03 Aug 2008 23:49:00 GMT |  Comments (10)

Nearly 600,000 Users on DotNetNuke

I jsut had a look at the number of registered users and its 599000.  Thas really close to 600,000, I remember when we gave a prize for the 100,000th person to register, wow that was a while ago.

 Posted by | Permanent link to this post Thu, 24 Jul 2008 05:36:00 GMT |  Comments (2)

Test Driven Development for DNN Modules Template - How to use it

I have completed the template for VS2008 that I was building so I could build TDD DNN Modules easily.  Download it from Code Plex.  Here's how to use it.

The vbproj for the module has some modifications to allow you to develop outside the DesktopModules folder, see this post for details http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/1873/Default.aspx.  The following steps require you to follow this development practice.
Also you will need to use an object qulifier on your db, which of course you do anyway right, and the Unit Tests use TransactionScope so you will need to start the MS DTC Service.

  1. Create a New Project and select the C# Web Folder and select the TestDrivenDNNModule.Tests template.  Make sure you put the tests into a subfolder of your module usually called Tests.  Name the tests project the same name as the Module project you will add soon.  Youu need to do this so the namespaces and object names in both projects are aligned.
  2. You will now see the Documentation.htm file opened with the rest of the instructions.
  3. Rename this test project to TestDrivenDNNModule4.Tests 
  4. Select Add New Reference and find the DotNetNuke.dll assembly in the File Dialog. 
  5. This test project also needs to access the database so you will need to set up the connection string in the SqlDataProviderFixture.cs file.
  6. Add a New project and select the TestDrivenDNNModule template and name the project TestDrivenDNNModule4 and put it in the parent folder of the tests project you added first..
  7. Edit the Project properties by double-cliking on the My Project folder in Solution Explorer.
  8. Make sure that the Application Tab is selected
  9. Make sure the Root Namespace text-box is empty, and save the Project.
  10. Select Add New Reference and find the DotNetNuke.dll and Microsoft.ApplicationBlocks.Data assemblies in the File Dialog.
  11. Build the Module project and then add a project reference to the TestDrivenDNNModule4 Module from the tests project.
  12. Install your new module as per normal and you will be able to run the Unit Tests.

 

 Posted by | Permanent link to this post Mon, 14 Jul 2008 14:00:00 GMT |  Comments (12)

Complete vbproj file for Help Module to explain the packaging in MSBuild

Had a few requests for more details on how Im auto packaging and developing the Help.  So here it is.

xmlversion="1.0"encoding="utf-8"?>
<ProjectDefaultTargets="Build"xmlns="http://schemas.microsoft.com/developer/msbuild/2003"ToolsVersion="3.5">
     <PropertyGroup>
          <Configuration Condition=" '$(Configuration)' == '' ">DebugConfiguration>
          <Platform Condition=" '$(Platform)' == '' ">AnyCPUPlatform>
          <ProductVersion>9.0.30428ProductVersion>
          <SchemaVersion>2.0SchemaVersion>
          <ProjectGuid>{4669A23C-BC31-45DA-A801-E81899A9582D}ProjectGuid>
          <ProjectTypeGuids>{349c5851-65df-11da-9384-00065b846f21};{F184B08F-C81C-45F6-A57F-5ABD9991F28F}ProjectTypeGuids>
          <OutputType>LibraryOutputType>
          <RootNamespace>
          RootNamespace>
          <AssemblyName>DotNetNuke.Modules.HelpAssemblyName>
          <FileUpgradeFlags>
          FileUpgradeFlags>
          <OldToolsVersion>3.5OldToolsVersion>
          <OptionExplicit>OnOptionExplicit>
          <OptionCompare>BinaryOptionCompare>
          <OptionStrict>OffOptionStrict>
          <OptionInfer>OnOptionInfer>
          <UpgradeBackupLocation>
          UpgradeBackupLocation>
          <SccProjectName>SAKSccProjectName>
          <SccLocalPath>SAKSccLocalPath>
          <SccAuxPath>SAKSccAuxPath>
          <SccProvider>SAKSccProvider>
     PropertyGroup>
     <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Debug|AnyCPU' ">
          <DebugSymbols>trueDebugSymbols>
          <DebugType>fullDebugType>
          <DefineDebug>trueDefineDebug>
          <DefineTrace>trueDefineTrace>
          <OutputPath>Bin\OutputPath>
          <DocumentationFile>DotNetNuke.Modules.Help.xmlDocumentationFile>
          <NoWarn>42016,41999,42017,42018,42019,42032,42036,42020,42021,42022NoWarn>
          <RunCodeAnalysis>falseRunCodeAnalysis>
     PropertyGroup>
     <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Release|AnyCPU' ">
          <DebugType>pdbonlyDebugType>
          <DefineDebug>falseDefineDebug>
          <DefineTrace>trueDefineTrace>
          <Optimize>trueOptimize>
          <OutputPath>..\..\bin\OutputPath>
          <DocumentationFile>DotNetNuke.Modules.Help.xmlDocumentationFile>
          <NoWarn>42016,41999,42017,42018,42019,42032,42036,42020,42021,42022NoWarn>
     PropertyGroup>
     <ItemGroup>
          <Reference Include="DotNetNuke, Version=5.0.0.145, Culture=neutral, processorArchitecture=MSIL">
              <SpecificVersion>FalseSpecificVersion>
               <HintPath>..\..\Releases\DotNetNuke_05.00.00_Install_BETA5\Bin\DotNetNuke.dllHintPath>
          Reference>
          <Reference Include="Microsoft.ApplicationBlocks.Data, Version=2.0.0.0, Culture=neutral">
              <SpecificVersion>FalseSpecificVersion>
               <HintPath>..\..\Releases\DotNetNuke_05.00.00_Install_BETA5\Bin\Microsoft.ApplicationBlocks.Data.dllHintPath>
          Reference>
          <Reference Include="System" />
          <Reference Include="System.Data" />
          <Reference Include="System.Drawing" />
          <Reference Include="System.Web" />
          <Reference Include="System.Xml" />
          <Reference Include="System.Configuration" />
          <Reference Include="System.Web.Services" />
          <Reference Include="System.EnterpriseServices" />
          <Reference Include="System.Web.Mobile" />
     ItemGroup>
     <ItemGroup>
          <Import Include="DotNetNuke" />
          <Import Include="DotNetNuke.Modules" />
          <Import Include="Microsoft.VisualBasic" />
          <Import I nclude="System" />
        Â