-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify branching strategy in the docs #43
Comments
Hi there! Have you changed packages to target SQLServer? You need to change both the data package as well as the Identity package! See this page for reference: https://piranhacms.org/docs/architecture/databases/sql-server Best regards |
@tidyui Yes, sorry, I forgot to mention. I installed both packages as the necessary types for SQL EF and SQL Identity aren't already present. I did not uninstall any packages, only added the two referenced on this page. |
@timgabrhel I actually also missed that you were running on master and not the current packages 😁 Master is our development branch and might not be stable. The SiteLogo field is new for 8.4 and we probably haven’t had time to create the migration for SQLServer yet! If you’re happy with the 8.3 functionality you can find the latest stable release in the version branch! Best regards Håkan |
@filipjansson Can you take a look at this when you get the time. It looks like you have already created the migration for |
@tidyui Might I suggest some guidance of this note, perhaps under this section. |
Yes good idea! I’ll rename this issue and move it to the documentation repo! |
Hi! I tried to reproduce this behavior but without success. What I did notice is that your My startup:
BR |
Trying to get started exploring the new Piranha Core, but running in to an issue on first time setup. I've done a clone on the full project source, currently on Master.
LogoId
column on the Site.20200625060542_AddSiteLogo.cs
I'm not sure if the migration is failing, or if it's simply not executing. I'm not as familiar with EF migrations so some guidance is appreciated.
The text was updated successfully, but these errors were encountered: