Yesterday we saw all the plumbing involved to lay a groundwork for RadUpload being used to add files to applicants. Today we actually dive into the code for getting RadUpload working in the MVVM application.

The first step in this is deciding where to add the ability to upload files. Doing this within the main Applicants grid is nice (since we're already using the RowDetails presenter), but that'll clutter up the UI there as I want to switch that into a quick and easy overview of each applicant. So instead we're modifying the AddEditApplicantView to make it tab-based, providing one tab...

One of the enhancements that the HR team has been asking for since I first launched this is the ability to attach some of the files that applicants send to the applicants once they are entered into the system.  This way, when looking through applicants anyone can easily view their resume, cover letter, or project (yes, sometimes there are projects!) as well as add a rating value to the project.  Seeing as we have a RadUpload control for Silverlight, I figured this would be a great opportunity to get that running in the application, especially since we have the new...

As you may recall from my previous blog post, we're revamping this application and bring it to the latest and greatest that is available in Silverlight today.  Coincidentally, Q2 2010 SP1 just came out today (check your accounts!) and I figured the best first place to start would be with something I removed previously- validation.

Since I redid the model for this application, I completely scrapped all of the previous validation because I knew I could now take advantage of using INotifyDataErrorInfo, which gives us a slightly more graceful way to handle asynchronous validation in our application.  I would explain all...

It has been a while since I've had a nice, lengthy, code-a-riffic post on here so I wanted to start this off right.  By the title of this post I've already given up part of the surprise- I'm revisiting the Silverlight Recruiting Application and bringing it up to date.  For those of you that don't remember (or haven't seen this series), the concept behind this application was around a real world internal use here at Telerik.  More specifically, we keep growing and therefore our HR demands have grown, requiring something more robust than a very organized use of Excel and...

Hey everyone, it is the day you've all been waiting for.  So what makes April 8th so special? 

Today on the live webinar I added the last module to the Silverlight Recruiting Application, both in the code-behind and in the MVVM/Prism versions.  Here is a quick look at the end result:

Pretty neat, right? :)

To get some of the pre-requisites out of the way, to play with this you will need...

• Visual Studio 2008
• Silverlight 3
• WCF RIA Services Beta for VS2008 (last version release for 2k8)

Ideally you'll all have downloaded the Q1 2010 release, but if not I included the...

Between the last post and this one I went ahead and carried the ideas for the Jobs module and view into the Applicants module and view- they're both doing more or less the same thing, except with different objects being at their core.  Made for an easy cut-and-paste operation with a few items being switched from one to another.  Now that we have the ability to add postings and applicants, wouldn't it be nice if we could schedule an interview?  Of course it would!

Scheduling Module

I think you get the drift from previous posts that these project structures start looking somewhat...

Now we starting getting into a more code-heavy portion of this series, thankfully though this means the groundwork is all set for the most part and after adding the modules we will have a complete application that can be provided with full source.

The Jobs module will have two concerns- adding and maintaining jobs that can then be broadcast out to the website.  How they are displayed on the site will be handled by our admin system (which will just poll from this common database), so we aren't too concerned with that, but rather with getting the information into the...

After our brief intermission (and the craziness of Q1 2010 release week), we're back on track here and today we get to dive into how we are going to navigate through our applications as well as how to set up our modules.  That way, as I start adding the functionality- adding Jobs and Applicants, Interview Scheduling, and finally a handy Dashboard- you'll see how everything is communicating back and forth.  This is all leading up to an eventual webinar, in which I'll dive into this process and give a honest look at the current story for MVVM vs. Code-Behind applications.  (For...

Taking a step back before I dive into the details and full-on coding fun, I wanted to once again respond to a comment on my last post to clear up some things in regards to how I'm setting up my project and some of the choices I've made.  Aka, thanks Ben. :)

Prism Project Setup

For starters, I'm not the ideal use case for a Prism application.  In most cases where you've got a one-man team, Prism can be overkill as it is more intended for large teams who are geographically dispersed or in applications that have a larger scale than my Recruiting...

Now we're starting to dive into the world of Prism and modular development as well as a very standard, event driven, code-behind way of handling this project- meaning now we finally get to see some code!  To start things off, we'll look at the slightly more in-depth approach of beginning an application using Prism/MVVM and what it entails.  Also, to make one distinction early on, since I'm using the same database and WCF RIA Services to handle my data transfer, I've created the code-behind project within the same solution, so when I am in the Recruit project or any module, I'm...