You're reading from Microsoft Power Platform Enterprise Architecture A guide for architects and decision makers to craft complex solutions tailored to meet business needs

Product type Paperback

Published in Sep 2020

Publisher Packt

ISBN-13 9781800204577

Length 452 pages

Edition 1st Edition

Languages

Tools

Power Platform

Concepts

Enterprise Resource Planning

Author (1):

Robert Rybaric

View More author details

Table of Contents (15) Chapters

Preface

1. Section 1: The Basics

2. Chapter 1: Microsoft Power Platform and Microsoft Dynamics 365 Overview FREE CHAPTER

3. Chapter 2: Microsoft 365 and Microsoft Azure Overview

4. Section 2: The Architecture

5. Chapter 3: Understanding Microsoft's Power Platform Architecture

6. Chapter 4: Tools and Techniques

7. Chapter 5: Application Lifecycle Management

8. Section 3: Implementation

9. Chapter 6: Implementation Approach and Methodologies

10. Chapter 7: Microsoft Power Platform Security

11. Chapter 8: Microsoft Power Platform Extensibility

12. Chapter 9: Microsoft Power Platform Integration

13. Chapter 10: Microsoft Power Platform Data Migration

14. Other Books You May Enjoy

Leave a review - let other readers know what you think

Presenting custom development tools

In this section, you will learn about the most important Microsoft and community tools that are used for custom development within Power Platform solutions. This toolset primarily focuses on IT pro developers.

Learning about Visual Studio

Visual Studio is the traditional major development tool from Microsoft and is used for all custom development work across all Microsoft and many non-Microsoft technologies. Visual Studio is an integrated development environment (IDE) that supports not just writing code, but also compiling, building, debugging, and packaging it into solution packages. Visual Studio is available for Windows and Mac PCs. Visual Studio offers several versions, of which Visual Studio Community is free of charge.

For the Power Platform solutions, Visual Studio is used for creating many different custom development artifacts – preferably those that are heavily dependent on the Microsoft .NET framework, such as the following...