Super slow debugging of ASP.NET 5 applications. Takes 2 minutes to start

Question

I noticed trying to debug an asp.net 5 application in fabric is extremely slow.

I looked at the build logs and I think it is just doing redundant steps.

Here are the steps i found

1. dnu pack <- Why pack? Doesn't look like the packed file is used. You can shave off a few seconds from removing this step
2. dnu publish <- Copies all files needed to run to a temp folder. If temp folder exists, delete first
3. msdeploy <- Runs a file system msdeploy into another temp folder. If temp folder exists, delete first. Why are you guys even doing this step? It seems very redundant to me
4. "pack" <- copies files back into pkg\Debug folder
5. Deploy pkg\Debug to fabric

It looks like there is massive copying of files again and again which does not do anything. I believe step 3 can be removed and we can do a dnu publish directly into pkg/Debug. That will probably shave off 30-60 seconds off deployment time

Answer 1

Jin,

Yes, you are correct. There are several steps required to initiate debugging for ASP.NET 5 apps. The ASP.NET team are aware of this and as ASP.NET and Service Fabric move towards GA, we certainly intend to improve this. I would suggest that you post feedback on the user voice forum here to allow others to vote.

https://feedback.azure.com/forums/293901-service-fabric

Thanks

---

Lead Program Manager, Microsoft

Answer 2

Already did that here. -> https://feedback.azure.com/forums/293901-service-fabric/suggestions/10777620-improve-deployment-speed-for-asp-net-5-projects

Any quick fixes that I can do now to improve the debugging speed?