I just installed WiX on my machine and then installed the extension for Visual Studio 2017. When I attempt to build the Product.wxs I get "Could not find wix.targets at ''" back. I can run a build from the command line using candle and light, but I need to be able to do this with VS. Is there a place I can configure Visual Studio to look for the wix.targets file. I'm guessing that is the problem since it looking at '' for the file.
Create a WiX v3 project not v4.
Related
I'm trying to build a SSIS 2016 project, that's been configured with the Project Deployment model in a VSTS build with the intent to deploy the .ispac file onto a SQL Server VM hosted in Azure.
Using MSBuild to build the project file returns the following error:
The default XML namespace of the project must be the MSBuild XML namespace.
If the project is authored in the MSBuild 2003 format, please add xmlns="http://schemas.microsoft.com/developer/msbuild/2003" to the element.
If the project has been authored in the old 1.0 or 1.2 format, please convert it to MSBuild 2003 format.
I found a blog post here describing the same issue
https://speaksql.wordpress.com/2013/06/07/a-journey-to-db-deployment-automaton-ssis-build-using-msbuild/
However, the solution depends on installed SQL Server Data Tools into a build agent.
Is there a method where I can use a VSTS Hosted agent, and not have to create an on-premises agent with SSDT installed?
Just released new Extension for VSTS/TFS
https://github.com/ToxicGlobe/VSTS-SSIS-Extension
It build Visual Studio project, containing packages and parameters to a project deployment file (.ispac)
https://marketplace.visualstudio.com/items?itemName=TG.VSTS-SSIS
For similar scenario i used devenv.exe
Tool : C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.exe
Arguments : .\Code\Database\NameOfSolution.sln /build $(BuildConfiguration)
devenv.exe /build does not require ssdt to installed on build agent
Looks like Microsoft is not supporting this just yet based off UserVoice
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/11543292-install-sql-server-data-tools-ssdt-for-sql-serve
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/4850300-install-sql-server-data-tools-for-bi-on-the-team-f
I have previously given up on installing OpenCV on my Windows 7 PC but now it has come back to haunt me, this time I'm trying to build its libraries using Visual Studio Community 2015.
I have tried finding a decent procedure on how to install it but they all sound simple until you encounter tons of errors when building ALL_BUILD in VS.
Here's what I did:
Downloaded the OpenCV 3.1 installer
Ran the installer and installed OpenCV in C:\
Added the OPENCV_DIR environment variable pointing to C:\opencv\build
Opened cmake-gui and set the source and build folders to C:\opencv\sources and C:\opencv\build, respectively
Clicked Configure, unchecked WITH_VTK option, clicked Configure again, then clicked Generate
Opened the generated solution file in C:\opencv\build
Right-clicked on the ALL_BUILD project and clicked Build
Only 11 projects were successfully built and 79 failed. The procedure they have on the OpenCV website is so outdated that it made me give up a long time ago. And there are several other resources that give equally confusing instructions.
Your help will be appreciated!
Upon further investigation, I saw this error frequently generated through build:
nvcc fatal : nvcc cannot find a supported version of Microsoft Visual Studio. Only the versions 2010, 2012, and 2013 are supported
This is caused by CUDA not supporting Visual Studio 2015 yet. So, I unchecked WITH_CUDA in cmake-gui, clicked Generate, opened the generated OpenCV solution file and built ALL_BUILD. No errors were generated after that.
I am just starting learning "Build 2D games with HTML5" from MVA and in starting i had a problem to configure my visual studio
Here is the link of that package Cordova-Windows package
The instructor shows that the Cordova windows package 3.5.0 contains CreateTemplates.bat file but it didn't work for me
i came up with this problem i dont know how to overcome this,
when i clicked the createTemplates.bat file its popup and off nothing happends so i try to open it up using command prompt and i get this errors , How to overcome?
what should i do now , your help would be highly appreciable !
You should use be using the Cordova CLI for your command line workflow for building Cordova Apps. For Cordova, more information is available here. If you want to use VS, then I strongly urge you to install our VS 2015 RC build which enables you to build Cordova applications for iOS, Android and Windows. More information for VS, is available here.
I used the script found here
... And every time that I generate this dynamic package, it needs to open the script task and click "Ok" because the "The binary code for the script is not found." error aways appears. Is there a way to solve this without BIDS ? Thanks and sorry my bad english.
I got this error when a SSISDB was upgraded to 2016 from 2012 and the package was not re-deployed using newer visual studio with project set to deploy to SQL Server 2016 in the project deployment properties.
This is often caused to to an error or omission in the code in the script task. If you are certain that the code is correct you can go to the script properties and set the PrecompileiIntoBindaryCode to False, the default is set to true. This is under the Properties or in the Script option of the properties window.
This worked for us
From Project properties, change TargetServerVersion to SQL Server 2019 (Or desired version)
open the .dtsx file for each package in Notepad++ or other text editor
remove the following for each dtsx file (there will be 1 occurence per script component in packages)
<PropertyGroup>
<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>
</PropertyGroup>
save the .dtsx file
go back into Visual Studio and rebuild the project file (as well rebuild individual script task)
I just ran into this error, after I changed my package deployment configuration to 2012. In the script some references we no longer linked. I had to reset the version of the .Net framework in the VS script environment, references were now legit, rebuild success.
In Visual Studio 2017, SSIS 2017 solution, had same error on a script task. Compared to another solution with similar process and discovered the issue was the Reference which had an error did not have a path listed for the dll. Removed the reference and added again. This resolved the issues.
Uninstall VS 2015 and SSDT 14.
Re Install VS 2015 and SSDT 14.
Open a new Integration project and import the SSIS project using the ispac file
Open the task having the error
Click On Edit Script.
Then either do this:
In Build tab click on Run code analysis on solution or Build or Clean and then Build
Save All the solution
Close the window
Click on OK in the task window.
OR just click on edit script and then OK button
The error should go off
This is for Visual Studio 2015 Community/SSDT 14
use SSMS V17.8.1 and upgrade your SSISDB and it will work, I tried it.
For me, I found that using string interpolation caused the issue.
For example:
This line caused the error:
command += $"test {property.Name}";
Changing it to this fixed the error:
command += "test " + property.Name;
After changing from VS 2017 to VS 2019, I saw this error in SQL Server / Integration Services Catalog / "My Package" / Validate... These messages are also visible in Standard Reports / All Executions.
My particular error messages were "VS_ISBROKEN" in the SSIS.Pipeline and "The binary code for the script is not found." in my scripting task.
I opened up the scripting task (C#) and changed the project target to x86 instead of None (MSIL), rebuilt it, closed the scripting solution, pressed Ok to keep the script changes, saved, built and deployed.
That worked for me.
Addendum:
It turns out that I was deploying a single package using VS2019 while the original Project was deployed using VS2017.
I think that the two deployments are not 100% compatible, and recommend that users either deploy an entire project, or deploy a package update using the same version as was used for the initial release.
You should probably ignore my suggestion above about changing project target.
Check your references, make sure all external references are added to the server's GAC.
For adding your dll(for example csvhelper.dll) in GAC you can use the following command in cmd.
C:\test>"C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7 Tools\gacutil.exe" -i csvhelper.dll
**Put your dll in a folder (for example in test folder)
**Pay attention which version of .Netframework you have(Here I used .net4.7)
I'm trying to build Marmalade project for Windows Phone 8 in Visual Studio Ultimate 2012 but receive following error:
error LNK1181: cannot open input file 'python.lib'
Seems that it happens because of wrong path to project's additional library directories. Currently it's c:\users\*user_name_omitted*\appdata\roaming\marmalade\packages\6.3.0\python_2.6.4\lib\wp8\x86
But in fact there is no wp8 folder. As I understand this foulder should be created automatically...
I have Marmalade evaluation license.
How can i get rid ot this error?
Two suggestions:
I've not got a working version to hand, but the bundled version of python with marmalade is (IIRC) 2.5.x, so the reference to 2.6.4 looks odd. I wonder if when you ran s3eConfig it was running a different version and got confused? More as like it should have downloaded some extra stuff and has not.
It might be worth uninstalling marmalade and then re-installing. There are reports of people not having a full installation following the install.