IMPORTANT!
This forum is now archived. Click here for the New Support Forum
Long debug start time
Quote from arjan on February 19, 2019, 3:27 pmHi,
Each time I start the application from visual studio within debug mode to test something it takes 1 minute 30 to start. This is due to Angular performing the entire compilation / build each time over and over again.
Most of the time I'm only making a minor change to see the effect or test if something is indeed resolved, but I do need to stop the application and start it again, waiting another 1:30 minutes.
Is there some way to speed up this proces? I already tried starting it with the command prompt with either ng server --aot and some other flags, but that does not change much. The development machine is running on SSD disks with a lot of RAM and CPU in place. This is killing my development speed, hope there is something to work a lot more efficient.
Hope to hear from you,
Best regards,
Arjan.
Hi,
Each time I start the application from visual studio within debug mode to test something it takes 1 minute 30 to start. This is due to Angular performing the entire compilation / build each time over and over again.
Most of the time I'm only making a minor change to see the effect or test if something is indeed resolved, but I do need to stop the application and start it again, waiting another 1:30 minutes.
Is there some way to speed up this proces? I already tried starting it with the command prompt with either ng server --aot and some other flags, but that does not change much. The development machine is running on SSD disks with a lot of RAM and CPU in place. This is killing my development speed, hope there is something to work a lot more efficient.
Hope to hear from you,
Best regards,
Arjan.
Quote from Eben Monney on February 26, 2019, 7:04 pmHello,
Try the following to see if it helps with your situation.
- Debug a fresh/blank copy of an angular project to see if the issue is related to specific components/configurations in your current project or its a generic issue. If its a generic issue you'll want to go through the below steps to try to speed up your development experience
- Test your project with "start without debugging" as this doesn't incur the cost of loading the debugger
- Disable "Enable JavaScript debugging for ASP.NET (Chrome and IE)" in Tools > Options > Debugging > General >
- Disable "Enable Diagnostic Tools while debugging in Tools → Options → Debugging"
- Disable "IntelliTrace, in Tools -> Options -> IntelliTrace
If this is specific to your project you might have to share your package.json and startup.cs files from your project.
You can send to support@ebenmonney.comRegards,
Eben Monney
Hello,
Try the following to see if it helps with your situation.
- Debug a fresh/blank copy of an angular project to see if the issue is related to specific components/configurations in your current project or its a generic issue. If its a generic issue you'll want to go through the below steps to try to speed up your development experience
- Test your project with "start without debugging" as this doesn't incur the cost of loading the debugger
- Disable "Enable JavaScript debugging for ASP.NET (Chrome and IE)" in Tools > Options > Debugging > General >
- Disable "Enable Diagnostic Tools while debugging in Tools → Options → Debugging"
- Disable "IntelliTrace, in Tools -> Options -> IntelliTrace
If this is specific to your project you might have to share your package.json and startup.cs files from your project.
You can send to support@ebenmonney.com
Regards,
Eben Monney
Quote from arjan on March 6, 2019, 6:47 pmThank you for your detailed reply Eben. It seems to be QuickApp related, other angular application start a lot quicker. We are just playing around with the QuickApp as is and only changed the URL and SQL Connectionstring within the startup configuration.
Thank you for your detailed reply Eben. It seems to be QuickApp related, other angular application start a lot quicker. We are just playing around with the QuickApp as is and only changed the URL and SQL Connectionstring within the startup configuration.
Quote from Eben Monney on March 7, 2019, 7:22 amWhat version of QuickApp do you use?
Can you send the same package you're testing with to support@ebenmonney.com for further testing?Regards,
Eben Monney
What version of QuickApp do you use?
Can you send the same package you're testing with to support@ebenmonney.com for further testing?
Regards,
Eben Monney
IMPORTANT!
This forum is now archived. Click here for the New Support Forum