[DevExpress Support Team: CLONED FROM T674277: CodeRush v.18.1.11 NGEN window does not appear in my VS]
I removed the xml file again and restarted VS. I chose the always NGen option (the middle one) and waited patiently for the NGen Icon to process the files.
Then, I restarted VS once again. This time only 8 dll where native.
I'm about to give up. I spent to much time trying to make this feature work. It has been frustrating.
When you have a version that works all the time I will try again.
Thanks for you support.
Eduardo Quintan
Eduardo,
We appreciate the time and efforts you have spent to help us make this feature better!
Let me explain the NGen process in detail:
Based on your log files, the NGen process doesn't cause any errors, however it seems that the files are not complete. It's possible that you have collected the logs while the native image compilation wasn't finished. Also, the number of native images loaded in your environment differs from the expected number (as it shown in our tests and this is confirmed by Alex in the original ticket). It makes us think that there are some additional dependencies in your environment we are not aware of.
We have improved our routines to collect more information about dependencies and are going to release the update shortly. If you don't want to wait for the update and can invest some of your time, you can try this build (using instructions from the original ticket):
http://downloads.devexpress.com/Share/IDE/180924/DevExpress.CodeRush.Roslyn-18.1.11.18267.exe
We will be happy to hear your feedback.
Hi Alex,
I did as you asked me to, and the result is a little more promessing, for the number of NGen'd libraries increased. See attached image (Incidentally, I would like to ask you to allow users to past images here, as you can do from your side. This would make life easier! And, also, the ability to add more than one file to each posting.).
One thing I have notice though is that the NGen icon on the system tray icons is kind of completing as the NGen process is progressing, but it stopped in the middle with a little more than half of if filled with white. I am supposing this is how it works. If it is so, maybe this info will help your understand what is going on. Also, I am posting a WinRar file with the logging files from this flight.
Eduardo Quintana
The second attachment required this new posting.
The previous CodeRush NGen feature processed 5 files. This new one processed 18. A good improvement, so far.
Eduardo Quintana
Hi Eduardo,
Usually the NGen process takes about 10 minutes to complete. In your log file I see that the entire process takes about 6.30 minutes and is not completed yet. Please wait until it finishes - the process indicator in the taskbar displays the current progress. The filled out part displays the current progress and the rotating part shows that actions are in progress and the NGenInstaller tool doesn't hang:
https://www.screencast.com/t/EQspLC54E
While the filled out part can be changed slowly (because some assemblies require more time to be compiled), the rotating indicator should move constantly as you can see in the screencast. Are you sure that the NGenInstaller tool hangs on your side? Can you please post the NGenInstaller log and the current state of loaded CodeRush assemblies (just restart VS to make sure that the latest native images are loaded) ? I hope that it has passed enough time from your previous post and the NGen process has been completed.
Him Alex,
I waited until the icon disappeared from the System Tray Icons area.
But I will repeat the process and keep an eye on the process using the Process Explorer application.
I will post the result here in minutes.
Eduardo Quintana
Interesting: this time I deleted the XML file, as instructed, and restarted VS (twice already) and started doing some editing in a solution, but the option to NGen did not appear!
Note that I always execute VS in Admin mode.
Eduardo Quintna
Eduardo,
We have checks that prevents running NGen if CR assemblies are loaded from the native images. Please share existing NGenInstaller log files (there is no necessity to run the tool) and screenshots (or screencast) from Process Explorer showing CR assemblies loaded in the devenv process. Please show the entire list of DevExpress* assemblies (it can require using the scrollbar in the Process Explorer window) so we can see if each assembly is loaded from native images. Here is an illustrating screencast:
https://www.screencast.com/t/bbMxLZgSfuQ
The last NGen install log was posted here 2 hours ago (NGenInstaller 2018-09-24 09.41.18.rar)…
The list of all assemblies, a very long one, is attached.
Please let me know if you need anything else.
I am leaving for lunch now, but will be back in about an hour.
Eduardo Quintana
Eduardo,
Thank you for the provided log files. We will soon prepare a new build for you to try out. Please give us some time.
Hi,
I have installed the new CodeRush 18.1.12 and the option to NGen the dlls appeared again in my VS.
I executed it and the process stopped amid again. Please see the images in the attached file.
The NGen installation log is also in the same compressed file, as is the list of CodeRush DLLs that are native now (only seven!).
Eduardo Quintana
Eduardo,
We have examined the log files you provided. They show that most likely the ngen process failed for some reason and not all assemblies were compiled as native.
We are still working on a new build for you. We are adding several changes to the ngen code to be more stable and we will also add additional logging to better understand the issue.
Thank you for your patience. We greatly appreciate your help. Please give us some time.
Eduardo,
We have prepared a special build containing additional logging and changes to avoid hanging:
http://downloads.devexpress.com/Share/IDE/180927/DevExpress.CodeRush.Roslyn-18.1.12.18270.vsix
Please perform previously mentioned steps and share your log files. Note that the NGenInstaller tool can take much time to complete (about an hour, but all work is done in background and shouldn't impact the performance). So please collect logs only after the tool finishes its execution. We hope that log files will shed some light on the reason of the issue. Thank your for your cooperation!
Thanks Alex.
Some questions:
Can I close VS while the NGen is running?
Or continue to use it to develop my applications?
Or even load another solution?
Or, do I have to wait and do not touch VS while the tool is running?
Eduardo Quintana
Eduardo,
Since the native image compilation is done in a separate process (NGenInstaller.exe), you can continue your work with Visual Studio without any limitation - continue working with your solution, load other projects, close VS, run new VS instances. It's not recommended only to shut down the PC while NGenInstaller is still working.