Building testable Silverlight and WPF applications wih Caliburn Micro

•Download as PPTX, PDF•

0 likes•1,413 views

TestableSilverlight/WPF Apps With Dennis Doomen

Dennis Doomen Model View-ViewModel INotifyPropertyChanged Events XAML (+C#) ViewModel ServiceAgent {Binding} Command Call Model Loads

Dennis Doomen Inter-VM Communication UntypedPropertyChanged Thread Marshaling Bootstrapping Challenges WCF, RIA or Data Interception Hooking Views toVMs No IObservableCollection Asynchronity Shell-View Life CycleMgmt WCF Data Services Command = Ugly Code

Basic Example

Dennis Doomen Solves ,[object Object]

Bootstrapping

UntypedPropertyChanged

Thread Marshaling

HookingViews toVMs

Command= Ugly Code,[object Object]

Dennis Doomen Solves ,[object Object]

No IObservableCollection

Command = Ugly Code,[object Object]

Dennis Doomen Solves ,[object Object]

Hooking Views toVMs

Command = Ugly Code,[object Object]

Dennis Doomen Solves ,[object Object]

Asynchrony,[object Object]

Dennis Doomen Solves ,[object Object]

Hooking Views toVMs

Shell-View Life Cycle Management,[object Object]

Dennis Doomen Solves ,[object Object]

More Related Content

Similar to Building testable Silverlight and WPF applications wih Caliburn Micro

Presentation Model

Presentation Model

Presentation Model

WinJS at NYC Code Camp 2012

WinJS at NYC Code Camp 2012

WinJS at NYC Code Camp 2012

Dmitri Artamonov

Testing Microservices is hard! Or is it really? One of the precepts of TDD is that if something is hard to test, then potentially the design itself is at fault. With a sweep through design options for Microservices, it can be shown that testing Microservices does not have to be hard, and can become as straightforward as any other test. This does require a radically different design philosophy, which this talk will review and show applied. Come prepared to discover why we should blame Plato for bad software, and why Microservices are really about data, not processes. About David Dawson David is CEO of Simplicity Itself, helping their clients adopt Microservices and cloud-native architectures. www.simplicityitself.io

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

AWS Summit Auckland - Sponsor Presentation - Zerto

AWS Summit Auckland - Sponsor Presentation - Zerto

AWS Summit Auckland - Sponsor Presentation - Zerto

Amazon Web Services

Meteoroid

Building single page applications with angular.js

Building single page applications with angular.js

Building single page applications with angular.js

Dieter De Mesmaeker

Presented at the 2014 Cow Town Code Camp in Ft. Worth, TX - http://CowTownCodeCamp.com - Blog Post: http://developingux.com/2014/07/23/modern-web-development/ The world is moving towards ASP.NET MVC.. but what about your legacy WebForms development. What are the things you can do today to make your WebForms more testable, reliable and even increase the SEO and usability of your WebForms. This talk will walk through applying the Model View Presenter pattern to your ASP.NET WebForm applications and introduce you to some additional enhancements that Microsoft has made to WebForms recently to make your site and life that much better!

Modern ASP.NET Webskills

Modern ASP.NET Webskills

Modern ASP.NET Webskills

A4 from rad to mvc

A4 from rad to mvc

A4 from rad to mvc

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Microsoft TechNet - Belgium and Luxembourg

Opening Up Your Network with SDN

Opening Up Your Network with SDN

Opening Up Your Network with SDN

Open Networking Summits

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

Domain specific languages, together with code generation or interpreters (a.k.a. model-driven development), are becoming more and more important. Since there is a certain overhead involved in building languages and processors, this approach is especially useful in environments where a spe-cific set of languages and generators can be reused many times. Product lines are such an environment. Consequently, the use of domain specific languages (DSLs) for Software Product Line Engi-neering (SPLE) is becoming more relevant. However, exploiting DSLs in the context of product lines involves more than just defining and using languages. This tutorial explains the differences as well as commonalities between model-driven development (MDD) and SPLE and shows how the two approaches can be combined. In this tutorial we will first recap/introduce feature modeling and model-driven development. We then build a simple textual DSL and a code generator based on Eclipse openArchitectureWare (oAW). Based on this language we’ll discuss the kinds of variability expressible via DSLs versus those expressible via feature modeling, leading to a discussion about ways to combine the two. In the next demo slot we’ll do just that: we’ll annotate a model with feature dependencies. When generating code, the elements whose features are not selected will be removed, and hence no code will be generated. Finally we’ll discuss and demo the integration feature dependencies into code generators to con-figure the kind of code generated from the model.

Model-Driven Development in the context of Software Product Lines

Model-Driven Development in the context of Software Product Lines

Model-Driven Development in the context of Software Product Lines

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

MvvmCross

Refacoring vs Rewriting WixStores

Refacoring vs Rewriting WixStores

Refacoring vs Rewriting WixStores

Doron Rosenstock

MVVM+MEF in Silvelight - W 2010ebday

MVVM+MEF in Silvelight - W 2010ebday

MVVM+MEF in Silvelight - W 2010ebday

Model View ViewModel (MVVM) is an architectural pattern that originated from Microsoft and provides a pattern for code-sharing across Windows Store and Windows Phone apps; however, you can take MVVM anywhere - including iOS and Android! MVVM frameworks act as the glue that ties together the apps user interface and business logic and adds amazing features such as data binding and commands. There are several MVVM frameworks that allow you to share more code on iOS, Android, and Windows including Bind, MVVM Light, MvvmCross, and Xamarin.Forms ships with its own lightweight MVVM framework. Come learn what exactly the MVVM pattern is, and when to use it. We will go through the pros and cons of several architectural patterns, such as MVC and MVP, and compare them to MVVM. We will investigate several different MVVM frameworks from lightweight to heavier approaches. Walk away with the ability to leverage the MVVM framework for optimal code reuse in creating beautiful native mobile applications on every platform

MVP Mix 2015 Leveraging MVVM on all Platforms

MVP Mix 2015 Leveraging MVVM on all Platforms

MVP Mix 2015 Leveraging MVVM on all Platforms

James Montemagno

Microservices and Friends

Microservices and Friends

Microservices and Friends

Portable Class Libraries and MVVM

Portable Class Libraries and MVVM

Portable Class Libraries and MVVM

Andreas Kuntner

Similar to Building testable Silverlight and WPF applications wih Caliburn Micro (20)

Presentation Model

Presentation Model

Presentation Model

WinJS at NYC Code Camp 2012

WinJS at NYC Code Camp 2012

WinJS at NYC Code Camp 2012

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

Microservices Manchester: Testing Microservices: Pain or Opportunity? By Davi...

AWS Summit Auckland - Sponsor Presentation - Zerto

AWS Summit Auckland - Sponsor Presentation - Zerto

AWS Summit Auckland - Sponsor Presentation - Zerto

Meteoroid

Building single page applications with angular.js

Building single page applications with angular.js

Building single page applications with angular.js

Modern ASP.NET Webskills

Modern ASP.NET Webskills

Modern ASP.NET Webskills

A4 from rad to mvc

A4 from rad to mvc

A4 from rad to mvc

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Forbidden fruits of Active Directory – Cloning, snapshotting, virtualization

Opening Up Your Network with SDN

Opening Up Your Network with SDN

Opening Up Your Network with SDN

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

ASBIS: Virtualization Aware Networking - Cisco Nexus 1000V

Model-Driven Development in the context of Software Product Lines

Model-Driven Development in the context of Software Product Lines

Model-Driven Development in the context of Software Product Lines

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

Встреча №9. Будущее паттерна MVVM в iOS приложениях, Денис Лебедев

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

CTU June 2011 - Hybrid Cloud Management with Microsoft System Center - Concero

MvvmCross

Refacoring vs Rewriting WixStores

Refacoring vs Rewriting WixStores

Refacoring vs Rewriting WixStores

MVVM+MEF in Silvelight - W 2010ebday

MVVM+MEF in Silvelight - W 2010ebday

MVVM+MEF in Silvelight - W 2010ebday

MVP Mix 2015 Leveraging MVVM on all Platforms

MVP Mix 2015 Leveraging MVVM on all Platforms

MVP Mix 2015 Leveraging MVVM on all Platforms

Microservices and Friends

Microservices and Friends

Microservices and Friends

Portable Class Libraries and MVVM

Portable Class Libraries and MVVM

Portable Class Libraries and MVVM

More from Dennis Doomen

I'm sure every developer wants to be able to change code with confidence and without fear. Readable and self-explanatory code is one aspect of that. Too much coupling is another major source of problems that prevent you from changing one part of the system without causing side-effects. In this talk, I'd like you to show you common sources of unnecessary coupling and offer you options to help prevent and/or break those. I'll talk about how principles like Don't Repeat Yourself and Dependency Injection can be a double-edge sword, how to detect too unnecessary dependencies and how to use the Dependency Inversion Principle to unravel some of those. And yes, I will also talk about controlling dependencies on the package level. Challenge 1. How to prevent too much coupling? 2. We are tought to decrease coupling and increase cohesion 3. How do you increase cohesion? By applying DRY! 4. But DRY creates more coupling 5. And too much decoupling results in a forest of abstractions 6. The solution is… find a balance (or "it depends") On the architecture level 1. Use architecture style that embraces DIP (e.g. Onion, Hexagon, Clean Architecture) 2. Organize your code along functional boundaries -> this will make it easier to break off that boundary for rebuilding/strangler/microservices. 3. Apply DRY within those boundaries only, but allow shared services for complicated capabilities 4. Align your test scope with those internal boundaries… On the package level • Classes and interfaces that are almost always used together should be packaged together. Those that don’t meet that criteria don’t have a place in that package • Packages should not require changes (and thus a new release) for unrelated changes. • There must be no cycles in the dependency structure • A package should only depend upon packages that are more stable than it is or abstract packages On the code level • Avoid technical folders and organize them by functionalities or capabilities • Things in adjacent folders usually mean they are separate boundaries • Use the Tell, Don't Ask principle • Use the Law of Demeter to detect unnecessary coupling • Encapsulate primitive types and collections in specific types • Dependency injection is great, but try to avoid a global container • It's fine to inject concrete classes inside boundaries Strategy for legacy code 1. Ensure you have a safety net using characterisation tests 2. Find existing seams and decouple them better a. Identify modules or functional slices b. Identify groups of classes that are supposed to be used together and are designed to be reusable c. Identify interfaces or abstractions in DI registration code and see if they are truly designed for reusability d. Assume that code in adjacent folders is supposed to be independent e. Move code from different technical folders that belong together in their own (functionally named) folderPublic 3. Use that to define (and visualize) the target architecture

Getting a grip on your code dependencies (2023-10)

Getting a grip on your code dependencies (2023-10)

Getting a grip on your code dependencies (2023-10)

We all love to build greenfield projects, but the reality is that in most jobs you have to deal with a lot of legacy code. This doesn't mean the code is bad. It just means that choices were made that were the right ones at that time, or that the developers were not entire up-to-date with modern development practices. And that's exactly what this talk is about. I enjoy taking such a codebase and gradually introduce architectural seems, add a proper build pipeline, introduce temporary tests and then gradually refactor the codebase to combine more maintainable, testable and reliable. So in this talk, I'd like to unfold my extensive toolbox of practices, principles, tools and mindset to help you improve your legacy code without jeopardizing your business. Understand production environment See which vinaries are running in production and what config files are used Verify the code and the production release are in sync, e.g. DotPeek Analyze logs to understand what features are used Try to get it to run on a local environment Understand code Generate project diagrams and class hierarchies Find origin calls and destination of a parameter using Rider Use navigation options to find inheritors, usages, etc. Use the namespaces and project names to understand the relation Have Rider's AI Assistant or ChatGPT explain the code Track all documentation in a single place Build C4 diagrams Find dead code Reduce the scope of types and members to internal to find more dead code Detect code inefficiencies and dead code using Rider Remove commented out code Build a safety net If therea are tests, add code coverage reporting using Coverlet and use that to find dark spots (HTTP API) Characteristics tests using FluentAssertions, Bogus, xUnit. Use AI to generate them. It's fine, you'll delete them later on Use test containers for .net t lo include the databse Build a couple of end to end UI tests e.g. using Cypress, Playwright, efc Improve deployability Add scripts or builds steps to run the code locally, Nuke build pipeline to get consistency Adopt a version strategy and name branches accordingly Adopt automatic versioning using GitVersion Adopt logging and exception strategy, e.g. Serilog Pulumi to automate PR deployments Improve code Treat all warnings as errors and fix thhem Editorconfig / eslint so auto-format works Configure a personal Rider/R# clean-up profile to auto-format file, project and solution Roslyn analyzers Microsoft.CodeAnalysis.BannedApiAnalyzers StyleCop.Analyzers CSharpGuidelinesAnalyzer Roslynator.Analyzers Meziantou.Analyzer Enable nullable types per file Move new code to .NET 6+ or cross-compile Switch to newer C# versions, possibly using Polysharp File-scope namespaces Target-typed news switch expression String interpolation instead of string.format Use Directory.Build.Props to reduce duplication Improve naming whenever you can Encapsulate prim itive types and collections in d

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

Providing a high quality library like that doesn't come for free. We've been trying to write code that is clean enough for our contributors, write tests that are self-explanatory, ensure breaking changes are strictly controlled and try to make it easy to use. In this talk, I'd like to share the tools and techniques we have been using. I'll talk about the release strategy, documentation, versioning, naming conventions, code structure, the build pipeline, automated testing, code coverage, API change detection, multi-targeting and more. In this talk, I'd like to share the tools and techniques we have been using, how they've enriched our day jobs, and how they may do that for you too. I'll talk about the release strategy, documentation, versioning, naming conventions, code structure, the build pipeline, automated testing, code coverage, API change detection, multi-targeting and more.

What you can learn from an open-source project with 250 million downloads

What you can learn from an open-source project with 250 million downloads

What you can learn from an open-source project with 250 million downloads

I'm sure every developer wants to be able to change code with confidence and without fear. Readable and self-explanatory code is one aspect of that. Too much coupling is another major source of problems that prevent you from changing one part of the system without causing side-effects. In this talk, I'd like you to show you common sources of unnecessary coupling and offer you options to help prevent and/or break those. I'll talk about how principles like Don't Repeat Yourself and Dependency Injection can be a double-edge sword, how to detect too unnecessary dependencies and how to use the Dependency Inversion Principle to unravel some of those. And yes, I will also talk about controlling dependencies on the package level.

Getting a grip on your code dependencies

Getting a grip on your code dependencies

Getting a grip on your code dependencies

About 15 years ago, I got inspired by a series of posts on Test Driven Development written by the Jeremy D. Miller. Now, with many years of great and not-so-great experiences practicing Test Driven Development, I thought it is the time to capture my own “laws”. The term "law" is obviously an exaggeration and "principles or heuristics" cover my intend much better. Either way, I want to talk about the scope of testing, using the observable behavior, naming conventions, state-based vs interaction-based testing, the impact of DRY, patterns to build useful test objects and some of the libraries and tools I use. In short, everything I try to follow every day I write, review or maintain code.

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

Event Sourcing is becoming more mainstream these days, and a lot of conferences have demonstrated the pros and cons of this architecture style from multiple angles. I've done a few of these and publishes a lot of articles on best practices and solutions to common problems. But what nobody did was to show you how to build an event sourced systems in the .NET ecosystem. There are a lot of open-source projects that you can use, so you'll need to find a right mix and your own code to that. So let me show you how I would implement this in .NET with almost 10 years of Event Sourcing experience behind my belt.

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Who remembers the days were you had to manually setup a physical server somewhere in a 19 inch rack? Nowadays those physical racks have been replaced by virtual machines provided by Google, Microsoft and Amazon. But some people are still provisioning them manually. The more mature organizations will script most of the provisioning using the native CLI or HTTP API provided by the specific cloud platform, but quite often those are maintained separately from the code of the system that is being deployed. Terraform by Hashicorp is another attempt to support infrastructure-as-code by using a declarative syntex to define the desired infrastructure. But then again, Yaml isn't really suited for anything but simple single-file configuration settings. Yaml isn't code and doesn't provide real Intellisense, line-by-line debugging and most importantly, refactoring. But what if you could use C# and .NET to provision your infrastructure and treat that code as first-class citizens of your codebase, including all the capabilities that you would expect? Well, let me show you how Pulumi for .NET will allow you to evolve your infrastructure code with the rest of the code base without turning it in a big spaghetti of Yaml files.

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

Whether you're just writing your first unit test or have been practicing Test Driven Development for many years, I'm sure your biggest challenge is to find the right scope for testing. Unfortunately a lot of books and guidance seem to imply that every class or type should be tested separately. Well, I can tell you from 15 years of unit testing experience that that's the best way to shoot yourself in the foot. In this session, I'm going to show you some concrete examples and why I chose a certain boundary for the "unit" in unit testing. I will also share design heuristics I use myself to find those boundaries and why those are not guidelines. I'll also illustrate how principals like DRY and SOLID can be both a blessing and a curse that may lead to the wrong design choices

What is the right unit in unit testing (UpdateConf 2022)

What is the right unit in unit testing (UpdateConf 2022)

What is the right unit in unit testing (UpdateConf 2022)

I don't have to tell anybody how awesome Event Sourcing is as an architecture style. But those that have been using it in production must have experienced the pains of keeping the upgrades fast enough, especially if you use a more traditional relational database like SQL Server. I've once heard somebody say: "If it's slow, make it faster", but rebuilding a big projection is simply a very expensive operations and involves a lot of network traffic between the application and the database servers. Over the years since we adopted Event Sourcing, we've been experimenting a lot and have implemented various improvements to make those reprojections faster. And we haven't stopped. We're already working on some new ideas lately. So in this session, I'd like to share those techiques, their pros and cons and how we implemented them on a more detailed level.

Slow Event Sourcing (re)projections - Just make them faster!

Slow Event Sourcing (re)projections - Just make them faster!

Slow Event Sourcing (re)projections - Just make them faster!

Enough books have been written, articles have been published and Youtube videos have been posted about how you should be behaving as a software developer, Scrum Master or team lead. To be original in this unoriginal world, I started thinking about the things you should NOT be doing. I came up with 50 tools, practices and principles covering topics like dealing with complexity, productivity, architecture, testability, traceability, maintainability, transparency and predictability that I believe hamper you as a professional. That sounds like a lot, but I promise you a fun and entertaining session that I'm sure will trigger a lot of recognition.

50 things software teams should not do.pptx

50 things software teams should not do.pptx

50 things software teams should not do.pptx

Whether you're just writing your first unit test or have been practicing Test Driven Development for many years, I'm sure your biggest challenge is to find the right scope for testing. Unfortunately a lot of books and guidance seem to imply that every class or type should be tested separately. Well, I can tell you from 15 years of unit testing experience that that's the best way to shoot yourself in the foot. In this session, I'm going to show you some concrete examples and why I chose a certain boundary for the "unit" in unit testing. I will also share design heuristics I use myself to find those boundaries and why those are not guidelines. I'll also illustrate how principals like DRY and SOLID can be both a blessing and a curse that may lead to the wrong design choices.

What is the right "unit" in unit testing and why it is not a class?

What is the right "unit" in unit testing and why it is not a class?

What is the right "unit" in unit testing and why it is not a class?

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I'd like to share my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

It’s 2021, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, Dennis regularly talks to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session Dennis likes to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks.

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

If I have to name a single biggest hype in software architecture land then it would be "microservice". They are supposed to be small and focused, can be deployed independently, can work with any technology and will solve all your monolithical problems. But we all know that silver bullets don't exist, plus technology should never be a goal, but merely a means to an end. Nonetheless, following the path towards real microservices is a great strategy for decomposing a monolith without the deployment complexity of the first. So how do you do that? What technologies does the .NET realm offer for us? In this talk, I'll show you some of the pros and cons of micro-services and its ingredients to leverage modern-day .NET and Event Sourcing to move your monolith into a bright new future.

Decomposing the Monolith using modern-day .NET and a touch of microservices

Decomposing the Monolith using modern-day .NET and a touch of microservices

Decomposing the Monolith using modern-day .NET and a touch of microservices

Over the years I've spoken many times about what Event Sourcing is and shared many of the good, the bad and the ugly parts of it in blog posts and various talks. However, I've never talked about how to actually build a system based on this architecture style. I keep getting the same questions over and over again. Like when to apply Event Sourcing and at what architectural level. How to deal with transactional boundaries within and outside the domain. How to build projections that are autonomous, reliable and self-supporting. How to deal with upgrades and blue-green deployments. But also on how to handle bugs, design mistakes and crashing projections. Having made a lot of these mistakes myself over these years, it's time to share my current thoughts and opinions about this. Since the .NET space has a pretty rich set of open-source projections to support this, the examples and code will be .NET. But the concepts are universal, so don't let that scare you off.

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

After several in-depth talks about Event Sourcing, I realized that there's a large group of developers that may have heard about Domain-Driven Design, Command-Query Responsibility Segregation and Event Sourcing, but have not really connected the dots yet. So in this talk, I'd like to take a practical example of a simple domain and gradually introduce functional requirements to see how the principles behind DDD affect the way your entities are going to protect the business rules. After that, I'll introduce some real-world non-functional requirements and see if and how Event Sourcing and/or CQRS may or may not help to accomplish those.

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

It’s 2019, so practices like Test Driven Development (TDD) have long found their way into organizations. However, the practices and principles to keep those unit tests maintainable haven’t really changed. Still, I regularly talk to developers that somehow ended up with an incomprehensible unmaintainable set of unit tests that they once believed in, but are now holding them back. So in this session I like to provide a refresh of those fundamental ideas and talk about why you should practice TDD, revealing intentions, naming conventions, state versus interaction based testing, and how to stay out of the debugger hell with proper mocking and assertion frameworks. And even if you believe you are well versed in the testing realm, join me anyway. Maybe we can learn some tips & tricks from the audience as well. Looking forward to it!

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

A micro-service architecture is a great strategy for decomposing a monolith. In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future. If I have to name a single hype in software architecture land then I would have to mention the micro-service architecture. Micro-services are supposed to be small, have a very focused purpose, can be deployed independently, are completely self-supporting and loosely coupled. Ideally, micro-services are technology agnostic, but hey, we’re in the .NET space, aren’t we? And they are not a goal, but a means to an end. In fact, a micro-service architecture has many benefits and are a great strategy for decomposing a monolith. So how do you build a micro-service? What technologies does the .NET realm offer for us? And what if you don’t want to deploy them independently? In this talk, I’ll show you some of the pros and cons of micro-services and how you can leverage OWIN, .NET, Event Sourcing and the Onion Architecture to gradually move your monolith into a bright new future.

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

Writing maintainable code is not something that is easy to do. Not only is a pretty subjective, a lot of the techniques like Clean Code, SOLID and such can be misinterpreted resulting in unconstructive dogma. I've made it my career's goal to find a good balance between all those different patterns, principles, practices and guidelines. In this talk, I like to share you my own ideas on what it takes to write maintainable code. I'll talk about architecture, class design, automated testing and any consequences on your development process. If you care about your code, be there with me.

A lab around the principles and practices for writing maintainable code (2019)

A lab around the principles and practices for writing maintainable code (2019)

A lab around the principles and practices for writing maintainable code (2019)

I recently was asked what I would do differently if I had the experience I have now. This got me thinking about the mistakes I've made, the traps I fell for and the dogmatism I became part of over the last 22 years of professional software developer in the Microsoft realm. In this talk, I'll be going down memory lane with you and share everything I've learned on architecture, tools, technologies, agile software development, maintainable code, automated testing, documentation and anything else that I think you should know. Prepare yourself for an event of stories, both good and bad.

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

More from Dennis Doomen (20)

Getting a grip on your code dependencies (2023-10)

Getting a grip on your code dependencies (2023-10)

Getting a grip on your code dependencies (2023-10)

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

Tools and practices to help you deal with legacy code

What you can learn from an open-source project with 250 million downloads

What you can learn from an open-source project with 250 million downloads

What you can learn from an open-source project with 250 million downloads

Getting a grip on your code dependencies

Getting a grip on your code dependencies

Getting a grip on your code dependencies

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

My Laws of Test Driven Development (2023)

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Design patterns for Event Sourcing in .NET

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

Automate Infrastructure with Pulumi and C#

What is the right unit in unit testing (UpdateConf 2022)

What is the right unit in unit testing (UpdateConf 2022)

What is the right unit in unit testing (UpdateConf 2022)

Slow Event Sourcing (re)projections - Just make them faster!

Slow Event Sourcing (re)projections - Just make them faster!

Slow Event Sourcing (re)projections - Just make them faster!

50 things software teams should not do.pptx

50 things software teams should not do.pptx

50 things software teams should not do.pptx

What is the right "unit" in unit testing and why it is not a class?

What is the right "unit" in unit testing and why it is not a class?

What is the right "unit" in unit testing and why it is not a class?

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

A lab around the principles and practices for writing maintainable code

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

How to Practice TDD Without Shooting Yourself in the Foot

Decomposing the Monolith using modern-day .NET and a touch of microservices

Decomposing the Monolith using modern-day .NET and a touch of microservices

Decomposing the Monolith using modern-day .NET and a touch of microservices

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Event Sourcing from the Trenches (DDD Europe 2020)

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

Practical introduction to DDD, CQRS and Event Sourcing

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

How to practice TDD without shooting yourself in the foot

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

Decomposing the Monolith (Riga Dev Days 2019)

A lab around the principles and practices for writing maintainable code (2019)

A lab around the principles and practices for writing maintainable code (2019)

A lab around the principles and practices for writing maintainable code (2019)

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Lessons learned from two decades of professional software development

Recently uploaded

How to Troubleshoot Apps for the Modern Connected Worker

How to Troubleshoot Apps for the Modern Connected Worker

How to Troubleshoot Apps for the Modern Connected Worker

AWS Community Day CPH - Three problems of Terraform

AWS Community Day CPH - Three problems of Terraform

AWS Community Day CPH - Three problems of Terraform

Andrey Devyatkin

Architecting Cloud Native Applications

Architecting Cloud Native Applications

Architecting Cloud Native Applications

Dubai, known for its towering skyscrapers, luxurious lifestyle, and relentless pursuit of innovation, often finds itself in the global spotlight. However, amidst the glitz and glamour, the emirate faces its own set of challenges, including the occasional threat of flooding. In recent years, Dubai has experienced sporadic but significant floods, disrupting normalcy and posing unique challenges to its infrastructure. Among the critical nodes in this bustling metropolis is the Dubai International Airport, a vital hub connecting the world. This article delves into the intersection of Dubai flood events and the resilience demonstrated by the Dubai International Airport in the face of such challenges.

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

MS Copilot expands with MS Graph connectors

MS Copilot expands with MS Graph connectors

MS Copilot expands with MS Graph connectors

Nanddeep Nachan

Exploring Multimodal Embeddings with Milvus

Exploring Multimodal Embeddings with Milvus

Exploring Multimodal Embeddings with Milvus

Scaling API-first – The story of a global engineering organization Ian Reasor, Senior Computer Scientist - Adobe Radu Cotescu, Senior Computer Scientist - Adobe Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Corporate and higher education. Two industries that, in the past, have had a clear divide with very little crossover. The difference in goals, learning styles and objectives paved the way for differing learning technologies platforms to evolve. Now, those stark lines are blurring as both sides are discovering they have content that’s relevant to the other. Join Tammy Rutherford as she walks through the pros and cons of corporate and higher ed collaborating. And the challenges of these different technology platforms working together for a brighter future.

Corporate and higher education May webinar.pptx

Corporate and higher education May webinar.pptx

Corporate and higher education May webinar.pptx

Rustici Software

Three things you will take away from the session: • How to run an effective tenant-to-tenant migration • Best practices for before, during, and after migration • Tips for using migration as a springboard to prepare for Copilot in Microsoft 365 Main ideas: Migration Overview: The presentation covers the current reality of cross-tenant migrations, the triggers, phases, best practices, and benefits of a successful tenant migration Considerations: When considering a migration, it is important to consider the migration scope, performance, customization, flexibility, user-friendly interface, automation, monitoring, support, training, scalability, data integrity, data security, cost, and licensing structure Next Wave: The next wave of change includes the launch of Copilot, which requires businesses to be prepared for upcoming changes related to Copilot and the cloud, and to consolidate data and tighten governance ShareGate: ShareGate can help with pre-migration analysis, configurable migration tool, and automated, end-user driven collaborative governance

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

FWD Group - Insurer Innovation Award 2024

FWD Group - Insurer Innovation Award 2024

FWD Group - Insurer Innovation Award 2024

The Digital Insurer

Join our latest Connector Corner webinar to discover how UiPath Integration Service revolutionizes API-centric automation in a 'Quote to Cash' process—and how that automation empowers businesses to accelerate revenue generation. A comprehensive demo will explore connecting systems, GenAI, and people, through powerful pre-built connectors designed to speed process cycle times. Speakers: James Dickson, Senior Software Engineer Charlie Greenberg, Host, Product Marketing Manager

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Retrieval augmented generation (RAG) is the most popular style of large language model application to emerge from 2023. The most basic style of RAG works by vectorizing your data and injecting it into a vector database like Milvus for retrieval to augment the text output generated by an LLM. This is just the beginning. One of the ways that we can extend RAG, and extend AI, is through multilingual use cases. Typical RAG is done in English using embedding models that are trained in English. In this talk, we’ll explore how RAG could work in languages other than English. We’ll explore French, Chinese, and Polish.

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Introduction to Multilingual Retrieval Augmented Generation (RAG)

[BuildWithAI] Introduction to Gemini.pdf

[BuildWithAI] Introduction to Gemini.pdf

[BuildWithAI] Introduction to Gemini.pdf

The microservices honeymoon is over. When starting a new project or revamping a legacy monolith, teams started looking for alternatives to microservices. The Modular Monolith, or 'Modulith', is an architecture that reaps the benefits of (vertical) functional decoupling without the high costs associated with separate deployments. This talk will delve into the advantages and challenges of this progressive architecture, beginning with exploring the concept of a 'module', its internal structure, public API, and inter-module communication patterns. Supported by spring-modulith, the talk provides practical guidance on addressing the main challenges of a Modultith Architecture: finding and guarding module boundaries, data decoupling, and integration module-testing. You should not miss this talk if you are a software architect or tech lead seeking practical, scalable solutions. About the author With two decades of experience, Victor is a Java Champion working as a trainer for top companies in Europe. Five thousands developers in 120 companies attended his workshops, so he gets to debate every week the challenges that various projects struggle with. In return, Victor summarizes key points from these workshops in conference talks and online meetups for the European Software Crafters, the world’s largest developer community around architecture, refactoring, and testing. Discover how Victor can help you on victorrentea.ro : company training catalog, consultancy and YouTube playlists.

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Accelerating FinTech Innovation: Unleashing API Economy and GenAI Vasa Krishnan, Chief Technology Officer - FinResults Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Discover the innovative features and strategic vision that keep WSO2 an industry leader. Explore the exciting 2024 roadmap of WSO2 API management, showcasing innovations, unified APIM/APK control plane, natural language API interaction, and cloud native agility. Discover how open source solutions, microservices architecture, and cloud native technologies unlock seamless API management in today's dynamic landscapes. Leave with a clear blueprint to revolutionize your API journey and achieve industry success!

WSO2's API Vision: Unifying Control, Empowering Developers

WSO2's API Vision: Unifying Control, Empowering Developers

WSO2's API Vision: Unifying Control, Empowering Developers

DBX First Quarter 2024 Investor Presentation

DBX First Quarter 2024 Investor Presentation

DBX First Quarter 2024 Investor Presentation

💥 You’re lucky! We’ve found two different (lead) developers that are willing to share their valuable lessons learned about using UiPath Document Understanding! Based on recent implementations in appealing use cases at Partou and SPIE. Don’t expect fancy videos or slide decks, but real and practical experiences that will help you with your own implementations. 📕 Topics that will be addressed: • Training the ML-model by humans: do or don't? • Rule-based versus AI extractors • Tips for finding use cases • How to start 👨‍🏫👨‍💻 Speakers: o Dion Morskieft, RPA Product Owner @Partou o Jack Klein-Schiphorst, Automation Developer @Tacstone Technology

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

UiPathCommunity

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Product Anonymous

Passkeys: Developing APIs to enable passwordless authentication Cody Salas, Sr Developer Advocate | Solutions Architect - Yubico Apidays New York 2024: The API Economy in the AI Era (April 30 & May 1, 2024) ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Recently uploaded (20)

How to Troubleshoot Apps for the Modern Connected Worker

How to Troubleshoot Apps for the Modern Connected Worker

How to Troubleshoot Apps for the Modern Connected Worker

AWS Community Day CPH - Three problems of Terraform

AWS Community Day CPH - Three problems of Terraform

AWS Community Day CPH - Three problems of Terraform

Architecting Cloud Native Applications

Architecting Cloud Native Applications

Architecting Cloud Native Applications

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

Rising Above_ Dubai Floods and the Fortitude of Dubai International Airport.pdf

MS Copilot expands with MS Graph connectors

MS Copilot expands with MS Graph connectors

MS Copilot expands with MS Graph connectors

Exploring Multimodal Embeddings with Milvus

Exploring Multimodal Embeddings with Milvus

Exploring Multimodal Embeddings with Milvus

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Apidays New York 2024 - Scaling API-first by Ian Reasor and Radu Cotescu, Adobe

Corporate and higher education May webinar.pptx

Corporate and higher education May webinar.pptx

Corporate and higher education May webinar.pptx

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

Strategize a Smooth Tenant-to-tenant Migration and Copilot Takeoff

FWD Group - Insurer Innovation Award 2024

FWD Group - Insurer Innovation Award 2024

FWD Group - Insurer Innovation Award 2024

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Connector Corner: Accelerate revenue generation using UiPath API-centric busi...

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Introduction to Multilingual Retrieval Augmented Generation (RAG)

Introduction to Multilingual Retrieval Augmented Generation (RAG)

[BuildWithAI] Introduction to Gemini.pdf

[BuildWithAI] Introduction to Gemini.pdf

[BuildWithAI] Introduction to Gemini.pdf

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Modular Monolith - a Practical Alternative to Microservices @ Devoxx UK 2024

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

Apidays New York 2024 - Accelerating FinTech Innovation by Vasa Krishnan, Fin...

WSO2's API Vision: Unifying Control, Empowering Developers

WSO2's API Vision: Unifying Control, Empowering Developers

WSO2's API Vision: Unifying Control, Empowering Developers

DBX First Quarter 2024 Investor Presentation

DBX First Quarter 2024 Investor Presentation

DBX First Quarter 2024 Investor Presentation

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

DEV meet-up UiPath Document Understanding May 7 2024 Amsterdam

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

ProductAnonymous-April2024-WinProductDiscovery-MelissaKlemke

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Apidays New York 2024 - Passkeys: Developing APIs to enable passwordless auth...

Building testable Silverlight and WPF applications wih Caliburn Micro

1. TestableSilverlight/WPF Apps With Dennis Doomen

2. Dennis Doomen Model View-ViewModel INotifyPropertyChanged Events XAML (+C#) ViewModel ServiceAgent {Binding} Command Call Model Loads

3. Dennis Doomen Inter-VM Communication UntypedPropertyChanged Thread Marshaling Bootstrapping Challenges WCF, RIA or Data Interception Hooking Views toVMs No IObservableCollection Asynchronity Shell-View Life CycleMgmt WCF Data Services Command = Ugly Code

4. Basic Example

5.

6. Bootstrapping

7. UntypedPropertyChanged

8. Thread Marshaling

9. HookingViews toVMs

10.

11.

12. No IObservableCollection

13.

14.

15. Hooking Views toVMs

16.

17.

18.

19.

20. Hooking Views toVMs

21.

22.

23. Hooking Views toVMs

24.

25.

26.

27.

28. UntypedPropertyChanged

29. Bootstrapping

30. Thread Marshaling

31. Interception

32. WCF, RIA or Data

33. Hooking Views toVMs

34. No IObservableCollection

35. Asynchronity

36. Shell-View Life CycleMgmt

37. WCF Data Services

38.

39. Emaildennis.doomen@avivasolutions.nl Twitter @ddoomen Blogwww.dennisdoomen.net