Current filter:
                                You should refresh the page.
                                Show all comments
                                • Eduardo Quintana 09.19.2018

                                  Detail: I always execute VS as Administrator, by default.

                                  Eduardo Quinana

                                • Alex Miller 09.19.2018

                                  Same here. I do not see the option. Admin mode... CodeRush 18.1.11 on VS 15.8.4.

                                • Dmitry O (DevExpress) 09.20.2018

                                  Hello,

                                  Thank for you notifying us of the problem.
                                  We have reproduced the same problem on our side and will try to fix it shortly.

                                  To make sure that we are fixing exactly the problem you faced, could you provide us with your CodeRush settings folder: "CodeRush->Support->Settings Folder..." and with the CodeRush log files folder: "CodeRush->Support->CodeRush Logs...".

                                  I am looking forward to receiving data from you.

                                • Eduardo Quintana 09.20.2018

                                  The requested files are in the attached file, compressed with WinRar and in the selfextracting form.

                                  Eduardo Quintana

                                • Eduardo Quintana 09.20.2018

                                  After I changed the setting as explained in the T674303 issue, and restarted Visual Studio, the window showing the NGEN optons appeared and I chose the middle one (run NGEN every time a new CodeRush version is installed).

                                  I do not know if there is any connection between the two problems, but, it now worked as expected now.
                                  I will observe the VS starting time from now on, to see if the NGEN was really executed and is impacting positively the VS startup time.

                                  I hope this info helps you with the problem solution.

                                  Thanks for your support.

                                  Eduardo Quintana

                                • Dmitry O (DevExpress) 09.20.2018

                                  Thank you for providing us with log-files and settings.

                                  I am happy to hear that the NGen hint appeared on your side. We have analyzed all the information from you and reproduced such a problem on our side.
                                  We will try to fix the problem as soon as possible and notify you about our progress in the context of the current ticket.

                                • Eduardo Quintana 09.20.2018

                                  Thanks, I will be waiting for a correction.

                                  Meanwhile, I would like to know how to I do to verify that the NGEN has been run in my computer?

                                  Eduardo Quintana

                                • Dmitry O (DevExpress) 09.20.2018

                                  As far as I understand you want to see whether CodeRush assemblies loaded via NGen in Visual Studio?
                                  If so, you can check this with help of Process Explorer, for this perform the following steps:

                                  1. Download the Process Explorer by the following link - Process Explorer.
                                  2. Run procexp.exe/procexp64.exe (depending on your OS) as Administrator.
                                  3. Find you Visual Studio process and check which .Net assemblies were loaded from NativeImages. I have recorded the screencastwith the checks on my side.

                                  Note: NGen can process assemblies for a long time and not all DevExpress.CodeRush.* assemblies can be processed on NGen and thus shown in a list of the Process Explorer. But we will do our best to improve the NGen processing in our future updates.

                                • Eduardo Quintana 09.20.2018

                                  Apparently, it did not happen. See attached image, please.

                                  Is there a way to ensure that the NGEN is really used by CodeRush?

                                  Eduardo Quintana

                                • Alex Miller 09.20.2018

                                  Here's my log and settings. Enabling the image paste worked, but it didn't fix the no-ngen warning.

                                • Alex Miller 09.21.2018

                                  This morning I was greeted in VS with the CR NGen banner. Now I see a little 'CodeRush Ngen Installer' icon working in the notification area.... seems it is working!

                                • Eduardo Quintana 09.21.2018

                                  I would suggest you check the DLLs, as described by Dmitry above, for the same thing happened to me, but the NGEN was never not executed.

                                  Eduardo Quintana

                                • Alex Miller 09.21.2018

                                  You are right. After the notification finished, process explorer showed only DomainNeutral assemblies. I closed and restarted VS and now everything seems perfect.

                                • Eduardo Quintana 09.21.2018

                                  Not here!

                                • Eduardo Quintana 09.21.2018

                                  I use VS 2017 Enterprise 158.5, and CodeRush Ultimate v18.1.11.

                                  Now, when I execute VS no option appears to NGEN its libraries.

                                  Eduardo Quintana

                                • Alex Miller 09.21.2018

                                  Maybe... try running this manually as admin...
                                  "C:\Users\alexa\AppData\Local\Microsoft\VisualStudio\15.0_37926244\Extensions\yyp0uvsv.j5i\NGenInstaller.exe"

                                • Alex Miller 09.21.2018

                                  In VS CodeRush\Support\ExtensionFolder->NGenInstaller.exe 

                                • Eduardo Quintana 09.21.2018

                                  I could not find the referred dir under my user, but I ran the NGenInstaller.exe.
                                  It took some minutes to complete, and now the DLLs started to be NGen'ed.

                                  Thanks for your help.

                                  Incidentally, I have a program I developed to automatically update all the DXperience Suite localization libraries, including the ones in the compiled projects. Should you like to get a complimentary copy, just let me know.

                                  Regards,

                                  Eduardo Quintana

                                • Eduardo Quintana 09.21.2018

                                  I would like to know if the only CodeRush DLLs that get NGen'ed are the five ones in the attached image, or did I miss something here?

                                  Eduardo Quintana

                                • Alex Eg (DevExpress) 09.21.2018

                                  Hi guys,
                                  We have analyzed your log files and it seems that the reason for the issue was the same - we can't correctly create a list of dependent assemblies for NGen. For some reason, one of the dependent assemblies - System.Composition.AttributedModel was not loaded in Visual Studio at the moment we collect dependencies for NGen and so the information banner was not shown as expected. We have changed the way we collect such dependencies and it works correctly in our tests. Also, we have added an additional logging so we can get more information if something goes wrong. Please perform these actions if the NGen process was incomplete or not displayed at all and you want to test a new build:

                                  1. Install the http://downloads.devexpress.com/Share/IDE/180921/DevExpress.CodeRush.Roslyn-18.1.11.18264.exe hotfix build
                                  2. Open the Options folder(CodeRush\Support\Settings Folder) and delete the .xml file in the folder root(if it exists) - it contains information about the previous NGen process:
                                  https://www.screencast.com/t/u5EW64a6
                                  3. Restart VS, open a project and make some changes - suggestion to NGen assemblies should be displayed shortly.
                                  4. After the NGenInstaller tool execution is finished, please restart VS so native images will be loaded.
                                  To check if CodeRush assemblies are loaded from the native images cache, please refer to the method Dmitry already described.
                                  Please note, that not all of CR assemblies will be loaded from the native images cache now and the exact list may be different on different machines. This screencast shows the list on our test machines:
                                  https://www.screencast.com/t/BpHnJNda2SI
                                  We will continue to work to improve it in future updates.
                                  Please inform us about your results.
                                  P.S.
                                  Running the NGenInstaller tool manually is not suggested because the NGen process wouldn't have the full dependencies list and the compiling process can be incorrect.
                                • Alex Miller 09.21.2018

                                  Hi Alex,

                                  I followed your instructions and everything worked perfectly.

                                  Thanks for the quickfix.

                                  Alex

                                • Eduardo Quintana 09.21.2018

                                  Hi Alex,

                                  I followed the procedure you described and now, alas, no dll is native!

                                • Eduardo Quintana 09.21.2018

                                  The logs dir is attached.

                                • Eduardo Quintana 09.21.2018

                                  I restarted VS several times, for other reasons, but only 10 DLL are native so far. It has been some time since I have followed your procedure, so I dont'  think this number will increase any time soon.

                                  Eduardo Quintana

                                • Eduardo Quintana 09.21.2018

                                  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

                                • Alex Eg (DevExpress) 09.24.2018

                                  Hello Eduardo,
                                  Since the original issue is resolved and the suggestion to use NGen is shown as expected now, I've created a separate ticket on your behalf (CodeRush assemblies cannot be loaded from native images after NGen). It has been placed in our processing queue and will be answered shortly.

                                2 Solutions

                                Creation Date Importance Sort by

                                Fixed:

                                Alex, Eduardo,
                                Thank you for your feedback on the hotfix. Since the suggestion to compile native images is shown now, we will mark this issue as fixed. We will continue working on this feature and improve the number of assemblies, which are loading from the native images.

                                • Eduardo Quintana 09.24.2018

                                  Sorry, Alex, but this is really not the case.

                                  I tried to execute the NGen program called from the CodeRush menu, but it did not worked as expected. Only five dll are now native, despite all my efforts.

                                  I understand that this functionality is not working yet and needs a good review by DevExpress.

                                  I like your support and your products, so much so, that all the products I develop are 100% based on your DXperience suite, for more than a decade. But, I cannot agree that this functionality is working. It is not ready yet. Sorry.

                                  Eduardo Quintana

                                • Eduardo Quintana 09.24.2018

                                  Obviously, the DXperience Suite did not exit a decade ago, but I have been using DevExpress products (predecessors to the DXperience Suite) since 2001!

                                  I consider 5 DLLs processed an insignificant percentage of the CodeRush DLLs. Also, you showed in your blog site close to 90% of the CodeRush DLLs as native.

                                  Incidentally, I would like to ask you to send me a batch file to run the NGen on all CodeRush DLLs that support it. So I would be able to take advantage of this technology to speed up CodeRush in the VS.

                                  Thanks,

                                  Eduardo Quintana

                                • Alex Eg (DevExpress) 09.24.2018

                                  Eduardo,
                                  As I previously mentioned in my comment, I have registered the following ticket on your behalf to research the issue in detail:
                                  CodeRush assemblies cannot be loaded from native images after NGen
                                  Mixing two different issues in one ticket is not productive, so let's continue discussion there.