I'm using Visual Studio 2012 to create a CRM 2011 Workflow Project
After filling the details of the CRM server I get this message
"failed to get location of Visual Studio from registry"
Why? and How to fix it please.
if you're on a 64 bit machine, try copying the whole visual studio registry key from local_machine to current_user.
Related
I am working on an SSIS package in Visual Studio 2017 SSDT. I had an update come through for Microsoft SQL Server Data Tools for Visual Studio 2017 (SSDT) Version 15.9.18 and it updated successfully. I went to open one of my SSIS packages and when I opened the Script Task and clicked EDIT to the C# code I now get an error: using Microsoft.SqlServer.Dts.Runtime; is no longer available. What do I now use in its place so that I can continue working? Any help/direction would be appreciated. Thanks.
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.
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.
I have an error when trying to run Worklight project as Visual Studio Project.
The project is set up in Eclipse Juno EE, Worklight version is 5.0.6.2. Project is successfully can be build and run as Android project. But when I run it from Eclipse menu Run->Run As->Visual Studio project I have an error:
Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegKeyEx(…) returned error code 5.
Failed Running Visual Studio: Cannot find Visual Studio 2012 or later.
Am I missing something obvious?
Thanks a lot in advance for help.
Do you have Visual Studio 2012 or 2013?
In 5.0.6.x, if you have Visual Studio 2013 you will need to double-click the .csproj/.jsproj accordingly in order to open the project.
This is fixed in newer versions of Worklight; namely, Worklight 6.0.0.x and above.
Now that Visual Studio 2012 is released, where can I download the accompanying 2012 Report Viewer Runtime so I can install it on my server? Is there a redistributable installer included with Visual Studio 2012?
Specifically, I'm looking for the updated 2012 version of this: Microsoft Report Viewer 2010 Redistributable Package
I believe I've found a temporary workaround for this:
In your project's references, select the Microsoft.ReportViewer.WebForms assembly.
Add a reference to C:\Windows\assembly\GAC_MSIL\Microsoft.ReportViewer.Common\11.0.0.0__89845dcd8080cc91\Microsoft.ReportViewer.Common.dll
In the properties window, set "Copy Local" to True for both assemblies.
Deploy your project to the server.
I haven't tested this extensively, but so far it appears that simply copying the assembly to your project's bin directory satisfies the runtime requirements on the server.
the final version of the installation program is http://www.microsoft.com/en-us/download/details.aspx?id=35747