This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
This guide demonstrates the authors’ ideas in action with three real-world case studies: datacenter replication for business continuity, management of a continuous deployment pipeline, and migration to a microservice architecture. . Software engineering practices require knowledge of the environment in which an application is to be run.
You’ve decided that you’re ready to embark on a modernization project for your legacy.NET applications—but making that decision is only the first step. This should include asking questions like: What is the systemarchitecture? How is the application compiled and packaged? Where is the source code stored? Conclusion.
“We used to have a shared test environment, and we were constantly stepping on each others’ toes. Pedro walks you through the application. The quick command tells it to only build and test the files that have changed.”. Test-DrivenDevelopment. Write a do-nothing entry point for your application.
Test-DrivenDevelopment. Test-drivendevelopment encourages you to think about and improve your design at nearly every step. Breakthroughs happen at all levels of the design, from methods and functions to architectures. Test-DrivenDevelopment. Applicationarchitecture.
We organize all of the trending information in your field so you don't have to. Join 49,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content