The journey of connection strings in Core Framework apps is a story of practicality and efficiency, with roots in database theory and the evolution of software architecture. While not directly tied to academic contributors, the development of connection strings in Core Framework apps draws inspiration from key principles and pioneers in the field.

Database theory, a cornerstone of computer science, laid the groundwork for efficient data storage and retrieval. Edgar F. Codd's relational database model, introduced in his seminal paper "A Relational Model of Data for Large Shared Data Banks," set the stage for structured and organized data storage.

The advent of Object-Relational Mapping (ORM) frameworks, such as Hibernate in Java and Entity Framework in the .NET ecosystem, further streamlined the interaction between applications and databases. These frameworks abstracted away the intricacies of database communication, influencing how connection strings are utilized in modern applications.

In the context of .NET Core Framework apps, the transition from the traditional .NET Framework brought about changes in configuration practices. The move towards a more modular and lightweight framework prompted the use of JSON-based configuration files, where connection strings found a new home.

David Fowler and Damian Edwards, key contributors to the development of ASP.NET and ASP.NET Core, played crucial roles in shaping the architecture and configuration practices of the framework. Their efforts ensured that Core Framework apps could seamlessly integrate with various data sources through flexible and customizable connection strings.

The .NET Core team's commitment to open-source development fostered community collaboration, allowing developers worldwide to contribute to and enhance the framework. While not explicitly academic, this collaborative model draws on the principles of shared knowledge and collective expertise.

Connection strings in .NET Core Framework apps follow a convention of specifying the database provider, server address, authentication credentials, and database name. This configuration flexibility allows developers to adapt their connection strings based on the specific requirements of the application and the chosen database technology.

Theoretical concepts like Dependency Injection (DI) and Configuration Management are integral to understanding how connection strings are handled in Core Framework apps. Dependency Injection ensures that components receiving the connection string can be easily replaced or configured, promoting modularity and testability.

The rise of cloud-based databases and services, such as Azure SQL Database and Amazon RDS, has further influenced connection string practices. Developers now need to consider additional parameters related to cloud-based authentication, security, and scalability when crafting connection strings.

In summary, the history of connection strings in Core Framework apps is a fusion of theoretical database principles, ORM frameworks, and the collaborative efforts of developers like David Fowler and Damian Edwards. The evolution reflects the adaptability of software architecture to changing paradigms, where connection strings play a pivotal role in configuring seamless communication between applications and databases.