Entity Framework 6 examples updated to use MsSqlCE. #100
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…quires installation of SqlExpress MSSQLLocalDB to Microsoft SQL Server Compact Edition (SqlCE 4.0): Server Less local Db - no installlation/external dependancy so an easy deploy
Change App.config and .efmodel files Add NuGet dependencies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is for a migration of the Entity Framework 6 examples from using Microsoft SQL Server Express (MsSqlExpress) to Microsoft SQL Server Compact Edition (MsSqlCE).
MsSqlCE offers a simpler, file-based approach to local databases, which eliminates the need for a Ms SqlExpress Local Db database server installation and initialisation. This can significantly lower the barrier to entry for new contributors and evaluators of the EFDesigner examples.
It is hoped that this change will encourage more developers to explore and contribute to the EFDesigner project by lowering the initial setup barriers and promoting a more streamlined development workflow.
I look forward to your feedback and any suggestions for further improvements.