Bøger udgivet af Microsoft Patterns & Practices

How can you create an application that has truly global reach, and can scale rapidly to meet sudden massive spikes in demand? Historically, companies had to invest in an infrastructure capable of supporting such an application themselves, and plan for peak demand-which often means that much of the capacity sits idle for much of the time. Typically, only large companies would have the available resources to risk such an enterprise. The cloud has changed the rules of the game. By making infrastructure available on a "pay as you go" basis, creating a massively scalable, global application is within the reach of both large and small companies. Yes, by moving applications to the cloud you're giving up some control and autonomy, but you're also going to benefit from reduced costs, increased flexibility, and scalable computation and storage. This guide is the third release of the second volume in a series about Windows Azure. It demonstrates how you can create from scratch a multi-tenant, Software as a Service (SaaS) application to run in the cloud by using the Windows Azure tools and the increasing range of capabilities of Windows Azure. The guide focuses on both good practice design and the practicalities of implementation for multi-tenant applications, but also contains a wealth of information on factors such as security, scalability, availability, and elasticity that are relevant to all types of cloud hosted applications. The guide is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates applications and services that run on or interact with the cloud. Although applications do not need to be based on the Windows operating system to work in Windows Azure, or be written using a .NET language, this guide is written for people who work with Windows based systems. You should be familiar with the .NET Framework, Visual Studio, ASP.NET MVC, and Visual C#.

How do you build and deploy applications to be scalable and have high availability? Along with developing the applications, you must also have an infrastructure that can support them. You may need to scale up or add servers, have redundant hardware, and add logic to the application to handle distributed computing and failovers-even if an application is in high demand for only short periods of time. The cloud offers a solution. It is made up of interconnected servers located in various data centers, but you see what appears to be a centralized location that someone else hosts and manages. By removing the responsibility for maintaining an infrastructure, you're free to concentrate on what matters most: the application. This guide is the third edition of the first volume in a series about Windows Azure. It demonstrates how you can adapt an existing on-premises ASP.NET application to one that operates in the cloud by introducing a fictitious company named Adatum that modifies its expense tracking and reimbursement system, aExpense, so that it can be deployed to Windows Azure. To illustrate the wide range of options and features in Windows Azure, this guide and the code examples available for it show a step-by-step migration process that includes using Windows Azure Web Sites, Virtual Machines, Cloud Services, and SQL Database. Together with useful information on developing, deploying, managing, and costing cloud-hosted applications, this guide provides you with a comprehensive resource for moving your applications to Window Azure. This book is intended for any architect, developer, or information technology (IT) professional who designs, builds, or operates applications and services that are appropriate for the cloud. Although applications do not need to be based on the Microsoft Windows operating system to work in Windows Azure or written using a .NET language, this book is written for people who work with Windows-based systems. You should be familiar with the.NET Framework, Visual Studio, ASP.NET, and Visual C#.

As more software projects adopt a continuous delivery cycle, testing threatens to be the bottleneck in the process. Agile development frequently revisits each part of the source code, but every change requires a re-test of the product. While the skills of the manual tester are vital, purely manual testing can't keep up. Visual Studio 2012 provides many features that remove roadblocks in the testing and debugging process and also help speed up and automate retesting. This guide shows you how to record and play back manual tests to reproduce bugs and verify the fixes, transform manual tests into code to speed up re-testing, monitor your project in terms of tests passed, create and use effective unit tests, load, and performance tests, run build-deploy-test workflows on virtual lab environments, and evolve your testing process to satisfy the demands of agile and continuous delivery. You'll learn how to set up all the tools you need for testing in Visual Studio 2012 and 2010, including Team Foundation Server, the build system, test controllers and agents, SCVMM and Hyper-V. Each chapter is structured so that you can move gradually from entry-level to advanced usage.

Over the years software systems have evolutionarily become more and more complex. One of the techniques for dealing with this inherent complexity of software systems is dependency injection - a design pattern that allows the removal of hard-coded dependencies and makes it possible to assemble a service by changing dependencies easily, whether at run-time or compile-time. It promotes code reuse and loosely-coupled design which leads to more easily maintainable and flexible code. The guide you are holding in your hands is a primer on using dependency injection with Unity - a lightweight extensible dependency injection container built by the Microsoft patterns & practices team. It covers various styles of dependency injection and also additional capabilities of Unity container, such as object lifetime management, interception, and registration by convention. It also discusses the advanced topics of enhancing Unity with your custom extensions. The guide contains plenty of trade-off discussions and tips and tricks for managing your application cross-cutting concerns and making the most out of both dependency injection and Unity. These are accompanied by a real world example that will help you master the techniques. Keep in mind that Unity can be used in a wide range of application types such as desktop, web, services, and cloud. We encourage you to experiment with the sample code and think beyond the scenarios discussed in the guide. In addition, the guide includes the Tales from the Trenches - a collection of case studies that offer a different perspective through the eyes of developers working on the real world projects and sharing their experiences. These chapters make clear the range of scenarios in which you can use Unity, and also highlight its ease of use and flexibility. Whether you are a seasoned developer or just starting your development journey, we hope this guide will be worth your time studying it. We hope you discover that Unity container adds significant benefits to your applications and helps you to achieve the goals of maintainability, testability, flexibility, and extensibility in your own projects.