PCL Reference In a Workflow Project Destroys Intellisense - by Drew Marsh

Status : 

  By Design<br /><br />
		The product team believes this item works according to its intended design.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 800070 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 9/9/2013 6:07:30 PM
Access Restriction Public


Referencing a Portable Class Library (PCL) assembly from a Windows Workflow project results in loss of Intellisense on what appears to be all other assembly type data except from mscorlib.dll, including project referenced assemblies.

NOTE: this is a bug in VS2012 as well.
Sign in to post a comment.
Posted by Microsoft on 9/20/2013 at 1:23 PM
Thank you for reporting this issue. We are currently gathering feedback for the next version of Visual Studio and will add this item to the backlog of features we consider in our product planning.
Posted by Microsoft on 9/10/2013 at 6:21 AM
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 Microsoft on 9/9/2013 at 6: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)