0
 Followers
8
 Likes

Solution publish should fail early

Service Center
New

When there is an error, like missing reference, at the beginning of solution publish - it still continues to go for half an hour or more, and only after "Gathering dependencies..." stage it fails with a message like "The deployment was aborted due to errors. No applications or modules were deployed".

This is really really really frustrating, especially when you are in a hurry, especially when you have noticed the error and fixed it, but you still have to wait for half an hour because there is no way to stop solution publish.

Why would it not stop immediately after the fatal error has occurred? Or at least show  that "continue/abort" confirmation, immediately.

Isn't this rule #2 from The Book?

Created on 14 Feb
Comments (1)

Changed the category to Service Center


views
59
Followers
0