Activities of "sh0knah"

• What is your product version?

  • 10.1

• What is your product type (Angular or MVC)?

  • MVC

• What is product framework type (.net framework or .net core)?

  • .NET Core

• What is ABP Framework version?

  • 6.2.0

Upgraded nuget and js library references, .NET framework version, etc. Got the project building.

On startup, the login page comes up correctly. On the Network tab in the browser, everything looks like it's loading correctly, except the call to abpserviceproxies/getall. That call never returns and spins the CPU up really high. Obviously, that breaks most functionality beyond the login screen.

On researching the issue, I found references to similar issues caused by System.Type parameters in the AppService interfaces. Verified that I have no Type parameters in my AppServices.

I also found references to issues caused by return types like IQueryable. I did have a couple of those and commented them out to see if that would resolve the issue. It did not.

I attributed all IApplicationService-derived interfaces with [RemoteService(IsEnabled = false)] to try to eliminate the issue, planning to bring interfaces back in slowly until I identifed the problematic interface. With all interfaces excluded, I get the same behavior--abpserviceproxies/getall never returns.

Thinking that maybe the complete lack of interfaces may cause a problem, I re-introduced a single, very simple IApplicationService-derived interface (1 method, simple parameter types). Same problem.

Where else can I look for a cause on this? I can reproduce it on all development machines on my team, Windows and MacOS.

I'm stumped. Any help would be much appreciated.

I need to be able to set the JobId when I schedule a one-time or recurring job. I'm allowing users to schedule jobs and if they change the schedule or delete the job, I need to be able to update or remove the original job. (These could be reminders or scheduled reports, etc.)

Hangfire seems to support this with the following syntax:

RecurringJob.AddOrUpdate("some-id", () => Console.WriteLine(), Cron.Hourly);

I'd be happy to use the Hangfire API directly, if someone could point me to some information on how to reference it in AspNetZero. I've completed the Hangfire integration steps. I can create Background Jobs through the ABP interface. And I can access the Hangfire dashboard and follow the progress of my jobs, which are all running correctly. But I don't know how to access the native Hangfire functionality so that I can set a JobId on a job.

Any help would be greatly appreciated. I can't seem to find anything on this anywhere, other than this one statement in the ABP Hangfire Integration document: "Thus, your code will be independent of Hangfire. But, if you like, you can directly use Hangfire's API also."

Thank you!

Looking for tips from anyone who has experience deploying to Azure.

I'm trying from just the raw application, without any customizations or modifications. It's working locally in a development environment. I use the Publish menu from the *.Web.Mvc project.

I can push it successfully to my Azure account.

Once I have everything connected and configured properly on Azure, I fire up the application and I get the "No language defined in this application" message that I would expect from an un-migrated instance.

Now I'm stuck.

There is no option to apply migrations with the Publish from Visual Studio 2017.

I can't apply it remotely from the Package-Manager Console. I get "The EntityFramework package is not installed on project '*.EntityFramework.'"

And I can't do it from the console in Azure. I run dotnet ef database update (or really any dotnet ef command) and I get "Unhandled Exception. Value cannot be null. Parameter name: Path."

So I don't have a way to migrate the database.

I'm not using a virtual machine, so I don't think I can just push Migrator out there.

I'm really trying to come up to speed on Azure. So I might just be missing something obvious.

Any ideas?

I have an application based on ASPNETZero. I run it in both my development and test environments and it works perfectly. When I deploy it my production environment, I lose certain functionality.

Critically to me right now, when I try to add a permission to a user, I get "You are not authorized." I'm logged in as the Admin user.

I also can't Impersonate users. I get a 500 error. Again, this is something that works correctly in both the development and test environments.

I've tried with and without a Redis server. That doesn't seem to make any difference.

Differences between test and production:

• The test systems are all single-server. Projection in multi-server.
• The production server is running https. I've run it that way in development and it seems to work fine.

Any ideas why this isn't working? I've spent way too many hours trying to figure it out.

This is a beautiful framework. But I can't go to production until I resolve this important issue.

Thank you for any help you can provide!