Over the years, this blog has been about many different things related to software development with Microsoft technologies. Since my current role focuses on PowerApps & Flow, that's what it's primarily about right now.
The post is all about using LINQPad as a tool to write your LINQ queries, then using the feature in LINQPad that gives you the url query translation. Well today, a new MSDN Code Callery project just popped up called OQuery that offers another approach that doesn’t require using an external tool such as LINQPad:
The major caveat (and bummer) with the library is that “LINQ support in the client library has been removed as the core support is not yet available on the phone platform.” I have a tip/trick for LINQ lovers like me that will allow you to still use LINQ query syntax to compose your query (kind/sorta). A tool I find useful to when writing OData queries on Windows Phone 7 is LINQPad. I use the tool to write LINQ queries against my data service, then get the url syntax query translated for me:
Once I get my LINQ query right, I just paste the http string into my app. I’m still surprised about how many people aren’t aware of LINQPad. You must check it out if you use LINQ in your day to day coding (which I am sure most of you do now). You can learn more about using LINQPad against OData services (amongst many other uses) from the product site:
As part of building my WP7 app, I spent a fair amount of time trying to get code coverage working for my unit tests. I tried a number of different approaches including using the Silverlight Unit Test Framework and NUnit + dotCover. I finally landed on an approach that worked for me using the unit testing capabilities in Visual Studio 2010. Since this is a much confused topic with very little info on the web on how to successfully get working for Silverlight/Windows Phone apps, I published a screencast on the subject. I hope you find it useful.
In this screencast, you will learn how to get code coverage for your Silverlight and/or Windows Phone ViewModels through unit testing. You can learn more about code coverage in Visual Studio 2010 from:
UPDATE: A great majority of people never look at an app unless it is free. Even though the manual rate lookup feature of my app is free through trial mode and never times out, I decided to publish an identical version of the app with trial mode behavior called “Free Per Diem Rates” so the app is more discoverable to those who won’t bother looking at an app unless they see FREE.
I’ve been working on an app for Windows Phone 7 in my spare time. The app is for business travelers whose employer’s policy for travel expenses is based on US Government per diem rates. It’s been live in Marketplace for a couple weeks now, but I have been iteratively improving it. Here is the description from Marketplace:
Look up US Government per diem rates. The manual lookup functionality is FREE and works in trial mode without expiration. GSA rates are currently available in the application. DoD and State Department rates are coming soon. Paid users get the following features:
I always hesitate to publish a blog post that is just a link to someone else’s. However, sometimes you just want to make sure people know certain posts exists. This is one from Paul Stubbs (@PaulStubbs on twitter) qualifies: