like below fixes the issue The Domain layer contains all the code that enforces business rules. It should be technology agnostic (like specific databases - sql, no sql - or protocols - HTTP, REST) and frameworks agnostic. This means that it looks the same whether the Aggregates are persisted in an SQL database or in a NoSQL database, it is called from a HTTP controller or from a console application.
wish helps you You're not missing any plugins, nor is VS ignoring the Import directives. The import directives are used when build the project. If you build the project, it builds fine and has all the classes that can be found in System.Data.SQLite*.cs.
Any of those help The solution we came up with was to add a new class library to our solution. This keeps the web site project separate and then we added a reference to our website pointing to the class library. We slowly are move the App Code from the website to the class lib, importing the necessary namespaces to the class library as needed.
C++ Visual Studio - multi-project solution - "static lib" vs "include directories"