I managed to perform the migration from IdentityServer4 v3 to IdentityServer4 v4 using the MS SQL scripts linked from this page: https://www.identityserver.com/articles/migrating-your-identityserver4-v3-database-to-identityserver4-v4. I would really like to have similar scripts for performing the migration from IdentityServer4 v4 to IdentityServer V6 - I've only been able to find a guide on how to do the migration using dotnet ef migrations, on this page: https://docs.duendesoftware.com/identityserver/v6/upgrades/is4_v4_to_dis_v6/. If possible, I'd like to avoid using ef migrations as it's very new tech for me.
Thanks in advance!
Related
We are migrating an application from Azure to AWS and we have migrated the SQL Server database to AWS RDS SQL Server database.
In AWS we use codepipeline / codebuild to deploy our application and which is pretty much automated when a push happens to github we have an application deployed. Similarly we also want any DB changes to also be deployed via pipeline.
We will have the dacpac scripts available when we build our project and all we need is to deploy these dacpac scripts from codepipeline to AWS RDS, so I researched to see if this is possible and how to achieve, but I got little help. If any of you have implemented this or are aware, can please help to share your experience, would be highly appreciated.
Thanks in advance.
Evening.
I have to develop an api for an existing SQL Server 2017 database.
I need to use Microsoft Web API, and I would like to use Core 3.1 but I have read I have to use migrations and such, and i have been told not to build the api using migrations.
Would I be better using .Net Framework instead or is there a way to use Core without using migrations?
I hope that it's not too broad a question, but I really am struggling to make a decision so any feedback etc would be greatly appreciated.
carlson
If you'd like to access data from an existing database and tables with Entity Framework (EF) Core in your ASP.NET Core Web API project, you can try to use Scaffold-DbContext command or dotnet ef dbcontext scaffold command to generate code for a DbContext and entity types for your database.
Besides, you can also install and use Microsoft.Data.SqlClient to access your existing SQL Server database in ASP.NET Core project.
I'm struggling deploying an umbraco built blog through Microsoft Azure.
I have a finished Umbraco database i exported to Microsoft Azure SQL Database.
I have a finished the blog i've deployed to an Azure app service.
I have connected the blog to the Azure SQL Database connectionstring.
But when i publish my website i get redirected to an Umbraco first-time-install. Instead of my Homepage with all the contents. And i know the tables are in the Azure SQL Database through MSSQL.
The blog works perfectly on localhost. I run IIS if that could be something that makes a difference.
Any ideas what i miss?
Is it saying you need to upgrade or install? If it is install then your connection string is either wrong or your database is not an Umbraco database.
I'm in OSX and I'm creating a new ASP.NET Core Web API. I've followed this tutorial: https://docs.efproject.net/en/latest/platforms/netcore/new-db-sqlite.html
That's cool and all but what about Sql Server? Now I know SQL Server won't yet run on OSX (https://www.microsoft.com/en-us/cloud-platform/sql-server-on-linux).
The only way I can see to make this work is if I create a cloud remote SQL server (on Azure or similar), then connect with it from my ASP.NET core application. I tried following this, but it assumes VS2015 https://docs.efproject.net/en/latest/platforms/aspnetcore/existing-db.html. We don't have the package manager console in VSCode and I don't know if there is an equivalent to Scaffold-DbContext.
So how do I make a connection to SQLServer and how do I do things like EF migrations to update that database.
All the packages download can be done without the package installer, by using project.json and dotnet restore (if VSCode doesn't do it when project.json is saved).
With the tools installed, you can create migrations with dotnet ef migrations add <migration name> and dotnet ef database update to apply the migrations to the db schema.
Class libraries (where DbContext and models are defined in class library) are not supported yet. There is a workaround in the Entity Framework Core docs though.
For scaffolding the usage is dotnet ef dbcontext scaffold [arguments] [options]. See the Scaffolding docs for details.
I’m new to vs2010 and the entity framework (and ASP.NET MVC as well....I’m from a winforms vs2005 background) as well as the azure platform and am starting a project using these technologies soon.
I’ve installed vs2010 and the windows azure sdk kit for vs2010 and am running through this tutorial, Deploying an ASP.NET Web Application to a Windows Azure Cloud Service and SQL Database.
http://www.windowsazure.com/en-us/develop/net/tutorials/cloud-service-with-sql-database/
I’ve got as far as the ‘Add SQL support’ section, followed the instructions and when I compile and run no database is being created.
And I’m using sql server 2008 r2.
Any ideas why this is the case? Nothing at all is being shown in the sql server log. My connection details look fine, am I missing some kind of add on or some permission settings need changing?
Cheers,
I've sorted this myself. If you wish to know the answers I've posted them in the comments on the tutorial page, just follow the link (names Mathew in the comments section).
http://www.windowsazure.com/en-us/develop/net/tutorials/cloud-service-with-sql-database/