I have recently been practicing playing the bass again and during one of the practicing session my friend had suggested some features for a digital metronome. We had used a few JavaScript based ones; however none of them had a few helpful features. These features included: Adjustable tempo, support for different beats per measures, a visual counter displaying the current count of the measure, the ability to allow for multiple measures, the ability to have two different volumes for the tick sound that plays for each beat, the ability to mute the tick for specified beats of a measure and allow the metronome to be run from the computer without being connected to the internet.So since we could not find a single metronome that supported these features, I decided to build one using Silverlight, figuring that it would be a pretty simple exercise. It turns out I was right, well for the most part.

Obviously the most important feature of a metronome is to keep time, this turned out to be so easy it was almost ridiculous....

I just posted a tutorial on using WCF RIA Services with DotNetNuke. This tutorial demonstrates creating a simple module that allows each registered user of a DotNetNuke website to create and edit their own Task list.

This tutorial also covers two important issues that are of interest to DotNetNuke module developers; implementing WCF RIA Services in a non WAP website, and securing and segmenting data for website users.



You can try out the live sample and download all source code at this link:

http://dnnsilverlight.adefwebserver.com/Silverlight30/WCFRIAServices/tabid/83/Default.aspx

...

 

This program allows users to add unlimited rows of search criteria to filter a list. This example uses the DotNetNuke Users table (normally you would not want to connect directly to a DotNetNuke core table. It is only used as an example).

Even though there is a lot of Linq code to construct the queries, there is only one trip to the database to execute the query. 

You can download the program here:

http://www.adefwebserver.com/DotNetNukeHELP/Misc/usersearch/

Maybe I am a bit to “old school” but I still prefer to use the ASP.Net Web Site project type as opposed to the ASP.Net Web Application project type. I believe this comes from the time spent developing Classic ASP sites and being used to the more “Windows-Like” development of WAP. I am not saying that I will not eventually switch to the “Dark Side” and honestly I already have embraced the Compiled Module project template for my recent DotNetNuke development. However, for now I still have several existing ASP.Net Web Sites that are in use and will not be changing to the compiled project paradigm anytime soon.

This has never been an issue and I had never even considered it to be a drawback until I started learning RIA Services. It didn’t take long to notice that the RIA Services template only allows for the WAP style projects. So I started to wonder how to go about adding RIA to existing web sites. I put together a quick example of how to structure a solution to enable RIA on a stand ASP.Net Web Site. The projects look this:

 

RegularWebSite: Obviously this is the regular non-compiled site, created using the ASP.Net Web Site template. ExampleRIAServicesApplication: This is a project created using Silverlight Navigation Application template. ExampleRIAServicesLibrary: A Silverlight class library project that was created using the WCF RIA Services Class Library project template. The template also created the next project automatically. ExampleRIAServicesLibrary.Web: A .Net class library project that was created using the WCF RIA Services Class Library project template.  

Once these projects were created I started setting up the Domain Services that will be hosted on the ASP.Net site. To do this I first added the following references to the ExampleRIAServicesLibrary.Web:



I then added a LinqToSql model to the project and created a Domain Service to expose the entities in the model. (To keep this post focused, I will not be discussing how to create the domain services. There are plenty of great resources on how to create these services, write custom queries, enable authentication and so on. This article is meant only to explain how to use RIA Services with a non-compiled ASP.Net site.) Once I had these services built (or at least started), I built the ExampleRIAServiceLibrary.Web project and verified that the code was generated in the ExampleRIAServiceLibrary project. If the code is generated, then the RIA Services link is functioning properly and you can move on to wiring this library projects to the application projects.



Note: If the code is not generated verify that the Silverlight class library is linked to the .Net library via the .Net RIA Services link project property.



 

First I added a reference to the ExampleRIAServiceLibrary project in the main Silverlight application:



Then I added a reference to the ExampleRIAServiceLibrary.Web project in the RegularWebSite project:



The final step to link all of the projects together is to link the ExampleRIAServicesApplication Silverlight application to the web site:



Now that all of the projects are linked properly, I built the solution to verify that all of the files were generated and\or copied to the appropriate locations and no errors where reported. Everything built properly so we are ready to published right? Well, actually not yet. There are a few web.config changes that need to be made to allow the Domain Services to function properly. All of the changes that need to be made should be found in the App.Config file of the ExampleRIAServiceLibrary.Web and can be copied directly into the RegularWebSite web.config. First make sure that the necessary connection strings are copied over so the Domain Services can access the data store. The two RIA Services specific settings are as follows:

Under system.web->httpModules  add the following entry: 

add name="DomainServiceModule" ...

Today we released “Silverlight Bridge - A Silverlight 4 File Manager”



Silverlight Bridge can run in "Out Of Browser" mode and access the local file system and allow dragging and dropping of files from the local file system to the server.

Requires:

SQL 2005 or higher Silverlight 4 (currently in Beta) ASP.NET 4.0 (currently in Beta) VS2010 (currently in Beta) It will NOT run on ASP.NET 3.5 and Visual Studio 2008 Not for production use You can download it here: http://silverlightbridge.net

...

Fluent programming strives to provide for more readable code. Fluent validation provides more readable validation code. This is really important when you are building applications that have a lot of validation logic. There are two Fluent Validation ASP.NET libraries that I found:

TNValidate

Fluent Validation 

Because it was the first one I found, I decided to give Fluent Validation a try.

Creating the Sample  



...

I just found out that the Microsoft Channel 9 program featured our DotNetNuke SketchFlow Viewer.

The link to the video is here:

http://channel9.msdn.com/shows/This+Week+On+Channel+9/This-Week-C9-IE8-most-secure-Unix-turns-40-SQL-DBA-eBook/ (they talk about SketchFlow for about 5 minutes and mention the DotNetNuke SketchFlow Viewer at about 23.18)