We have a couple of projects in the integration services catalog, both containing packages that contain vb script tasks. I did an export of them from the integration services catalog into ispac files and tried to pull them into visual studio
2015. they both pulled in, but when opening the script task we noticed that it was converted to c# and was just a shell. After that, I pulled the projects directly from the integration services catalog using visual
studio and the integration services import project wizard. after doing this, I was able to open one of them and the script task was vb and was complete, but the other was still a C# shell as before. The
server instance is sql 2016. We have the code saved in source control, but we are having a prod issue and were wanting to pull the code from prod and verify what is actually running to make sure it was what we thought it was.
Any idea why it's losing the vb script task and converting to a c# shell?
↧