Exception object in WCF service causes VS2012 to not generate reference.cs

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

Active

Type:	Bug
ID:	779627
Opened:	2/20/2013 9:03:37 AM
Access Restriction:	Public

Workaround(s)

view

User(s) can reproduce this bug

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?

Details (expand)

Visual Studio 2012

Create WCF service with two functions:includes an Exception object.

[OperationContract]
bool WriteMsgToLog(string msg, gdAccountsPayable.LoggingLevels Log4NetLevel);

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

Open project in VS2010 and verify service reference is created when interface included Exception Object

Add silverlight project and add service reference. Works correctly without Exception Object, fails with Exception Object

Using .Net 4.0

English

Windows 7

English

Service reference NOT created when Interface includes Exception Object

Service reference created when Exception Object inteface is removed.

Service reference should be created successfully in VS2012 as it is in VS2010

0 attachments

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)