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 Windows Azure Service Bus Relay enables applications hosted anywhere with an internet connection to securely call back to applications hosted in your own datacenter behind a firewall. The CRM 2011 SDK offers documentation on how to use the Windows Azure Service Bus Relay from CRM Online. Here’s a link to the documentation that describes the scenario:
My old team is having a developer dinner tomorrow night titled Developing SharePoint 2010 Solutions Using External Data and Services. See here for more details at http://bit.ly/kPUq5n.
What you will learn
SharePoint 2010 allows developers to work with both internal and external data using Business Connectivity Services (BCS), Excel Services, Access Services and custom WCF services. During the presentation we will discuss and demonstrate several common usage scenarios.
Bringing SQL Server data to SharePoint using BCS
Sharing Excel Data using PowerPivot for SharePoint
Publishing Access Database applications to SharePoint
Sharing secure data using BCS and the secure store service
Creating Silverlight Using WCF RIA services for SharePoint
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:
This is a topic I have customer conversations about quite often. I just found my latest “watch this, then let’s talk about it” reference. Tony Sneed just published a webinar about the topic. Definitely worth watching if you are interested in this scenario.
If you have a need to consume REST Services from .NET Framework based code, then you should really have look at the WCF Rest Starter Kit. There is a handy class called HttpClient that is, in my opinion, provides the best / cleanest way to consume REST services at the http level. Essentially, it gives you the ability to make http calls as easy as:
There is so much more to HttpClient than the little snippet above, including ways to easily hydrate / deserialize the response of the REST service into a .NET types. You have quite a bit of power / control over the common REST service consumption scenarios. There’s a nice little blog post over at The .NET Endpoint blog which covers HttpClient. The BEST starting point, again my opinion, for learning about HttpClient is these two Ch. 9 screencasts by Aaron Skonnard:
“At this event, experts will provide an overview of Bing Maps as a powerful visualization tool for geographic and location-based information. With highlights of scenarios such as locators, fleet/asset tracking, data visualization portals, and location intelligence, we’ll present a deep dive into the Bing Maps Platform, including details on specific features, AJAX, Web Services, and new Silverlight APIs.
We’ll also review exciting recent enhancements, exploring ways to integrate with GIS systems and leverage SQL 2008 spatial features, as well as other related tools and technologies. When you meet the experts, you’ll learn solution implementation and best practices―and you’ll leave with the tools and resources to tap the power of location using Bing Maps.
Event Summary: 1:00 – 2:15 Introduction to Bing Maps, Solution Overview, and Demos 2:30 – 3:30 Deep Dive on Architecture and APIs 3:45 – 5:00 Best Practices, Data Integration, and Future of Bing Maps”
With the .NET Framework 3.5 (the version native to Visual Studio 2008) coming up on its first anniversary, Microsoft is poised to release the first update to the framework in the form of Service Pack (SP1). This Service Pack is unlike your standard Service Pack, in that it will introduce new features/capabilities to the .NET Framework. Some of these features where originally planned to be in the initial release of the framework and others are features/capabilities added to enhance or further secure the core .NET Framework. The August Developer Dinner is going to focus on some of the new features as well as a few of the new enhancements, to give you an introduction of the improved capabilities of the Microsoft Developer Platform.
What you will learn:
This evenings presentation will be a running stream of demonstration focusing on new features and functionality coming in the new Service Pack for several of the key areas of .NET Development today, including Web Development (ASP.NET), Database Development (ADO.NET), Web Services/SOA (Windows Communication Foundation) and User Experience (Windows Presentation Foundation).
You will see demonstrations that will include:
Making data access easier with the ADO.NET Entity Framework.
Exposing your data access layer using ADO.NET Data Services
Building “Data Entry” Web-based applications faster than ever using ASP.NET Dynamic Data.
Making AJAX Applications faster with script combining and easier with built in support for handling browser history (i.e. back/forward buttons).
How to achieve up to 40% faster startup performance for your WPF applications and further improve the startup experience using a splash screen.
Reducing the time it takes to deploy your WPF applications using the New .NET Framework Client Profile.