I played around with a new feature added to the RAD tool to point to a different DB / table. However been having issues wtih this. This is a feature I desperately need. Also the ability to generate UI from existing tables (in any DB) would also be powerful and helpful.
Initially when I pointed to a different DB and table it tried to generate it into the current selected DB?! I don't really understand this.
Now it just hangs after I entered the connection string (maybe from a recent update?). I have to manually kill Visual Studio after many hours hanging / busy. Would have also been better if the connection string selector rather showed the connection string names as set up in the Appsettings.config file under ConnectionStrings, than entering the connection string manually (that gets saved where?).
I had issues pointing to a different DB trying to use dependency injection of Aspnet Zero / .NET Core. In the end I had to manually create the other DB context everywhere I want to use it without using dependency injection in the Aspnet Zero project... The same type of dependency injection to my other DB works perfectly in any other .NET Core project, but not in the Aspnet Zero Host project.
1 Answer(s)
-
0
I think you've misunderstood that feature.
when I pointed to a different DB and table it tried to generate it into the current selected DB?!
That's the point of the "Load entity from database" feature. It is for speeding up the process of moving an old project to a new asp.net zero based project.
Also the ability to generate UI from existing tables (in any DB) would also be powerful and helpful.
Actually this is the "Load entity from database" feature we are talking about.
Would have also been better if the connection string selector rather showed the connection string names as set up in the Appsettings.config file under ConnectionStrings, than entering the connection string manually.
Because of some strong reasons, you should not generate a new entity from asp.net zero based application's own database.
Now it just hangs after I entered the connection string (maybe from a recent update?). I have to manually kill Visual Studio after many hours hanging / busy.
What is your extension version? Could you provide any more steps to reproduce this issue?
