Still very new to service fabric but I'm surprised that something as advanced as this is so slow to debug. I'm using a fairly fast machine but it takes 4-5 minutes to tear down and restart the cluster. I've googled it and can't see that anyone else has reported this as being a show stopper.
service fabric slow development cycle
2.3k Views Asked by user3688632 At
2
There are 2 best solutions below
2
On
Yes, we have the same issue, we have around 10 services in our application and debugging is very slow, VS fails to refresh 1 node cluster all the time, so cluster reset is only solution. So every debug run takes about 5 minutes.
Yes, very disappointment development process, the only advantage is some reuse of C# code, if you have not decided what to use for your cloud solution, abandon C# as early as possible. Go for any JST based language having no intermediate binaries.
Some clues to help with your slow development turnaround time:
When developing locally, consider using a One-node cluster in order to speed-up deployments and upgrades (less Upgrade/Fault Domains): https://learn.microsoft.com/en-us/azure/service-fabric/service-fabric-get-started-with-a-local-cluster#one-node-and-five-node-cluster-mode
You need to setup/create your cluster once and than start it and keep it running between debugging sessions, Visual Studio will take care of uninstalling/upgrading the SF Apps when starting the debugger.
You can modify the properties of the SF Application project to decide if your SF App will be uninstalled and install or upgraded when starting the debugger, which impacts the deployment time.
Consider running from a SSD drive which will speed up compilation and deployment (file intensive).
Expect less than one minute to compile, deploy and attach debugger for a SF App with 2-3 services.