This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 84%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDL%3C/text%3E%3C/svg%3E)
Hi
I have Visual Studio 2019 16.9.3 installed with just the Data storage and processing Toolset and the SQL Server Integration Services Project 3.12.1 extension.
When I try and compile a script task I get the following error from mscorlib.
Severity Code Description Project File Line Suppression State
Error Could not find a part of the path 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\bin'
Not surprising since this folder does not exist in the installation.
Obviously our migration to VS19 from VS17 is on hold until this issue can be resolved
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 26%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EYK%3C/text%3E%3C/svg%3E)
Please add a screen shot with the error in VS2019 to your question.
Just tried running an installation repair using Visual Studio 2019 installer but this has no effect
Please make sure that you have the following installed:
I don't have a bin directory on my machine under
c:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\
and everything is working properly.
Please make sure that SSIS Script Task is using .Net Framework version that is installed on your machine.
Hi
I checked registry and it is running above 4.5 (according to Microsoft Learn)
Specifically version 4.8
Hi
As you can see from the previous posts I am running all the latest and correct versions of Visual Studio and the SSIS projects extension. I am also running .net 4.8 on that VM.
The script task will be using whatever is appropriate for SQL Server 2016 (VSTA VB.net 2015 I believe.) This VM was running SSIS in VS17 perfectly until I upgraded it.
Obviously despite the patch to the SSIS Projects extension Microsoft still haven't got it right for systems that are only using SSIS. I'll wait for them to fix it for now
David
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 87%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDW%3C/text%3E%3C/svg%3E)
Same issue here, all components are up to date
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(35.2, 16%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESC%3C/text%3E%3C/svg%3E)
Same issue. Professional version will work fine, but Community version won't compile scripts.
It doesn't work with the professional version, that's what we're using.
Hmmm. I' m using the Enterprise version as we are licenced for that under the partnership program.
I have a feeling it might be a mismatch between the library locations and the environment path settings.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 6%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPK%3C/text%3E%3C/svg%3E)
Same issue here (i.e. missing bin folder) with VS2019 Community version 16.9.4, Integration Services Designer extension 15.0.2000.166 - an existing SSIS 2017 project being upgraded to SSIS 2019..
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(140.8, 28.999999999999996%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Hi all.
I have the same proble.
I have SSIS package from VS 2017 Community version and all script task work fine, but in the same machine with a VS 2019 Professional when I try change and after rebuilt any script task I get this error:
Severity Code Description Project File Line Suppression State
Error Could not find a part of the path 'C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\bin'.
I have reviewed the NetFramework version and seems that is correct for a 4.5 :
I have try to change dt TargetFramework used for all script to 4.5 version,
(that is a suggestion in other forum)
after I realized that some packages with this version in script task work, and the packages that doesn't work have 4.0 version, but It doesn't work either.
Does anyone have any more ideas to solve that situation?
Many thanks
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi
tried this by changing the dtproj files manually and by editing the project using the Visual Studio interface. Tried both changing the entries to .\bin\ and deleting them and neither change worked. Still got the dialog telling me it couldn't compile the script although no errors reported or found when editing the script.
When is Microsoft going to fix this? They have already agreed that this is a regression bug in Visual Studio 2019 in the link AidanOrton posted.
We are just sticking with VS 2017 for now until they release a working version.
Regards