I never found a resolution and am not able to share my whole project. So I'm working through the other direction, starting with a 10.3 codebase and re-applying all of my application code to that. Not a small effort. But otherwise I'm frozen on an older version if I can't load the proxies.
No errors in the log file.
If I watch the Network tab of the browser, all of the resources load correctly, except for GetAll. The call to GetAll just never returns.
What is your product version?
What is your product type (Angular or MVC)?
What is product framework type (.net framework or .net core)?
What is ABP Framework version?
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.
Awesome. Thank you!
I don't know why that didn't occur to me. But it's working great.
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!
I'm still unable to get this resolved. My application is deployed for the enterprise now. And it's fully functional, with two major exceptions that I've identified:
I can't impersonate users. Trying to impersonate a user takes me to the 500 error page. There's literally nothing in the logs, other than the startup event. Nothing at all in the log4net logs. And after I do this, I'm logged out. Again, this works in production and staging (where I have one server each), but not in production, where I have multiple servers.
**I'm unable to delete a role or to edit permissions on a user.**I can create a role and edit permissions there. But if I try to delete a role, or to edit permissions on a user directly, it says I'm not authorized. I'm logged in as Admin with full rights. Again, this is not an issue in dev or staging, just production.
Any thoughts?
Brilliant! Works great! Thank you so much!
ASP.NET Zero is a great framework. But the community is equally great.
For any one reading this message later, make sure you authorize your client IP address to Azure SQL Database before you do this.
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?
Thank you for all of your help.
At this point, I think it's coming down to the fact that the address I'm putting in the appsettings file is a domain name that can't be resolved locally on the machine. It can only be resolved externally. That works fine for most things, but not for these few features.
I tried putting the load-balanced internal IP address of the servers in the file. But then, when I do a rights assignment or an impersonation, that IP address ends up in the address bar of my browser, which, of course, can't resolve it externally.
I think my solution is to add the domain name to the DNS table on the machines so that it can be resolved locally on the machines. But I'll have to setup a set of test servers to try that. That's probably a weekend project. I'll let you know if it works!
Thanks again!
Asp.net core with jQuery
