Exception object in WCF service causes VS2012 to not generate reference.cs - by Phil Newell

Status : 

 


1
0
Sign in
to vote
ID 779627 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 2/20/2013 9:03:37 AM
Access Restriction Public

Description

I have a WCF service that was written in VS2010, it includes the following interface:

 [OperationContract]
 bool WriteToLog(Exception ex, gdAccountsPayable.LoggingLevels Log4NetLevel);

When I open the project in VS2012, I cannot refresh the service reference.  If I remove this inteface item, then the service references are generated correctly.

If I open the project in VS2010, the references are refreshed correctly.

What has changed in VS2012 to cause this bug?
Sign in to post a comment.
Posted by Microsoft on 3/27/2013 at 6:12 PM
Thanks Phil for reporting this. At this point, we have decided not to fix this as it is not a regression. Have you looked at this thread - http://stackoverflow.com/questions/4656257/using-custom-faultcontract-object-containing-system-exception-causes-add-servic for possible workarounds?
Thanks!
Posted by Microsoft on 2/22/2013 at 2:48 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 2/21/2013 at 1:52 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)