background preloader

Software Development

Facebook Twitter


.NET Multi-Tier Application - Windows Azure Tutorial. Developing for Azure is easy using Visual Studio 2013 and the free Azure SDK for .NET. If you do not already have Visual Studio 2013, the SDK will automatically install Visual Studio Express 2013, so you can start developing for Azure entirely for free. This guide assumes you have no prior experience using Windows Azure. On completing this guide, you will have an application that uses multiple Azure resources running in your local environment and demonstrating how a multi-tier application works. You will learn: How to enable your computer for Azure development with a single download and install. How to use Visual Studio to develop for Azure. How to create a multi-tier application in Azure using web and worker roles. In this tutorial you'll build and run the multi-tier application in an Azure Cloud Service.

A screenshot of the completed application is shown below: Note Azure also provides storage queue functionality. Scenario overview: inter-role communication Temporal decoupling. Implementing Reliable Message Receive Loops. Through observations from several customer projects leveraging the brokered messaging API, we noticed that receiving a message is often subject to a canonical repeated implementation of the receive logic without a sound approach to handling potential anomalies. Generally, such logic does not allow for edge cases; for example, expired message locks. This type of approach can be error-prone if it is not implemented in a robust fashion. The purpose of this section is to provide some specific recommendations around the implementation of reliable message receive logic.

First, it is important to note the two distinct modes in which messages can be received from Service Bus. These modes are provided by the brokered messaging API to support message delivery using either “At Most Once” (with ReceiveAndDelete) or “At Least Once” (with PeekLock) semantics. The second mode is PeekLock, which prescribes that a received message is to remain hidden from other consumers until its lock timeout expires. MVC 4. Accessing Resource Files in MVC 3. How to use table storage - Windows Azure feature guide. This guide will show you how to perform common scenarios using the Azure Table Storage Service. The samples are written in C# code and use the Azure Storage Client Library for .NET. The scenarios covered include creating and deleting a table, as well as working with table entities.

For more information on tables, see the Next steps section. Table of Contents What is the Table Service The Azure Table storage service stores large amounts of structured data. Storing TBs of structured data capable of serving web scale applications Storing datasets that don't require complex joins, foreign keys, or stored procedures and can be denormalized for fast access Quickly querying data using a clustered index Accessing data using the OData protocol and LINQ queries with WCF Data Service .NET Libraries You can use the Table service to store and query huge sets of structured, non-relational data, and your tables will scale as demand increases. Concepts The Table service contains the following components: MSDN – Explore Windows, Web, Cloud, and Windows Phone Software Development. Best Practices for Leveraging Windows Azure Service Bus Brokered Messaging API | Windows Azure Customer Advisory Team (CAT)

This article offers practical guidance for developers working with the brokered messaging .NET managed API in the Windows Azure Service Bus . The recommendations supplied in this article come directly from recent customer projects. While building real-world solutions with the Service Bus, we learned about some key best practices and little-known secrets that will help increase reliability and improve the performance of the solutions leveraging the new brokered messaging capabilities in the Service Bus.

This article intends to share these learnings with the developer community. Relayed vs Brokered Messaging The Windows Azure Service Bus provides two comprehensive messaging solutions. The first solution is available through a centralized, highly load-balanced “relay” service running in the cloud that supports a variety of different transport protocols and Web services standards, including SOAP, WS-*, and REST. Brokered Messaging API Overview Best Practices in Brokered Messaging API. Announcing Release of Windows Azure Media Services. I’m excited to announce the general availability (GA) release of Windows Azure Media Services.

This release is now live in production, supported by a new media services dev center, backed by an enterprise SLA, and is ready to be used for all media projects. With today’s release, you now have everything you need to quickly build great, extremely scalable, end-to-end media solutions for streaming on-demand video to consumers on any device. For example, you can easily build a media service for delivering training videos to employees in your company, stream video content for your web-site, or build a premium video-on-demand service like Hulu or Netflix. Last year several broadcasters used Windows Azure Media Services to stream the London 2012 Olympics. Media Platform as a Service With Windows Azure Media Services, you can stream video to HTML5, Flash, Silverlight, Windows 8, iPad, iPhone, Android, Xbox, Windows Phone and other clients using a wide variety of streaming formats: Upload Consume.

Service Bus Queues. Queues provide messaging capabilities that enable a large and heterogeneous class of applications running on premises or in the cloud to exchange messages in a flexible, secure and reliable fashion across network and trust boundaries. Queues are hosted in Windows Azure by a replicated, durable store infrastructure.

The maximum size of a queue is 5GB. The maximum message size is instead 256KB, but the use of sessions allows you to create unlimited-size sequences of related messages. Queues are accessed through the following APIs: The new messaging API available through the new Microsoft.ServiceBus.Messaging assembly. Queue entities provide the following capabilities: Session-based correlation, allowing you to build multiplexed request/reply paths easily. The DefaultMessageTimeToLive property specifies the default message time-to-live value. Date de génération :

Azure Development

Apps for Office Development. JavaScript Development. How an Entirely New, Autistic Way of Thinking Powers Silicon Valley | Wired Opinion. Book excerpt by Temple Grandin and Richard Panek I’ve given a great deal of thought to the topic of different ways of thinking. In fact, my pursuit of this topic has led me to propose a new category of thinker in addition to the traditional visual and verbal: pattern thinkers. Reading an interview with Steve Jobs, I came across this quote: “The thing I love about Pixar is that it’s exactly like the LaserWriter.” What? The most successful animation studio in recent memory is “exactly like” a piece of technology from 1985?

He explained that when he saw the first page come out of Apple’s LaserWriter — the first laser printer ever — he thought, There’s awesome amounts of technology in this box. But he also knew that the public wasn’t going to care about what was inside the box. He was right, obviously. I haven’t been able to look at an iPod or iPad or iPhone without thinking about that interview. The notorious antenna problem on the iPhone 4?

Temple Grandin & Richard Panek Go Back to Top.

Windows Debugging & Troubleshooting

Accessiblity. Learn to code. Assembling Sass. Walkthrough: Creating an MSBuild Project File from Scratch. Programming languages that target the .NET Framework, for example, Visual C# and Visual Basic, use MSBuild project files to describe and control the application build process. When you use Visual Studio to create an MSBuild project file, the appropriate XML is added to the file automatically. However, you may find it helpful to understand how the XML is organized and how you can change it to control a build. This walkthrough shows how to create a basic project file incrementally, by using only a text editor. The walkthrough follows these steps: Create a minimal application source file. This walkthrough shows how to build the project at the command prompt and examine the results.

To complete the walkthrough, you must have the .NET Framework (version 2.0, 3.5, 4.0, or 4.5) installed because it includes MSBuild and the Visual C# compiler, which are required for the walkthrough. This section shows how to create a minimal Visual C# application source file by using a text editor. ASP.NET MVC Tip #47 – Using ResolveUrl in an HTML Helper. Yesterday, I was creating a simple HTML helper for displaying images.

Nothing fancy. The code for the helper is contained in Listing 1. Listing 1 – HelpersImageHelper.cs using System.Web.Mvc; using System.Web.Routing; namespace MvcApplication1.Helpers { public static class ImageHelper { public static string Image(this HtmlHelper helper, string id, string url, string alternateText) { return Image(helper, id, url, alternateText, null); } public static string Image(this HtmlHelper helper, string id, string url, string alternateText, object htmlAttributes) { // Create tag builder var builder = new TagBuilder("img"); // Create valid id builder.GenerateId(id); // Add attributes builder.MergeAttribute("src", url); builder.MergeAttribute("alt", alternateText); builder.MergeAttributes(new RouteValueDictionary(htmlAttributes)); // Render tag return builder.ToString(TagRenderMode.SelfClosing); } } } This helper method uses a TagBuilder to render a standard HTML <img> tag.

Creating Custom HTML Helpers (C# The goal of this tutorial is to demonstrate how you can create custom HTML Helpers that you can use within your MVC views. By taking advantage of HTML Helpers, you can reduce the amount of tedious typing of HTML tags that you must perform to create a standard HTML page. In the first part of this tutorial, I describe some of the existing HTML Helpers included with the ASP.NET MVC framework. Next, I describe two methods of creating custom HTML Helpers: I explain how to create custom HTML Helpers by creating a static method and by creating an extension method. Understanding HTML Helpers An HTML Helper is just a method that returns a string. The ASP.NET MVC framework includes the following set of standard HTML Helpers (this is not a complete list): Html.ActionLink()Html.BeginForm() Html.CheckBox()Html.DropDownList()Html.EndForm()Html.Hidden()Html.ListBox()Html.Password()Html.RadioButton()Html.TextArea()Html.TextBox() For example, consider the form in Listing 1.

Listing 1 – Views\Home\Index.aspx.