4

Hoping you guys can help :)

Using VS2015 with currently latest version of SSDT. Have a script component and am trying to change the Target framework to 4.5.1 (from the default 4.5 - not sure where the default is gotten from) Have followed the instructions here - slightly modified for VS2015

The problem is that every time I set it and save, it reverts back to 4.5. Have also tried to set it backwards to 4.0 - same story.

Have tried saving and closing down project and Vsta editor in all combinations to no avail and suspect that this might be an environmental issue.

Any ideas?

TIA

Edit: I've since tried the exact same thing on another machine and it works perfectly, so it does indeed seem to be an environmental issues.

Improve this question
6
  • 1
    @BHouse have you actually read my reply to the only proposed answer? Are you just looking for places to type comments? Commented Nov 21, 2017 at 17:12
  • Which version of SQL Server are you targeting? Commented Aug 29, 2018 at 22:51
  • 1
    Did you figure out what was different in your development environment that was causing this error? I'm having the same issue where my target framework reverts back to 4.5 and the references I added from NuGet for MySQL are lost. I don't have another machine to use to test this from. The only answer below isn't helpful because the SSIS project doesn't have a target framework and changing the script task target framework doesn't hold when re-opening the script. Commented Jan 17, 2019 at 6:46
  • 1
    @Brandon, sorry no. Commented Jan 18, 2019 at 7:06
  • If the TargetServerVersion is 2017 it forces it to 4.5 and will overwrite the changes made. I was trying to use a MySQL integration that I ended up finding an alternate solution for (I think by using a different library but I don't recall now). Commented Feb 19, 2019 at 21:08

1 Answer 1

Reset to default
1

First thing to do, when you are creating a project, make sure to choose Target framework to 4.5.1. Kindly refer to this Cannot change Target Framework on Several Projects From v4.0 to V4.5 or 4.5.1 .

Since you mentioned about environment issue, you need to verify that .net framework 4.5.1 and above were installed in your environment. Hope this will help.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

Thanks for trying to help, but unfortunately that doesn't work. I can do the exact same thing on 2 different machines - on one it works as expected and the other not.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.