# .NET Conf Published articles for .NET Conf. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Build an Endpoint Data Loss Prevention Strategy for Your Development Team DevFeed: [How to Build an Endpoint Data Loss Prevention Strategy for Your Development Team]() Original publisher: [Read original article]() Author: Alex Tray Published: 2026-09-15T21:03:09Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [data loss prevention](), [Development](), [Access Control](), [data]() Tags: [access-control](), [cybersecurity](), [cybersecurityawareness](), [data-loss-prevention](), [data-protection](), [database](), [development](), [encryption](), [endpoint-security](), [hardcoded-credentials](), [it-security](), [net-conf](), [remote-access](), [secrets](), [sensitive-data](), [web-development]() ### AI overview A tutorial for development teams on building endpoint data loss prevention strategies. It covers auditing laptops for secrets and sensitive data, removing unnecessary copies, rotating exposed credentials, and establishing access controls. ### Source excerpt A developer's laptop holds more sensitive data than most people realize: API keys, database credentials, staging environment secrets, and sometimes entire copies of production data pulled down "just f ## Share your .NET story with the community DevFeed: [Share your .NET story with the community]() Original publisher: [Read original article]() Author: Luis Quintanilla Published: 2026-09-14T17:05:00Z Content type: article Language: en Sources: [.NET Blog]() Topics: [.NET](), [.NET Conf](), [Development]() Tags: [2026](), [blog](), [community](), [conference](), [customer-stories](), [developer-stories](), [developers](), [development](), [modernization](), [net](), [net-conf](), [performance](), [post](), [virtual-event]() ### AI overview Microsoft invites teams to share how they use .NET to solve practical problems for possible inclusion in .NET Conf 2026 and other .NET channels. Submissions may describe applications, system modernization, performance, security, efficiency, modern C#, or practical AI-powered capabilities. ### Source excerpt Share how your team uses .NET to solve real problems and help us bring more community stories to .NET Conf 2026 and other .NET channels. The post Share your .NET story with the community appeared first on .NET Blog. ## JDK 27 Runtime Updates Release Notes DevFeed: [JDK 27 Runtime Updates Release Notes]() Original publisher: [Read original article]() Author: Billy Korando Published: 2026-09-12T00:00:00Z Content type: release Language: en Sources: [Inside Java]() Topics: [JDK 27](), [Release notes](), [releases](), [Java]() Tags: [env-file-security](), [gc](), [jdk-27](), [memory](), [net-conf](), [passwords](), [performance](), [release](), [release-notes]() ### AI overview This article reviews runtime updates in JDK 27, including G1GC becoming the default garbage collector in all cases, Compact Object Headers being enabled by default, and improved JFR redaction and filtering for sensitive information such as passwords and API keys. ### Source excerpt Let's review the performance updates, new runtime features, and other changes to existing features that are in the JDK 27 release! ## .NET Conf 2026 Community Days Call for Presenters Is Open DevFeed: [.NET Conf 2026 Community Days Call for Presenters Is Open]() Original publisher: [Read original article]() Author: Javier Lozano, Chris Sfanos, Jon Galloway Published: 2026-09-08T20:30:00Z Content type: news Language: en Sources: [.NET Blog]() Topics: [.NET]() Tags: [call-for-presenters](), [community](), [conference](), [net](), [net-conf](), [virtual-event]() ### AI overview The .NET Conf 2026 Community Days call for presenters invites proposals for community-led sessions about building with .NET and software development practices. ### Source excerpt Submit your session proposal for the community-led .NET Conf 2026 Community Days by October 6, 2026. The post .NET Conf 2026 Community Days Call for Presenters Is Open appeared first on .NET Blog. ## .NET Conf 2026 - Save the Date DevFeed: [.NET Conf 2026 - Save the Date]() Original publisher: [Read original article]() Author: Jon Galloway Published: 2026-08-25T16:28:27Z Content type: news Language: en Sources: [.NET Blog]() Topics: [.NET Conf](), [.NET](), [C# 15](), [ASP.NET Core](), [Blazor](), [WebAssembly](), [Aspire](), [OpenAPI Specification](), [Model Context Protocol]() Tags: [asp-net-core](), [blazor](), [c-sharp-15](), [community](), [conference](), [event](), [mcp](), [net](), [net-11](), [net-conf](), [speakers](), [union-types](), [virtual-event](), [webassembly]() ### AI overview Microsoft announces .NET Conf 2026, a free online event running November 10-12, featuring community sessions and the launch of .NET 11. The article previews updates across .NET, including C# 15 union types, .NET MAUI, ASP.NET Core, Blazor, OpenAPI, Aspire, and the official MCP C# SDK. ### Source excerpt .NET Conf returns November 10-12, 2026, with three days of sessions, community, and the launch of .NET 11. The post .NET Conf 2026 - Save the Date appeared first on .NET Blog. ## Swift Testing explained with code examples DevFeed: [Swift Testing explained with code examples]() Original publisher: [Read original article]() Author: Antoine van der Lee Published: 2026-08-17T08:51:15Z Content type: tutorial Language: en Sources: [SwiftLee]() Topics: [Swift](), [Xcode](), [Code]() Tags: [examples](), [net-conf](), [swift](), [swift-testing](), [testing](), [xcode]() ### AI overview This tutorial introduces Swift Testing, the modern Swift testing framework built around expressive macros such as @Test, #expect, and #require. It explains how Swift Testing replaces XCTest, reduces repetitive boilerplate, defines tests globally, and organizes them with structs, traits, and tags. ### Source excerpt Swift Testing is the modern framework for writing tests in Swift, built around expressive macros like @Test, #expect, and #require. It's the successor to XCTest and the default testing framework for new projects in Xcode. Instead of dozens of assertion methods, you work with a single expressive macro that tells you exactly why a test ... -> The post Swift Testing explained with code examples appeared first on SwiftLee. ## SCIM Deprovisioning Is a Promise Your App Probably Breaks DevFeed: [SCIM Deprovisioning Is a Promise Your App Probably Breaks]() Original publisher: [Read original article]() Author: WorkOS Published: 2026-08-06T01:29:36Z Content type: article Language: en Sources: [WorkOS Blog]() Topics: [Security](), [API](), [HTTP](), [JSON](), [Internet Engineering Task Force (IETF)](), [Protocol (disambiguation)]() Tags: [api](), [http](), [identity](), [idp](), [ietf](), [json](), [net-conf](), [protocol](), [schema](), [security](), [standards](), [state](), [token]() ### AI overview This article explains that SCIM deprovisioning updates identity state but does not automatically invalidate an application's sessions, refresh tokens, or API keys. It describes how identity providers commonly use soft deactivation and why applications must explicitly handle the resulting offboarding state. ### Source excerpt SCIM tells you a user is gone, but sessions, refresh tokens, and API keys often outlive deprovisioning. Here's why offboarding needs more than a user row. ## Effortless Data Fetching: Introducing Apollo Connectors for REST APIs DevFeed: [Effortless Data Fetching: Introducing Apollo Connectors for REST APIs]() Original publisher: [Read original article]() Author: Robert Walters Published: 2024-12-05T14:00:17Z Content type: tutorial Language: en Sources: [Apollo Blog]() Topics: [Apollo Connectors](), [GraphQL](), [REST API](), [React]() Tags: [announcement](), [apollo-connectors](), [graphql](), [net-conf](), [react](), [rest-apis](), [tutorial]() ### AI overview This tutorial demonstrates how Apollo Connectors can fetch data from REST APIs without custom GraphQL resolvers. It walks through a React currency-converter application using the Apollo GraphQL client, CurrencyAPI, Apollo Studio, and Rover CLI. ### Source excerpt Writing resolvers for REST APIs has been a rite of passage for developers working with GraphQL, but what if there were an easier way? Meet Apollo Connectors. As shown in Figure 1, Apollo Connectors mitigate the need to write code that connects to and returns data from REST APIs, reducing code surface area and time so you can focus on the business problem you're trying to solve. ## Kotlin's Flow in ViewModels: it's complicated DevFeed: [Kotlin's Flow in ViewModels: it's complicated]() Original publisher: [Read original article]() Author: Christophe Beyls Published: 2021-08-28T10:42:09Z Content type: tutorial Language: en Sources: [Stories by Christophe Beyls on Medium]() Topics: [Android](), [Kotlin](), [Programming]() Tags: [android](), [android-app-development](), [androiddev](), [architecture-components](), [background-work](), [caching](), [configuration](), [flow](), [google](), [kotlin](), [livedata](), [net-conf](), [state](), [ui](), [viewmodel]() ### AI overview This article explains the challenges of loading UI data in Android applications when screen lifecycles and configuration changes are involved. It outlines goals such as caching valid data, pausing background work when screens are inactive, and avoiding unnecessary interruptions during configuration changes, then discusses ViewModel and LiveData as tools for addressing them. ### Source excerpt LiveData is still your friend Loading UI data in Android applications can be challenging. The lifecycles of the various screens need to be taken into account, as well as configuration changes leading to the destruction and recreation of Activities. The individual screens of an app constantly toggle between interactive and hidden as the user navigates further and back in an app, switches from one app to another, or the device screen gets locked or unlocked. Each component needs to play fair and only perform active work when given the ball. Configuration changes happen on various occasions: when changing the device orientation, switching the app to multi-window mode or resizing its window size, switching to dark or light mode, changing the default locale or font sizes, and more. Goals of efficiency To achieve efficient data loading in Activities and Fragments leading to the best user experience, the following should be considered: Caching: data that has been loaded successfully and is still valid should be delivered immediately and not loaded a second time. In particular, when an existing Activity or Fragment becomes visible again, or after an Activity gets recreated on configuration change; Avoiding background work: when an Activity or Fragment becomes invisible (moves from the STARTED to the STOPPED state), any ongoing loading work should be paused or canceled in order to save resources. This is especially important for endless streams of data like location updates or periodic refreshes of any kind; No work interruption during configuration changes: this is an exception to the second goal. During configuration changes, an Activity gets replaced by a new instance of it while preserving its state, so canceling ongoing work when the old instance is destroyed to immediately restart it when the new instance is created would be counter-productive. Today: ViewModel and LiveData To help developers reach these goals with code of manageable complexity, Google released the fir ## The Instagram ads Facebook won't show you DevFeed: [The Instagram ads Facebook won't show you]() Original publisher: [Read original article]() Published: 2021-05-04T00:00:00Z Content type: opinion Language: en Sources: [Signal Blog]() Topics: [data](), [Instagram](), [Internet](), [systems]() Tags: [ads](), [data](), [facebook](), [instagram](), [net-conf](), [platform](), [technology](), [visibility]() ### AI overview The article describes an attempt to buy targeted Instagram ads that would show viewers personal data Facebook collects and uses for advertising. Facebook denied the ads, illustrating the article's argument that the platform sells visibility into people's lives while limiting transparency about how their data is used. ### Source excerpt Companies like Facebook aren't building technology for you, they're building technology for your data. They collect everything they can from FB, Instagram, and WhatsApp in order to sell visibility into people and their lives. This isn't exactly a secret, but the full picture is hazy to most - dimly concealed within complex, opaquely-rendered systems and fine print designed to be scrolled past. The way most of the internet works today would be considered intolerable if translated into comprehensible real world analogs, but it endures because it is invisible. Read more... ## Integration verbosity and good layering DevFeed: [Integration verbosity and good layering]() Original publisher: [Read original article]() Published: 2021-04-07T00:00:00Z Content type: article Language: en Sources: [Jake Wharton]() Topics: [Android](), [XML](), [Dagger](), [SQLite](), [MySQL]() Tags: [abstraction](), [dagger](), [dependency](), [design](), [env-file-security](), [integrations](), [mysql](), [net-conf]() ### AI overview The article argues that integration verbosity can be a consequence of good layering. General-purpose libraries such as view binding, Dagger, SQLDelight, and RecyclerView must leave higher-level integration and configuration decisions to their callers, enabling more flexible libraries and platforms. ### Source excerpt One of my favorite non-features from building view binding is that it lacks integration with activities or fragments. If you use view binding with activities or fragments, however, this fact might be to your disdain. Every activity using view binding is forced to do something along the lines of: override fun onCreate(savedInstanceState: Bundle) { super.onCreate(savedInstanceState) val binding = ProfileViewBinding.inflate(layoutInflater) setContentView(binding.root) // Do stuff with 'binding' } This is textbook verbosity, and some would argue boilerplate. It only gets worse with fragments (due to their poor design and to no specific fault of view binding which works the same as any View reference). View binding exists at a different layer of abstraction than is appropriate for integration with higher-level components like activities or fragments. It serves as a type-safe representation of a schema declared in an XML file and that's it. It has no more knowledge of activities and fragments than the associated R.layout.profile_view integer does. Higher-level libraries like androidx.activity and androidx.fragment have integrations with those R.layout integers. If you're upset that view binding has no turn-key solution for activities and fragments then this is the tree you should be barking up. View binding wasn't built with verbosity in mind. Hell, it's not even that verbose. It ended up this way because it's the design the layer of abstraction it operates at demands. The same pattern occurs in some of my other favorite libraries. Dagger offers you nothing and requires that you build up the dependency injectors, their hierarchy, and their lifecycle entirely yourself. SQLDelight makes you specify database info in the build configuration and a database driver in the runtime API. RecylerView requires at minimum an adapter subtype and to choose and configure a layout manager. The layer at which these tools operate is sufficiently general such that their good design requires ## Using Android Architecture Components with Firebase Realtime Database (Part 3) DevFeed: [Using Android Architecture Components with Firebase Realtime Database (Part 3)]() Original publisher: [Read original article]() Author: Doug Stevenson Published: 2017-12-22T00:00:00Z Content type: tutorial Language: en Sources: [Firebase Blog]() Topics: [Android](), [Realtime Database](), [Firebase](), [Database]() Tags: [android](), [android-architecture](), [architecture-components](), [best-practices](), [firebase](), [net-conf](), [optimization](), [performance](), [realtime-database](), [threading](), [viewmodel]() ### AI overview This tutorial explains how lifecycle-aware Android Architecture Components work with Firebase Realtime Database. It focuses on LiveData and ViewModel, threading for expensive data manipulation, and the performance cost of removing and re-adding database listeners during Activity configuration changes. ### Source excerpt News, tutorials, and updates from the Firebase team.