May 20, 2021 at 1:29 pm
I have no link for VS Pro, you need to buy it or create a VS subscription.
Before you do that, can you try creating a brand new package and adding a script task to that, then see whether you can open the C# editor from there. Just to make sure that this issue is machine related, rather than package related.
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
May 20, 2021 at 3:44 pm
To fix the issue with not being able to edit scripts - you need to repair 'Microsoft Visual Studio Tools for Applications YYYY'. This happens almost every time you apply an update to SSDT/Visual Studio and is a pain, but once that program is repaired you will be able to edit scripts again.
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
May 20, 2021 at 4:40 pm
To fix the issue with not being able to edit scripts - you need to repair 'Microsoft Visual Studio Tools for Applications YYYY'. This happens almost every time you apply an update to SSDT/Visual Studio and is a pain, but once that program is repaired you will be able to edit scripts again.
Simple as that? The hours I've wasted in the past. Thanks for the tip (assuming it works :-))
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply