Saturday night my mom came up and watched our 15 month old while the wife and I went out on a date. She is now 23 weeks pregnant and so of course she gets to choose the dining arrangements! She was ruling out almost everything except authenticate Italian food, but she didn’t want to go to a chain restaurant such as Johnny Carino’s or Olive Garden.
Then she remembered this little place by the College Station Medical Center she had seen while going to her doctors. The restaurant is Luigi’s Patio Ristorante, and it is located in a little shopping center at the intersection of highway 6 north and Rock Prairie road. They have directions on their website here. I had never seen it before and I’m always willing to try out new restaurants and food, so we headed that way.
The outside of Luigi’s is nothing special… it’s true beauty is inside. They have done an exquisite job of decorating the interior so that you forget you are in College Station, TX. When you walk in you are instantly transported to a patio in Italy! We noticed a little band stage when we arrived at 6:00 PM, but they did not play until 9:00. I was kind of bummed because I really enjoy live jazz music.
We started the meal off with an order of calamari that was absolutely fabulous. Sometimes calamari can be over cooked which makes it too hard, or the batter used is too thick. However, the calamari was perfectly cooked and breaded and the marinara sauce and tartar sauce that came with it was fresh and delicious. We usually stick with one appetizer, but we decided to order some soup. We figured if the calamari was that good the soup had to be good too. Read More…
I recently had a little problem with my build scripts on my CI server. Since I have Visual Studio 2008 installed on my development machine, NAnt finds the Windows SDK v6.0A installed (flack from the VS2k8 install) and runs along happily building .NET 3.5 libraries (where I use WCF for SOA layers). However, when I recently created a new build server without installing Visual Studio, I kept getting these errors about the sdkInstallRoot not being found for net-3.5. I went ahead and downloaded and installed the latest Windows SDK for Vista (v6.1), but it had no effect on the build scripts. Read More…
The third post in this series on Automating Code Review tools will cover FxCop. FxCop is a coding standard and introspective analysis tool that looks at code using a ruleset and analyzes things such as code design (”should this method be static, internal, etc”) and performance (”change this method to static because it never uses the ‘this’ member”).
I have added FxCop to the automation on several projects I run and found out the hard way just what Microsoft thinks of my code. Actually, there were not a lot of code errors that were show stoppers. Most of the errors came from the Microsoft.Design and Microsoft.Performance rule sets of FxCop. I also had a strong naming error on all my libraries, which I fixed with some quick public/private keypair generation tools (more on this later).
So today’s post is about automating FxCop and fixing some of the likely rule violations you are going to see in your output. You can also follow the FxCop Blog at http://blogs.msdn.com/fxcop/.
Read More…
Yesterday I posted about automating CAT.NET. Today while adding it to another build file, I ran across a great error! The tool did not detect any vulnerabilities in my code and therefore the XPath used in the xmlpeek task failed! This caused the build to fail with a false positive. I’ve updated my target to include the failonerror=”false” for the xmlpeek task and an if statement around the fail task that checks for the hasError property first. If it doesn’t exist the xmlpeek task did not find anything to put in the property and we do not need to fail the build. Read More…
The other day in Part I of this series I said I was going to write up some more articles about automating code review tools in your build process. Today I spent some time looking over CAT.NET and figuring out how it fits into my build process. CAT.NET is a static code analysis tools that analyzes data flow through a .NET library or executable and tries to identify common security problems such as cross site scripting (XSS) and SQL Injection (SQLi) vulnerabilities. My process is not perfect but it does the job well enough. Remember, you should always augment automated tools with a human review to catch things automation cannot. Read More…
