Module Creator Doesn't Complete #884
-
I was very excited to learn about Oqtane from Shaun's .netConf 2020 talk, and would like to use it on the next project starting next week. I downloaded it from git, ran it in VS 2019 Community, installed db in setup, and created a common module by following the YouTube video series. I'm now trying to create a Developer Module using the Module Creator. I enter in the Owner Name/Module Name/Desc/External Template, location was good, then clicked Create Module. It created most of the files in the directory, but my browser shows a ERR_CONNECTION_RESET partway through. I opened the .sln file and see that the Add.razor and View.razor files are missing from the Client folder, as well as several in the root of the parent folder (only .sln file exists). I have turned off my firewall, do not use a proxy. I use Windows 10 and it's up to date. I have the latest VS 2019, installed latest .net 5 SDK and hosting exe's, installed latest SQL 2019. I have tried (IISExpress) in debug mode, started without debug, and chose to run under Oqtane.Server to see the command prompt. I tried with the Brave browser and Chrome (both up to date). During the module creation process, the server just shuts down. I have seen the links to the module template files to download, but I would like to use this model since it's fast and convenient. It's likely operator error or environment, but if I ran into it while following the videos, someone else must also be running into it. Any help would be appreciated. Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 26 replies
-
Did you try creating an internal or external module? |
Beta Was this translation helpful? Give feedback.
-
No there is no Add and View razor file. Just Index and Edit razor files. The Edit component can handle Adds and Edits though. The root folder should just have the solution (*.sln file) and the four project folders. Client, Package, Server and Shared. |
Beta Was this translation helpful? Give feedback.
-
I've recorded a video of the full experience here: https://www.dropbox.com/s/kwekuxh2d5drnpe/2020-11-15_08-51-42.mp4?dl=0 |
Beta Was this translation helpful? Give feedback.
-
The reason why the framework forces a server restart is because Oqtane relies on logic which executes during application startup to discover modules/themes and load them into the AppDomain - so if the application was not restarted, the module which was created using the Module Creator would never be activated. One thing I have noticed is that when people see the ERR_CONNECTION_RESET behavior they immediately assume that something went wrong. This behavior only happens when running on Blazor Server - and @jimspillane is correct that there is so far no technical solution to allow the application to recover when you force a server restart. One question I have is if it may be a better user experience in those areas of the framework which require a restart ( ie. module/theme creation, installation, deletion ) to not force the restart at that moment, but instead include a message to the user that the application needs to be restarted for the changes to take effect. We could include an option in one of the Admin UIs to allow a host user to manually force a restart the application. The benefit of this approach is that it puts the user in control of when the restart happens. It also consolidates restarts to a single deliberate area of the framework. And in the case where you are running Oqtane from Visual Studio you do not even need the manual option - you simply need to stop your debugging session and then run the app again. The downside is that if a user does not read the message displayed in the UI or understand that a restart is required, they may assume the framework is broken when their action does not provide their expected result immediately. Thoughts? |
Beta Was this translation helpful? Give feedback.
I've recorded a video of the full experience here: https://www.dropbox.com/s/kwekuxh2d5drnpe/2020-11-15_08-51-42.mp4?dl=0