Intellisense stops working when method signature contains optional parameter - by kzu

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


2
0
Sign in
to vote
ID 780724 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 3/5/2013 12:39:57 PM
Access Restriction Public

Description

Generic methods that leverage the generic parameters to specify the types of expressions/lambdas received as parameters, typically work great (i.e. fluent APIs that exist everywhere) and infer the types of the lambdas and provide great intellisense.

This stops working completely when the generic method has optional parameters, though, as we just discovered :(
Sign in to post a comment.
Posted by Bill [MSFT] on 4/16/2013 at 9:34 AM
Hi, DanielKzu. Thanks for letting us know about this. While we do not currently have plans to address this issue in the next release of Visual Studio, we do plan to fix it in Roslyn, which is our long-lead effort to rebuild the C# and VB editing experiences from the ground up. When Roslyn eventually becomes part of Visual Studio, you should see this issue corrected. We have not determined when that will be, but it is on our roadmap.
Posted by Microsoft on 3/12/2013 at 11:38 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Helen [MSFT] on 3/5/2013 at 12:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(http://support.microsoft.com)