I’ve been interested in learning more about functional C#, and how it differs from the OOP style C# that I’ve been doing for years. Ed Charbeneau gave a talk on this topic at CodeMash back in January, the main lesson being how to score a poker game using C# and functional principals and the samples. In this blog entry I will be reviewing a few of the functional principals I took away from the presentation— there are many more but here’s a short list: Continue reading “Functional Programming with C#”
On Monday I attended a presentation on the Domino’s AnyWare application.
A large portion of the talk from Domino’s was about their working culture. They utilize agile and scrum processes, with stand ups and sprints.
co-authored by Joseph Dotson
We are working on a project where the data access methodology for the application was defined and provided by the client. While this approach accomplishes the tasks of accessing data in SQL Server we found that we were duplicating code making small changes to new files but largely repeating code to access new tables in the database. We decided to look at dynamic code in C# to solve this problem and reduce redundancy in the code base.
I had a client that had an existing ASP.Net webforms application and wanted to move to ASP.Net MVC without rewriting the existing web site. Well, as it turns out, you can! Since ASP.Net MVC is an abstraction on top of ASP.Net you can run both simultaneously. Here are the steps I followed to get it working.Bootstrapping MVCTo get Asp.NET MVC4 working in an Asp.NET webforms website we need to add a few files and settings.
As I sat in my living room reflecting on the past three days instead of my latest blog post topic I came to the realization that the last three days could easily be a relatable topic for almost anyone. In the past three days I have loaded and unloaded a 26 foot moving truck, picked up a new puppy that has not stopped barking since we brought him home, unpacked half of our belongings, flown from Cincinnati, Ohio to San Antonio, Texas with my wife for a “weekend getaway” and flown back to Cincinnati. In all of the chaos that surrounded the weekend I learned a few things about myself along the way. We always like to do takeaways and action items when we have meetings at work so I will present mine from the last few days.
I started including unit testing as part of my development routine four years ago. Like a lot of developers, I struggled at first to know what to test and how to make my code more testable. In the .NET space the common approach is to use a lot of interfaces and dependency injection to help keep your code loosely coupled and easier to test.
While developing SharePoint 2010 solutions I am constantly going through the ULS logs to find out what happened when an error occurs. I usually use a tool like ULSViewer to wade through the logs and find my specific correlation id. Then figure out what happened. I thought to myself, there must be a better way! So I tossed around a couple of ideas about creating a web part that would show the log items that had that the correlation id, but that still seemed too cumbersome. What I really needed was to have it right on the error page.