I recently created a new SSIS project from within VS2015. I added a script task and when I click on the "Edit Script" button. Visual Studio opens; however, there's no solution
I'm running VS as administrator. I've tried re-installing Microsoft Visual Studio Tools for Applications 2015. With no luck. I did once get the solution to pull up after I re-installed Microsoft Visual Studio Tools for Applications 2015; however, the next time I clicked "Edit Script" there was nothing.
Is this a bug withing VSTA or has anyone else came across this issue?
"Edit Script" buttion from within the Script Component:
No solution when clicking "Edit Script":
Ok, for me this problem was due to Resharper - if I go under Tools | Options | Resharper and Suspend Now it allows the VSTA editor to display each time. Hope this helps
I've solved the exact same problem today. In my case it was most likely caused by installing and removing several versions of VS/SSDT without some proper clean-up.
Go to Control Panel -> Uninstall or change a program -> "Microsft SQL Server Data Tools for Visual Studio 2015" -> Change -> Repair.
Repeat the steps for "Visual Studio Tools for Applications 2015".
This should only fix your installation and not affect any of your projects.
After restarting my Windows the problem was fixed!
I have VS 2013 (with VSTA 2012) and VS 2015 (with VSTA 2015). I had the same problem: If I tried to edit a Script Task (both in VS 2013 SSIS or VS 2015 SSIS project), the VS 2015 shell opened, but was empty.
I tried the solution described by Rae: Uninstalling "Visual Studio Tools for Applications 2015" and subsequently repairing "Visual Studio Tools for Applications 2012". This solution worked for VS 2013, after that, all scripts are opened in VS 2012. But after that, in VS 2015 SSIS Projects, I could no longer edit Script Tasks. (Error message "Could not load file or assembly 'Microsoft.VisualStudio.Tools.Applications, Version=14.0.0.0,...")
The solution was:
- Repair "Microsoft SQL Server Data Tools - Visual Studio 2015" (which re-installed VSTA 2015). After that I had the same problems like at the beginning, VS 2015 Shell opened empty, without source code file.
- Install VS 2015 Update 3 (like recommended by Rob Nicholson). This was the fix...
After that, I can edit Script Tasks both in VS 2013 SSIS and VS 2015 SSIS projects, both open the VS 2015 shell.
I was experiencing this issue with an SSIS 2012 project.
Uninstalling "Visual Studio Tools for Applications 2015" and subsequently repairing "Visual Studio Tools for Applications 2012" got it for me.
My SSIS project in VS2012 would try opening scripts in a VS2015 instance. After uninstalling VSTA 2015, VS2012 now successfully opens the scripts in a VS2012 instance.
For reference, I have both Visual Studio 2012 and Visual Studio 2015 installed. I also have SQL Server Data Tools v11.1 and v14.0 installed.
I'm guessing this issue comes down to clashing versions of Visual Studio Tools for Applications.
I tried many of the proposed solution but could not get this working. After I updated SQL Data Tools to 14.0.61707.300 (the highest version of available for Visual Studio 2015 available) and applied Visual Studio Update 3 (14.0.25420.01) the code inside the Script Task / VstaProjects now populates correctly. As a side note my SQL/SSIS version is 2016 and Visual Studio Tools for Applications 2015 is at 14.0.23829. Hope this helps
I've encounted the same problem as well.
Since no solution to repair VisualStudio until now, I began to do the job by writting my own code directly in the DTSX file.
If your logic business was not very complex, this solution maybe suitable:
Firstly, add a "Scritp Task" in your package of SSIS project. It will generate lots of code in the DTSX file, and save our work.
Open DTSX file of the package in Notepad++/SublimeText, as your wish, and look for "// TODO: Add your code here", which was in a public void Main().
Fun Coding!
I've uploaded a project of TestScriptTask, in case of making coding easier in visual studio. It needs SQL Server Developer edition installed at least (Express edition probably would not work, didn't test).
Restart VS 2015, then it will load the next time you try.
Every time it fails, restart VS.
Yes simple/tedious... but works. Just write everything correctly the first/1 time you edit the script ;) easy
I came across this issue and it was driving me crazy. GIT is definitely what is causing this. When you take the solution out of the source control directory, the problem disappears.
Related
For many versions I have a reporting services project in Visual Studio. The latest is Visual Studio 2013. I have installed Visual Studio 2017 community edition and it has the Microsoft Reporting Services Projects extension. It also says that it has Data Tools installed as part of VS (at least that's what it looks like). Yet my rptproj file will not be recognized by Visual studio 2017. Every document that I'm sent to says I need SqlServer Data Tools but is that now a separate program I have to use to deal with reports outside of Visual Studio? It makes no sense to me given that there is a reporting Services projects in VS. But that isn't working at all. I've tried creating a new project and copying the RDL over to it. It opens it and I can see designer but when I try to preview I get the dreeded " Unknown report version 9". Any help would be very very much appreciated.
Just download and install
https://learn.microsoft.com/en-gb/sql/ssdt/download-sql-server-data-tools-ssdt
SSDT will provide all the missing bits for VS2017. You will then be able to edit your reports in VS2017 but you will need to upgrade the solutions. You will be promoted to do this upgrade when you attempt to open the project/solution.
I am trying to convert some older VS2005 projects over to VS2015 Enterprise. When I open any with a report project (.rptproj), VS says the project is unsupported.
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
Every search I've done, the solution is to install SSDT (apparently formerly known as SSDT-BI)
I havs SSDT installed already.. when I download/install from here (https://msdn.microsoft.com/en-us/mt186501.aspx), it gives me repair/uninstall options. I've tried repair even though I did not suspect it was broken. There are no updates available under Tools > Extensions and Updates... in VS.
Where do I go from here? Every solution I've found says the same thing, but I already have SSDT.
Any info appreciated.
Support for BI projects for Visual Studio 2015 is available here: https://msdn.microsoft.com/en-gb/mt186501
There are two versions of SSDT available for Visual Studio 2015. Only the "Preview" version (available here: https://msdn.microsoft.com/en-us/mt429383.aspx) contains the BI project types.
SQL Server Data Tools in Visual Studio 2015 (a.k.a. SSDT)
Open Visual Studio 2015 and choose the Tools > Extensions and Updates menu. SQL Server tooling updates will appear in the Updates list.
Visual Studio 2015 comes with SSDT which is why you kept getting repair screens - note "SQL Server Data Tools Preview in Visual Studio 2015" is the older version
My development environment: SQL Server 2014, Visual Studio 2015, SQL Server Data Tools Preview (September) for Visual Studio 2015
I have a custom SSIS source component that I can successfully use on another SQL 2014 box with VS 2013 and SQL Server Data Tools - Business Intelligence. However, this component does not show up in the toolbox in VS 2015 Integration Services project.
The component is located in c:\Program Files (x86)\Microsoft SQL Server\120\DTS\PipelineComponents. It is also registered in GAC.
Do I need to make changes to the component so that it will work with VS2015?
More general question: how to troubleshoot issues like this?
I've managed to get the problem of adding a custom SSIS component to a Visual Studio 2015 SSIS package. This maybe have been enabled by the release of SQL Server 2016 CTP 3.2, but I thought that I'd put this out there in case it helps anyone.
First of all let me just let everyone know what system I'm using in case this doesn't work for everyone:
My system is: Windows 8.1 64 bit
Visual Studio Community 2015 Version 14.0.24720.00 Update 1
Microsoft SQL Server Integration Services Designer Version 13.0.900.80 (I've installed the SQL Server 2016 CTP3.2 so the version of SSIS is this version - this may be part of the problem and it isn't a fully released product and this may be a bug)
Microsoft .NET Framework Version 4.6.01055
In my c# class project I used the .NET Framework 4.6
(Project Properties->Application).
I made sure that I added to the gac using the gacutil.exe in the following folder:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6 Tools
and I copied the dll to the following folder:
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\PipelineComponents
After refreshing the SSIS toolbox the component now appears in the Common folder/subsection.
I hope this works for everyone or is at least of use to anyone else who has had this problem. I was so happy after trying nearly everything and it coming up blank to see the component appear in the SSIS toolbox and know how frustrating this kind of thing can be!!!
Matt
In VS2015 Solution Explorer, right click on the .dtproj file and select properties. On the General Tab choose the SQL Server version that matches the component version. If the component worked on VS2013, choose 'SQL SERVER 14' when opening the package in VS2015.
Visual studio 2012 hangs frequently. Every time I am trying to close it through TaskManager and when opening the solution, visual studio will stay for 1 to 2 mins then hangs.
Restarted my system.
Restarted Visual studio 10 times.
Closing all the files in Visual studio when restarting the solution.
My observation : This is happening after installing Json.net through nugetpackagemanager and adding reference to Newtonsoft.JSon .
Any solution for this?
Download VS 2013, its awesome with GITHUB Integration and Many productive tools.
When I click on EDIT SCRIPT button for Script Task in SSIS 2012 package,
It does not open the Script editor rather it shows:
"cannot show Visual Studio Tools for Application editor"
Couls not load file or assembly
"Microsoft.visualstudio.tools.applications.core version=10.0.0.0 ...."
system can not find the file assembly specified.
I tried the solutions provided in the following links:
http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e5337b0c-7f70-4603-859e-fbc7d0cf1c37
SSIS Script Editor throws an exception
First of all go to Program and Features and check whether you have
"Microsoft Visual Studio Tools for Applications x86 Runtime 3.0"
installed. Most probably you will see this below
"Microsoft Visual Studio Tools for Applications x64 Runtime 3.0"
If it is not installed then you have the same issue that i have.
To resolved this error, I put in my SQL Server installation disk. Then go to redist->VSTA->runtime->x86 and then run VSTA_RT30.msi
The workaround mention in this link solved my issue:
https://connect.microsoft.com/SQLServer/feedback/details/776248/could-not-load-file-or-assembly-microsoft-visualstudio-tools-applications-core
Both the x86 and x64 runtimes must be installed, currently one or both the runtimes may be missing depending on the order of the SQL Server 2012 installation. As a workaround, check in Control Panel - Programs and determine which of the component is missing (it should be listed as Microsoft Visual Studio Tools for Applications x86 or x64 Runtime 3.0). You can install the component manually from your installation disk or download from the \redist\VSTA\runtime\ folder.
It is year 2021, when searching for the error, this is the top hit. The solution that worked for me with Visual Studio 2019 is to download and install "Visual Studio Tools for Applications 2019"
Link:
https://www.microsoft.com/en-us/download/details.aspx?id=58317&WT.mc_id=DX_MVP4025064
Interestingly, this is not provided as an option in Visual Studio installer. The above needs to be manually downloaded and installed.
By now, SQL Server 2012 Service Pack 1 is out. Try updating your release and after that, you might even consider putting the Cumulative Update 1 on top of it.
More about CU1: http://blogs.msdn.com/b/sqlreleaseservices/archive/2012/11/21/cumulative-update-1-for-sql-server-2012-service-pack-1.aspx
goto SQL server installer folder and install these msi files
redist/VSTA/designtime/VSTA_DT30msi
redist/VSTA/runtime/x64/VSTA_RT30.msi
redist/VSTA/runtime/x86/VSTA_RT30.msi