Finally saw that there is "Microsoft Reporting Services Projects 2022" available for VS2022, which should by idea work as a report designer and open the existing reports. But it turns out all of the report projects now are unsupported/incompatible due to new version of VS. If the VS2019 will be installed, there everything will work.
And migration report is not very informative:
The application which this project type is based on was not found. Please try this link for further information: https://go.microsoft.com/fwlink/?LinkId=661331&projecttype=F14B399A-7131-4C87-9E4B-1186C45EF12D
Any ideas how to make them work in VS2022? Maybe someone had similar experience?
Solution:
Thanks to the posted suggestion (marked green) managed to install 'Microsoft Reporting Services Projects' Version 3.0.1, which was crucial on VS2019, instead of the 'Microsoft Reporting Services Projects 2022'. That fixed my reporting issue, but due to outdated reporting solution. Probably will need to update it to newer one to avoid such legacy workarounds.
If you'd like to have early access to VS2022 release candidate builds before they are published to the VS Gallery, we’re making available to give customers an opportunity to provide feedback prior to finalizing releases. To access the release candidate of the extensions in Visual Studio, you may do so by creating a “private gallery” and entering the following settings.
Navigate to Tools > Options and then select Extensions and Updates under General.
Under "Additional Extension Galleries", enter the following details:
Name: Microsoft BI VSIX Preview
URL: http://aka.ms/ProBI-VSIX2022
After entering these settings, your "Extensions and Updates" dialog will show updates for the extension when there is a new release candidate that you can install to provide feedback for a day or two before the VS Gallery VSIX is updated.
Provide feedback and report issues with this Vsix Package or Reporting Services projects in general to: ProBIToolsFeedback#microsoft.com.
https://marketplace.visualstudio.com/items?itemName=ProBITools.MicrosoftReportProjectsforVisualStudio&ssr=false#overview
I faced a similar issue. I was working on my reports, closed VS2022 and trying to re-open the project, it was shown as "incompatible".
Go to Extensions -> Manage Extension -> Installed
In my case the 'Microsoft Reporting Services Projects' was disabled. Re-enable it, then close and re-open VS2022. If the project is still shown as "incompatible", reload it and it should solve the issue.
Related
A very valuable tool is the ability to quickly grab json and create a class. Paste Special in previous versions of VS was a great feature, but I can't locate it in Visual Studio 2019.
According to this forum thread, you just need to add the ASP web development tools. I've installed everything, paste special nowhere to be found.
How/where do I go to enable this or what is the new alternative provided in Visual Studio 2019?
I've combed through all the options & individual components in Visual Studio Installer, and I've enabled just about everything where this might live. But it's still not showing up in menu.
I met the same problems in here too with 2019 visual studio and found out how to fix it.
Go to Visual Studio Installer > Modify > Individual Components > Web development Tools
It should be under the Edit menu:
If you've installed the ASP.NET tools and still don't see this, send feedback so the product team can investigate why.
If you don't do it often, just use an online JSON to class converter
The "Paste JSON as Classes" option doesn't display when in debug. Just in case you had the option, but it seemed to disappear.
Try restarting your computer. My Paste special disappeared after altering some extensions. I updated Web Essentials 2019 and then uninstalled CodeMaid. When the option disappeared, I tried restarting Visual Studio and it didnt work, but after I restarted my machine, the option came back
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.
I have written a tool in Visual Studio Community using a C# windows form project. When I started the project I was unaware Microsoft insist on a user signing into an account after 30 days, (even though they offer an offline installation). For security reasons I cannot connect the computer to the internet to login. I have downloaded MonoDevelop and successfully opened and compiled the project. However, I would like to have the ability to "easily" edit the GUI. MonoDevelop's documentation seems to have little in-sight as to if this is possible. I checked out http://www.monodevelop.com/documentation/stetic-gui-designer/ which describes the process for native Mono applications. When I open the Form1.cs file, I am presented only with the option to view the source code. Is it possible to view the GUI designer?
The Stetic GUI Designer is only available for GTK 2.x based applications and not for Windows' Forms.
There is a project called WinForms Designer that might help you, it has not been updated for many years, but it still runs on at least OS-X (that is only OS that I have personally used it on).
http://www.mono-project.com/archived/winforms_designer
Note: For OS-X (or Linux) using the latest Mono, you will need to update the Makefile and replace the references to gmcs to mcs
I have a problem. This co-worker, whenever they open a BIDS project it gives her an error message:
...cannot be opened because its project type (.rptproj) is not
supported by this version of the application.
However, if I remote onto the computer using my login, it opens stuff just fine. The thing is, it was working for them for about 8-9 months. It just 'randomly' started doing this today. It also gives a similar error when creating new report projects.
Do you have an idea what the issue might be? I'm thinking maybe it's a configuration in the user profile? I mean, the computer obviously can open it up- just not for them. Has anyone experienced this and resolved it?
We are using the BIDS suite that comes with SQL Server. It is VS2008, we are running SQL Server 2008 R2.
Thanks in advance.
From Solved: project type (.rptproj) is not supported by this version of the application:
Install "Business Intelligence Development Studio" from the SQL Server 2008 installer.
See Business Intelligence Development Studio 2008 installation for more information on the installation.
I have a server that was configured by someone that is not on the company anymore and I need to check the TFS installation and enable that "dasboard" with reports, charts etc.
The only stuff working are: Source Control, issue tracking, web access.
As far as I could check, Reporting Services seems to be disabled (or not installed) and I don't know how to check SharePoint installation.
How can I verify and fix the TFS installation in order to make the reports work?
If Reporting Services are not installed or disabled, where can I install or enable it?
Use the Team Foundation Server 2010 Best Practices Analyzer included in the TFS Power Tools.
If you just open the TFS Admin Console, you can check for everything configured
SharePoint
Reports
Others
After that, start check this configuration per collection
If the SharePoint or Reporting not installed? You will need to install and configure them
For how to do this, there is a guide with videos on how to do enterprise installation, you can see the video of the SharePoint and Reporting only if you want, it will told you what exactly you will need to do?
http://tfs10enterprise.codeplex.com/releases/view/78529