Invalid ObjectName

[asreid212]

Invalid ObjectName

[asreid212]

Forgot to add, I am connecting to SQL Server 2012. Thanks

[JonPSmith]

I haven't tested the SQL side for a while so there may well be a problem. I'm on a contract at the moment so I will look at it at the weekend.

[JonPSmith]

I tried the following:

1. I made sure I didn't have a database called PermissionAccessControl2-AspNetCoreIdentity and PermissionAccessControl2-DemoDatabase so that I was starting from stratch.
2. I just changed the appsettings to

{
  ... other parts left out
  "DemoSetup": {
    "DatabaseSetup": "Permanent", 
    "UpdateCookieOnChange": true //this doesn't matter.
  }

And when I ran the the application it started OK. I then stopped the application and ran it again - it was fine. So I don't see your error.

Can you tell me about your PermissionAccessControl2-DemoDatabase. Is it old, or have your tried to swap over to migrations (which wouldn't work without changes). If its not that then I don't know what it is.

Let me know.

[JonPSmith]

PS. I have been cleaning things up and found there were some changes to the database schema between the first version (Part 3) and the latest (Part 6). Therefore if you ran a early copy of PermissionAccessControl2 your database schema might be out of date to the current version.

[asreid212]

Hi Jon, Thanks for taking the time to look at this, I really appreciate it. I clicked the link in the part 3 article to go to the repository, and not any links in part 6 as I did not get that far (I have since read them all). I would assume the redirect would take me to the same version, but to be safe, I will go directly to GitHub and download from there and try again. If I understand this correctly, the 1st connection should just be pointed to the Aspnet DB that was created @ runtime. The 2nd DB is the database I want to use identity on, meaning I don’t have to create any objects in it other than what’s there (no identity is setup on the 2nd DB). I have been working over the last year to get data cleaned up and organized into a DW and I have been slowly working on the creation of the front end. I am naturally a SQL/data guy, and use PowerShell for pretty much all of my ETL as I dislike SSIS in ways the world can never understand. Do I have it wrong, should the 2nd DB in your example always be in-memory and then create another connection string for the production DB that has all of the data I need to perform CRUD on and the 2nd connection in your example is just a temporary housing repository? T The most trying part of the front-end was choosing between asp.net MVC and asp.net CORE and then after making that decision, the learning process as articles and examples/tutorials quickly go out of date as it jumped from core 2.0 to 2.1, 2.2.0, 2.2.1 and now 3, I felt smart until I ventured down this path LOL; I am just used to SQL/PowerShell and generally things don’t really ever change, and definitely not that fast. I decided to go with core as it seems to be the best solution (even though it will be hosted on windows), the performance seems to be far superior. I have stumbled through this when I have time to work on it, but now the pressure is on to produce, and security has been the one thing I have been slow to decide how to do until I found your article (it is exactly how I envisioned it should be!). I saw that you have a book out as well, and I want to purchase, is it still relevant, as I know things have changed so much over the different core releases, I assume the same is happening for entity framework. One last thought if you don’t mind, I am using jqgrid. I am able to populate the grid just fine and post back to my edit url in my project, but what I still am having a hard time understanding, is why do I have to bring every column down from the table and the send an update for every column. In my startup, I am serializing my context to JSON. I came across your article that discusses your generic library that would allow me to just post back what I want to update, and was like yes, this is what I want as I think it’s a huge waste of resources and a drag on performance to pulling and pushing data that is not needed. My question is, if I install your generic library, would it be able to work ok since I have my connection serialized in the startup, or do I need to remove that, and then just serialize in my controller to be able to use the library? I really appreciate the help and your thoughts on everything, I know you are busy and answering these questions is probably the last thing you want to do. Thanks! From: Jon P Smith <[email protected]> Sent: Saturday, September 21, 2019 9:10 AM To: JonPSmith/PermissionAccessControl2 <[email protected]> Cc: asreid212 <[email protected]>; Author <[email protected]> Subject: Re: [JonPSmith/PermissionAccessControl2] Invalid ObjectName (#4) PS. I have been cleaning things up and found there were some changes to the database schema between the first version (Part 3) and the latest (Part 6). Therefore if you ran a early copy of PermissionAccessControl2 your database schema might be out of date to the current version. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#4?email_source=notifications&email_token=AFHZW22DJIDT5YLHHESCFDDQKYTNDA5CNFSM4IXU7RVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7ISQII#issuecomment-533800993> , or mute the thread <https://github.com/notifications/unsubscribe-auth/AFHZW263R75IYNFLHNGCA7DQKYTNDANCNFSM4IXU7RVA> . <https://github.com/notifications/beacon/AFHZW22LNWBGAE6OQEE2DR3QKYTNDA5CNFSM4IXU7RVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7ISQII.gif>

[JonPSmith]

Wow, a long answer. Here are my (short) answers.

I updated the PermissionAccessControl2 software as I created the new articles, so the version in master has everything in it. That was easier to me, but does make it harder for people to pick out the simple stuff. I'm working on a new release with code for each article/approach. Should have a article out in a few weeks which should help you and other people (I'm working on a contract so limited time at the moment).

There are two databases:

• Standard ASP.NET Core Identity database
• A single database that I split across to DbContexts, so people can see the two parts):
  • The extra authorisation classes (see 'ExtraAuthorizeDbContext`)
  • An example multi-tenant application (see CompanyDbContext)

This second database is created via the CombinedDbContext using context.Database.EnsureCreated in the startup code (see program.cs), which is a cheat way to do it (that's only really used in unit testing).

In a real application you would need some form of migration. I'm with you - I use SQL scripts for migrations and I have a tool called EfSchemaCompare that checks my migration matches what EF Core thinks it should be.

GenericServices - there are example applications showing how to use GenericServices with Razor Pages, MVC and Web APIs. It picks up the DbContext via dependency injection.

[JonPSmith]

Hi @asreid212,

Quick update that might help you.

To help developers like you I released a major overhaul of the PermissionAccessControl2 repo over the weekend (make sure to pull the changes) and posted a new article called Part 7 – Adding the “better ASP.NET Core authorization” code into your app. In the article I show how to build a new ASP.NET Core app by copying in code from PermissionAccessControl2 into your ASP.NET Core app.

NOTE: The PermissionsOnlyApp uses EF Core Migrations and applies any outstanding migrations on startup - that isn't the best way to add migrations (and I don't use EF Core migrations myself), but it makes it easier for people to run the app to see what it does.

I hope that helps you.

[asreid212]

Jon, Thank you, this was much appreciated and breaking it out into separate projects really helped. One side note, I think some may have issues if they start from a 3.0 project and I believe a 2.1 netstandard because of ef core 2.2.6 (remembering believe that's the version you use) because it wants you to move to ef core 3 along with all the other references. It will also force people to use end point routing in startup unless you force it to false. Unit testing will also break and users need to remove some references of razor and aspnet core in the projects. Not a big deal, but want to throw it out there that the netstandard can become an issue for some if they don't pay attention and start doing updates or start from a project with 2.1 Thanks for everything! Get Outlook for Android<https://aka.ms/ghei36>

…

________________________________ From: Jon P Smith <[email protected]> Sent: Tuesday, October 1, 2019 10:46:24 AM To: JonPSmith/PermissionAccessControl2 <[email protected]> Cc: asreid212 <[email protected]>; Mention <[email protected]> Subject: Re: [JonPSmith/PermissionAccessControl2] Invalid ObjectName (#4) Hi @asreid212<https://github.com/asreid212>, Quick update that might help you. To help developers like you I released a major overhaul of the PermissionAccessControl2 repo over the weekend (make sure to pull the changes) and posted a new article called Part 7 – Adding the “better ASP.NET Core authorization” code into your app<https://www.thereformedprogrammer.net/part-7-adding-the-better-asp-net-core-authorization-code-into-your-app/>. In the article I show how to build a new ASP.NET Core app by copying in code from PermissionAccessControl2 into your ASP.NET Core app. NOTE: The PermissionsOnlyApp uses EF Core Migrations and applies any outstanding migrations on startup - that isn't the best way to add migrations (and I don't use EF Core migrations myself), but it makes it easier for people to run the app to see what it does. I hope that helps you. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#4?email_source=notifications&email_token=AFHZW26UC5ILWFWTMLPETYTQMMTABA5CNFSM4IXU7RVKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAA2TDQ#issuecomment-536979854>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFHZW25JXITQJ6R3KBIJ2RTQMMTABANCNFSM4IXU7RVA>.