Can't see this email? View it in your browser.
DotNet Weekly
Liquid Newsletter Template Week:11
Year:2014
Date:2014-Mar-11
Visit Our Site
Your weekly .NET update

Articles we enjoyed

Design Patterns in ASP.NET
Design patterns provide general solutions or flexible way to solve common design problems. This article gives you a simple introduction regarding learning and understanding design patterns. Before starting with design patters in .NET, let’s understand what is meant by design patterns and why it is useful in software programming?

Read more

Enhancements to Debugging Exceptions with IntelliTrace in Visual Studio 2013
The Microsoft Monitoring Agent allows you to collect reliability and performance data for web applications and to review the data using IntelliTrace. With Visual Studio 2013 Update 2, we have added the ability to more easily navigate the diagnostics data related to an exception by using a CodeLens-enhanced Code Map view in combination with the existing IntelliTrace experience.

Read more

TFS for cross team and cross business line work item tracking
I was asked by current customer to come up with a solution, within TFS, to allow an entire division to work together in delivering software for a bank. This divisions made up of over 10 teams than work on many pieces of software. Some have simple requirements while others require harsh security and compliance. This is a standard problem and not unique to this company, however the perception still prevails with both TFS users and administrators, that one must have a single Team Project for each [Project | Team | Product] under way. This perception is not only incorrect but Team Foundation Server was designed to be used differently. The Developer Division (DevDiv) at Microsoft, who built the product, uses a single 20+ terabyte Team Project for their Work Items, Source Code and Builds for over 2k people. Team Foundation Server was designed and built to be used with fewer large Team Projects rather than many small Team Projects.

Read more

Writing Windows Store apps with locale-based adaptive design
The Windows architecture allows developers to create apps and easily make then available to people all around the globe. This process, known as globalization, requires that developers primarily design an app with culturally-neutral behavior. Windows Store apps use the Globalization namespace to address these needs. In this namespace, you’ll find all the core APIs that allow an app to manage, define, detect and convert all international elements (e.g.: formats for date, time, decimals, currencies, regions, languages, etc.) supported by any Windows machine, regardless of the user’s profile.

Read more

Maximize code reuse between Windows Phone 8 and Windows 8
In this section, we will help you make the right choices to maximize code reuse in your apps. As a developer, you want to streamline your development and make maintaining your apps as efficient as possible. By working smarter, you give yourself more time to develop more apps and fill the marketplace with your creations. When building an app for Windows Phone 8 and Windows 8, you should look for opportunities to share code, designs, and assets as much as possible so that you maximize the return on your investment. This section describes the sharing techniques that you can use when building you app for both platforms.

Read more

Follow us: Facebook Facebook Twitter Twitter
/* DotNet Weekly */

Email: info@dotnetweekly.com

Unsubscribe here
Footer