Looks like there is an update out now for this. The change log specifically mentions a fix for the issue when modifying a stored procedure.

https://msdn.microsoft.com/en-us/library/mt238290.aspx