Search

SQL CLR VB Project - Upgrade from VS 2010 to 2012 fails by Mister T99

Closed
as Fixed Help for as Fixed

2
0
Sign in
to vote
Type: Bug
ID: 776968
Opened: 1/19/2013 7:42:09 AM
Access Restriction: Public
0
Workaround(s)
0
User(s) can reproduce this bug
I have a SQL CLR VB Project that works on VS 2010.

The upgrade to VS 2012 Premium fails, and I am unable to understand the error message well enough to repair the project.

----------------------------------------------------------------------------------------------------------

Your team marked this as 'Wont Fix', but no explaination. Please supply a reason why you will not fix.
----------------------------------------------------------------------------------------------------------

Details (expand)

Visual Studio/Team Foundation Server/.NET Framework Tooling Version

Visual Studio 2012

Steps to reproduce

1. Take the attached SQL CLR VB project.
2. Open it using VS 2012
3. The upgrade will fail

Product Language

English

Operating System

Windows 7 SP1

Operating System Language

English

Actual results

SQL CLR project upgrade from VS 2010 to 2012 feils

Expected results

SQL CLR VB project upgrade should have a high level of success.
File Attachments
File Name Submitted By Submitted On File Size  
SQLPollErrType.zip 1/19/2013 9 KB
Sign in to post a comment.
Posted by Microsoft on 3/26/2013 at 8:19 AM
To fix this go into the SQLCLR project properties page and select the .NET Framework version of 2.0. There is a bug in the upgrade process which forces the framework version to 4.0. Thanks for reporting this. It will be fixed in the next version of Visual Studio.
Posted by Microsoft on 1/21/2013 at 12:20 AM
Thanks for your feedback.

We are rerouting this issue to the appropriate group within the Visual Studio Product Team for triage and resolution. These specialized experts will follow-up with your issue.
Posted by Microsoft on 1/19/2013 at 7:51 AM
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)
Sign in to post a workaround.