VS2013 Update 2 has broken the Solution Explorer for SSDT database projects when using SQLCLR - by Daniel Nolan (ReadyRoll)

Status : 

 


11
0
Sign in
to vote
ID 873898 Comments
Status Closed Workarounds
Type Bug Repros 4
Opened 5/15/2014 5:00:38 AM
Access Restriction Public

Description

I'm getting a "Member not found" error with VS2013 Update 2 (either RC or RTM) in the Solution Explorer, with my SSDT database projects. I also get errors when adding new files to my database project, as well as when changing the values of various file properties (e.g. changing the Build Action to "none").

The errors occur if I have an AssemblyInfo.cs file in the project, i.e. in projects where I am deploying SQLCLR. The interesting part is, if I change the AssemblyInfo.cs file build action to None, then close and re-open the solution, I no longer get the error.
EDIT 2014-06-11: As mentioned by Lawrence Smith, the issue occurs if there are any .cs files in the database project at all, i.e. it is not limited to just the AssemblyInfo.cs file. To work-around the issue, you need to set all .cs files Build Action to "none".

A number of customers have reported this issue, who have also upgraded to VS2013 Update 2.

Here are some of the errors I am receiving in the Solution Explorer/Properties window:

* Exception has been thrown by the target of an invocation.
* An unexpected exception was encountered: The project item was not created.
* Not implemented (Exception from HRESULT: 0x80020001 (E_NOTIMPL)).
* Member not found. (Exception from HRESULT: 0x80020003 (DISP_E_MEMBERNOTFOUND)).
Sign in to post a comment.
Posted by Steven [MSFT] on 7/15/2014 at 10:17 AM
This issue has been fixed in our July release of SSDT. More information about the July release is available here:
http://blogs.msdn.com/b/ssdt/archive/2014/07/15/sql-server-data-tools-july-update.aspx

Thanks!
Steven Green [MSFT], SSDT
Posted by Daniel Nolan (ReadyRoll) on 7/14/2014 at 6:50 PM
Confirmed that this is fixed in the July update (SSDT 12.0.40706.0).
http://go.microsoft.com/fwlink/?LinkID=400927
Posted by Steven [MSFT] on 6/17/2014 at 6:21 PM
We are targeting a summer release date for the next version of SQL Server Data Tools. For historical context, since the first release of SSDT in March 2012 to our most recent SSDT release in late March 2014, the interval between releases has not exceeded 4 months.
Posted by harvyk on 6/16/2014 at 9:10 PM
This is also causing me major problems, since my CLR project is littered with CS files. Is there a safe way to uninstall Update 2 until this patch is rolled out via SSDT? Otherwise what sort of time frame is it until the next SSDT release?
Posted by Daniel Nolan (ReadyRoll) on 6/10/2014 at 6:31 PM
wizardvivek: It has since been discovered that having any .cs files in the database project will cause the problem. You will need to set all such files Build Action property to "none", in order to work-around the problem.
Posted by wizardvivek on 6/7/2014 at 10:56 PM
In the Database Project I don't have assemblyinfo.cs file. Could you please help me in understanding the workaround for this. Since we are in critical part of the development and this issue is seriously affecting things.
Posted by Steven [MSFT] on 6/3/2014 at 10:00 AM
Thank you for submitting this feedback. A fix for this issue will be included in the next release of SQL Server Data Tools.

Regards,
Steven Green [MSFT]
SSDT
Posted by Microsoft on 5/15/2014 at 10:55 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been reproduced and has been routed to the appropriate VS development team for review. We will contact you if we require any additional information. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Posted by Microsoft on 5/15/2014 at 7:48 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.
Posted by Microsoft on 5/15/2014 at 7:48 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If you require immediate assistance with this issue, please contact product support at http://support.microsoft.com/ph/1117.