I have recently migrated my visual studio 2010 projects to 2013 but my database project looks unhappy about it. I have a TFS build definition which helps me deploy the database project and i have specified the (.sln) solution file and the .proj separate file which helps e drop the file to some location. This has been working well when I was using 2010 but right now its giving me the following error.
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\SSDT\Microsoft.Data.Tools.Schema.SqlTasks.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I replaced .sln file with the .sqlproj and this seems to fix the failing build definition but I don't get any deployment files.
Do you have any suggestions please, this is blocking my work right now.
You need to set the environment variable VisualStudioVersion=12.0 when building from the command line if you are using VS2013. SQL Projects rely on this to detect whether to use the VS2012 (v11.0) or VS2013 (v12.0) targets file when building.
Normally when a new Visual Studio version is released there's an accompanying .Net version update that changes the default VisualStudioVersion default value, but with VS2013 this didn't happen. Hence SQL Projects (and some other resources with similar version-specific dependencies) require 12.0 to be explicitly set as the version, since 11.0 is the default.
Also when running on a build server you must have a version of Visual Studio 2013 installed that includes the SQL Server tools. Full instructions on setting up a build server are in the whitepaper and presentation on the SQL Server tools team blog.
Related
UWP App not being able to work with MySql
I have made an app in UWP and instead of using SQLLite which seems to be the norm for Visual Studio 2015 I want to use MySql. I have already connected my Azure mysql database to Visual Studio via the 'Server Explorer'.
I'm using MySQL Workbench to update my tables within my connected database from Azure but I cannot actually write any code to access my tables as whenever I try to install MySql.data/.entity/etc in the NuGet Package Manager I get an error.
nuget error
I tried downloading the Mysql installer, the Mysql drivers for Ado and ODBC. I even tried downloading the MySql for Visual Studio option as I found out that Visual Studio is not compatibile with MySql and instead requires the MySql for Visual Studio download but I still have errors whenever I try to use MySql in my code as I need an assembly reference for it but I'm having no luck in being able to get one that doesn't error.
Does anybody have any idea how I could actually use MySql within Visual Studio 2015?
This is what I've been using as my guideline but I can't seem to get past the Mysql.data errors when installing.
http://web3.codeproject.com/Articles/1074242/Designig-your-Azure-MySQL-DB-with-a-UWP-Demo
I have seen a lot of people talk about this but there is no one straightforward fix (I've tried a lot of the fixes, one in particular being to use Vs13 to install Mysql in the Nuget package manager and then it should update within VS15 but as my app is a UWP VS13 does not actually load/read it so that idea isn't good to me, might help anyone else though)
Starting with 6.7, Connector/Net fully supports building Windows Store apps. But using Connector/Net RT is not by install the Nuget package, it just reference the MySql.Data.RT.dll assembly according to MySQL Connector/Net Developer Guide:
Using Connector/Net RT is easy. Simply create a Windows Store application using Visual Studio and then reference the MySql.Data.RT.dll assembly in your project. The code you write should be exactly the same as for normal Connector/Net (including using same namespace MySql.Data.MySqlClient) except for the differences listed above.
You may find this dll at C:\Program Files (x86)\MySQL\Connector.NET 6.79\Assemblies\RT if you have install the connector. You can also download the mysql-connector-net-6.7.9-noinstall.zip to find this file inside the folder. I also have a MySql UWP sample before and has the dll here. Right click your project and add reference for this it will work.
More details please reference this sample
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.
This have been told here but I really can't figure why Visual Studio 2013 Ultimate (x86 installation) generates only bin\Debug and does not generate bin\Release folder.
Does anyone know why it does not generate the release folder?
Here is my Visual Studio version (am I missing a Service Pack?)
My project is a Windows Forms Application.
My project is targeting .NET 2.0, it runs fine and bin\Debug is always generated. Here are my project properties with default configuration:
Hope you have set the Release configuration from here:
Also go to the Configuration Manager and check the Active Solution Configuration as Release.
I have been searching for a while on this and have no real direction on what the problem may even be. I haven't done SSIS for about 5 years and even 5 years ago I only did one or two.
I have Visual Studio 2012 on my machine. I installed SSDT so that I could write an SSIS package. I have the package written and working locally but when I try to set up a job in the SQL Agent on the server I get this error after selecting the package:
I have looked into this error and none of the resolutions I have found are working. My project is already set to not use 64 bit mode. I'm kind of thinking this might have to do with the fact that the version of SQL Server on that machine is just 2008 and that maybe that means it has an incompatible SSIS runtime. I don't know if there is an additional runtime I need to install to get this to work and I don't know if it's backward compatible with the old runtime they are using if that's even the problem.
I can't find any information online about setting up the environment for an SSDT SSIS package..
Please help.
Thanks
You have a package built against the SQL Server 2012 Integration Services object model. You are attempting to execute it on a 2008 instance. Backwards compatibility is not an option.
You need to either update the 2008 instance to 2012 (there is a licensing change to be aware of) or recreate your package using the 2008 model.
There are 2 steps you have to do:
1) Build you package using correct version - Update 2208 Instance to 2012
2) If you have multiple versions install and you try to deploy using .ispac file, it will most likely pick the latest version. To resolve the issue, you have to pick the correct version of Installer by going to where it is installed. In my case it is (C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn)
I've been trying to get a report running through Microsoft ReportViewer in Visual Studio 2012. Here is my situation.
I have a report (.rdl file) that was originally created through Microsoft Reporting Services running on a SQL Server 2008 R2 server.
I originally tried moving it into a VB.NET project running through Visual Studio 2005, but when I converted the .rdl file to .rdlc and tried to bring it into the VS 2005, I could not view the .rdlc file in design time. A while after that, I figured out that this was due to schema compatibility issues because of the fact that the report was created on a SQL Server 2008 server.
So then I tried creating a project through Visual Studio 2012 instead, which we also had in house. This time I was successfull at being able to view the report in design time. However after that, I ran into run time issues because I was using Version 8 of the Microsoft.ReportViewer.Winforms dll. I believe that this was also due to a schema comaptibility issue
So now, I'm trying to move up to using a newer version of the Microsoft.ReportViewer.Winforms dll (Version 11). When I remove the Version 8 and add the version 11 instead in my references, everything appears to be fine at first, no errors present. However, when I try to build my project I get the many compile errors all over the place like the following:
Type 'Microsoft.Reporting.WinForms.ReportViewer' is not defined.
The wierdest part is that if I were to remove and re-add the reference, or check one of the Microsoft.Reporting references in the Imported namespace, all the errors go away. But when I rebuild the project the errors come back, and I'm stuck.
I'm currently running the Microsoft .NET framework 4.5 on my computer, and I'm using Microsoft Visual Studio Professional 2012 as my development platform.
Any help would be appreciated
Thanks,
Doug
This might help: How to edit SSRS 2008R2 Reports in Visual Studio 2012?