Home Dashboard Directory Help
Search

dbml upgrade passes parameters out of order upgrading .NET 3.5 to .NET 4.0 by RobertP2


Status: 

Active


1
0
Sign in
to vote
Type: Bug
ID: 794126
Opened: 7/16/2013 8:54:16 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

When I upgraded my project .NET 3.5 to .NET 4.0, my dbml files were re-generated. In at least one case, where the order of the parameters in my SPROC had changed (from the time I originally generated the dbml) the upgraded dbml pass the wrong values to the wrong parameters.

Where I use to have:
@PARAM1, @PARAM12, @PARAM3

I now have:
@PARAM2, @PARAM3, @PARAM1

Which was working fine until I upgraded; now the parameters are being passed by position, not by name. Meaning I get this:

@PARAM2=@PARAM1, @PARAM3=@PARAM2, @PARAM1=@PARAM3
Details
Sign in to post a comment.
Posted by Microsoft on 7/24/2013 at 12:09 AM
Hi, given that we have not heard back from you in these days. We will go ahead and close this Connect Issue. If you get a chance to review and provide the information requested earlier, you can go ahead and reactivate this issue.
Posted by Microsoft on 7/21/2013 at 10:58 PM
I am currently standing by for an update from you and would like to know how things are going on your end. If you could get back to me at your earliest convenience with information I request, we will be able to make headway towards a resolution. I look forward to hearing from you.
Posted by Microsoft on 7/16/2013 at 7:24 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting additional information outlined below.

Could you please give us a demo project to demonstrate this issue so that we can conduct further research?

We look forward to hearing from you with this information.

Microsoft Visual Studio Connect Support Team
Posted by Microsoft on 7/16/2013 at 9: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.