Christopher Slee

TFS and Office 2010 Beta connections

2010-03-01T15:13:00.006-05:00

I do a lot of work with TFS and one of the things I have to do is use Excel to deliver Gantt charts to management at the various clients I have.

I use excel to build a chart that reads the Interactions and assembles them (along with some sprint info) into a very workable chart that looks like a standard project management Gantt, but requires none of my time to produce.

The problem came when one client updated my Office install to the 2010 Beta (not that I was complaining at the time). The issue was, when I opened the spreadsheet that talks to the TFS server, I got a rude error saying that "TF84034: Team Foundation was unable to initialize the workbook". That was painful. I rely on this particular workbook to do most of my reporting overhead and wanted to get this resolved quickly.

After finding a few posts that talked about TFS 2010 (which we are not using yet) I found this post from Granth's Blog that wasn't quite the issue I had but it was close enough.

I downloaded the hotfix listed on this Microsoft page (FIX: You can no longer connect to a Team Foundation server from Excel after you insert a column in a worksheet) even though it wasn't my exact problem and it worked.

Moving from MVC Beta to MVC 1.0

2009-04-08T09:47:00.006-04:00

During this sprint, one of our clients upgraded from the MVC Beta to MVC 1.0 and I wanted to share what Joe wikied into the team wiki because it might be useful to the rest of us. :)

To upgrade to 1.0 release, you will need to uninstall ASP.NET MVC BETA. You can do this by going to "Add/Remove Programs" under "Control Panel" and find MVC Beta and remove it. Once you have done that, you can download ASP.NET MVC 1.0 from this link.

Once the install is done, do a get latest from TFS.

You can find the Release Notes from ASP.NET team:

There are some changes in 1.0 release compared to the BETA version we have been using up until 3/31/2009. Begining April 1st, all of our ASP.NET MVC project in TFS will be based on 1.0 release. Here are some of the highlights of the upgrade:

Views no longer need code-behind by default
Visual Studio experience improvements:
- New contextual commands like "Add Controller", "Add View", etc
- Able to create partial view (ascx) as a view using the new contextual command
- Basic scaffolding for strongly type views (list, edit, etc)
- Ability to add custom scaffolding templates
Page title is now setable in the ViewPage instead of just in Master.Page
Strongly typed HTML (AJAX) Helper
Smarter and less verbose binding for POST forms, including with complex objects
CSRF Protection
New file handling methods (for upload/download files)
Updated jQuery lib to 1.3.2

You can read a more detailed overview in ScottGu's blog here.

For our site(s), I had to manually do certain several things:

Remove all the code behinds and update the ascxs and aspxs to bind correctly
Update our jQuery references
Change HTML helper call to DropDownList since the upgrade changed the API parameters
Change all <"button"> to <%=Html.Button ... %> since behaves like if button type is not specified correctly
Change every UpdateModel method call to "TryUpdateModel" to utilize non-exception invalid data handling and modify our controllers to display error message correctly
Add CSRF validation attribute to all POST action methods in all of our controllers
Add CSRF tag within all of our forms to work with CSRF attributes in our controllers
Change Delete action method to POST instead of GET to enhance security

Calculating Business Days in a Scheduling System

2009-03-20T09:27:00.000-04:00

We just had a little coding competition in the office to solve "how best to code a scheduling object calculator" and Johannes did a great job recapping the issues and the alternative paths to a solution and showing which really is the best way to go.

Happy reading!

ASP.NET MVC IIS Configuration Info

2009-02-26T15:39:00.002-05:00

As we go to deploy ASP.NET MVC apps, it is important to have a basic understanding of how to deploy on the different environments we encounter.

Server 2008 (The easiest by far)

http://blogs.dovetailsoftware.com/blogs/kmiller/archive/2008/10/07/deploying-an-asp-net-mvc-web-application-to-iis7.aspx

Server 2003 (likely a very common event)

http://haacked.com/archive/2008/11/26/asp.net-mvc-on-iis-6-walkthrough.aspx

Windows XP (I cant' see doing this unless you want to punish yourself, but to each his own)

http://itscommonsensestupid.blogspot.com/2008/11/deploy-aspnet-mvc-app-on-windows-xp-iis.html

Chris

Pushing Source Code

2008-12-17T15:42:00.003-05:00

Well, I was pushing source code around between my dev machines using dropbox (I know I know, but it worked) then I thought, since I am sharing all this with everyone (both the experience and code) why not put it on codeplex?

So, now you can keep up with the current solution by going to http://www.codeplex.com/twitivia and downloading it. I will shortly be posting the Windows Service solution here and also the database that got made to support both the Service and Website (once it is more complete).

Turns out codeplex is just a big Team Foundation Server installation so I am checking files in and out.

Just a quick note to give everyone a stats update and let you know you can hijack the code whenever you want now.

One further refinement

2008-12-15T14:36:00.003-05:00

I believe we will be adding in one additional message to the queue, it will be a quick "time is almost up" message that will go out a few hours before the contest for the day is over.

Oh geeze, the sales guy in my head just tried to issue a "Change Request Form" to the client in my head after the Project Manager just told him about adding a new message type. Now the client is all ticked off and is threatening to kill the whole project. I stepped in and told them all that changes like this are a normal part of the development process and this particular change won't be much at all since we haven't started coding that part yet. That's what refactoring is for. Refinements..

Everyone seems ok now...

Twitter twitter Yedda yedda

2008-12-13T19:47:00.000-05:00

Twitter exposes some of its functionality via an Application Programming Interface (API). That means we can talk to the twitter at a system to system level rather then having a high maintenance human (me) in the loop. After doing the contest 3 times, I think we can automate pretty much the whole thing and just leave it run.

Twitter provides a RESTful interface (check Wikipedia for more on what that means if you like http://en.wikipedia.org/wiki/REST). While we could spend valuable time writing an interface to twitter in C#, but it seems someone has already done that for us (sweet) and we can build our application on their work. I looked at 3 libraries and have decided to use the Yedda Twitter C# Library (http://devblog.yedda.com/index.php/twitter-c-library/)

So with that decision made, we can look at how we can build the application at a higher level.

I’m thinking a windows service can do all the day to day work, the twitivia.com website can be based on MVC (since I’m using that right now and it will be easier) and then we can add in some cool silverlight stuff to play with that.

How about, I get started then catch you up.

The rules of Twitivia

2008-12-13T11:58:00.000-05:00

Ok, just a quick post to formalize the rules we have been talking about. Ha, formalize rules.. I crack myself up.

Anyway, when we started posting twitivia questions way back 3 days ago, it seemed like a good idea to have the first response win. Then we all watched @joshuainboden hover over his text messages and was quick on the response. I believe that is when we coined the term “tweethover”.

So after a quick discussion with a few people, it was decided that we should award a “First Responder” award but allow the session to run for several hours to allow more people to participate and then choose the winner “randomly” from the list of winners.

Ok, that should be the last of the non-project, project related stuff about the project.

What are we building again?

2008-12-11T15:00:00.002-05:00

So, let’s talk about what we want to accomplish next.

I have to do it??!

I have run the contest for two days, and wow is it a lot of work. Well, not really, but it’s not something that anyone should have to do for very long by hand. Isn’t that really why we made computers?

The way I see it, there are 6 message types that should go out to the twitterverse about the game and let’s explore them.

Warning! Questions ahead!

The game is going to run once a day (at least while I have to do it by hand) and the first correct answer to the question is the winner. That means the speed that the players respond is important. I think we should give them some warning that the question is getting ready to go and what better way then with the sponsor message that will carry the “hey, a twitivia round is queuing up”. So message type one is a sponsor message, something like;

“Today's twitivia sponsor is AWH (www.awh.net) "Make IT work for your business". Prepare for the question!“

So when we want to have more sponsors then AWH we would likely fill the message in with data and it would look like something like

“Today's twitivia sponsor is <sponsorName> (<sponsorUrl>) "<sponsorTagline>". Prepare for the question!”

(I’m using the <> to wrap the section we will put data into in the future.)

Next, the inquisition begins!

Twitiva wants to know, With separate divisions for righties and lefites, what sport requires its players to keep their elbows at the table?

We have to keep the questions (and answers for that matter) under 140 characters… so the wording is important. Why 140 characters? That is a twitter message limit.

A simple substitution like;

Twitiva wants to know, <question>?

would work for this.

Pavlovian response anyone?

I noticed today, when I posted the questions, the people that played that I was in the room with were chomping at the bit to see if they won. I think that the lag in announcing a winner for several hours is a good thing for the games and it allows me to space the posts out over a longer period of time so they are not as annoying to everyone, and they show up spaced out in the global timeline to attract more players. That is one of the goals (so if you’re reading this… sign up!)

And the winner is: @joshuainboden for the correct answer, Arm Wrestling!

Which again is a simple substitution for something like;

And the winner is: @<userName> for the correct answer, <correctAnswer>!

By tracking the username, we can then keep track of leader boards and individual player stats which we will added into the twitivia.com website (when we get there)

Gimme gimme gimme

Since everyone I know likes instant gratification, once the winner is announced, we should provide the daily stats so people can see how well they did and how many other players are playing. We all want to feel part of something big (and of course, since you’re reading this, not only are you a part, you on the inside, like in the inner circle of trust). Don’t violate the circle of trust…

Daily stats from twitivia: 8 total answers, 7 correct answers, first answer 1 minute from question post.

Would be something like;

Daily stats from twitivia: <totalAnswers> total answers, <totalCorrectAnswers> correct answers, first answer <firstAnswerDelay> from question post.

I figure at some point we can also do prizes (once we have real sponsorship), until then… “Yea! You won! My, look at the big brain on that player” is all we are getting.

But Chris, that is only 4, what about the other two?? The other two!!

The other two will be simple “reminder” type message and a “call to action” type message that will broadcast out until we have enough players playing and the game is rolling on its own. Something along the lines of;

Tune in tomorrow for the next question and follow the twitiva project at www.chrisslee.com
To win at twitivia, you have to follow twitivia!

Wow

That was a lot of dense narrative. If you read this much, cool. I figured we had to get this part done so we all understood what the goal was. Next post, we start to look at solving the problem, until then I’ll slave over a hot laptop to get the questions out. So play, for the love of all that is Holy, play!

Twitivia

2008-12-10T20:54:00.002-05:00

Twitter, ASP.NET MVC, Silverlight, XNA, iPhone, what do they all have in common? Twitivia! (If you’re on twitter feel free to follow the project @twitivia on twitter).

Twitivia is a project that you can follow me through, it is a simple idea, ask one trivia question a day on twitter and track the answers.

The goal is to create an application that will do all the real work and then spread the client to as many platforms as possible (web, iPhone, Xbox, desktop (WPF)) and you can follow me through. As I build the application, I am going to post the progress (bad code and all) and hopefully some can learn with me, and others will point me in the right direction when I’m lost.

So, let’s get started shall we?

Step one: Get twitter all set up

Well that was simple, go to twitter.com and click the join button.

I setup the new account to be twitivia (obviously) and then went out and registered the domain (yes, I really did). So when we start writing code that runs on the net, like the leader board (for scores) and all the various service end points, we can all find it.

I found a nice icon, changed the design colors on the twitter site and bang, it was online.

Step two: Let people know

I posted the first question and winning answer (hmm could use that as a trivia question later on.. who was the first winner on twitivia).

Then I went out to my regular twitter account (http://www.twitter.com/kuronoir (feel free to follow me there too)) and posted the “it’s alive” announcement and since my twitter and Facebook accounts are linked, about 150-200 people were notified.

I got some good feedback and have asked people to email me questions and answers we can use to populate the database. If you have some good trivia, email me.

Step three: Let’s work out the application plan

Since the primary input and output channel is twitter, I think the first place to go would be to the twitter API and start fooling around with that.