I am using the VS Build Tools 2017 With MSBuild 15.4.8
The project builds and auto restores NewTosoft JSON pkg just fine in Vis Studio 2015 IDE. Not with the build tool however!
C:\Source\DevCopyJenkins\Utils\TestCIJenkinsNuGet>MSBuild TestCIJenkinsNuGet.sln /t:Restore
Microsoft (R) Build Engine version 15.4.8.50001 for .NET Framework
Copyright (C) Microsoft Corporation. All rights reserved.
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 10/17/2017 11:14:14 AM.
Project "C:\Source\DevCopyJenkins\Utils\TestCIJenkinsNuGet\TestCIJenkinsNuGet.sln" on node 1 (Restore target(s)).
ValidateSolutionConfiguration:
Building solution configuration "Debug|Any CPU".
**Restore:
Nothing to do. None of the projects specified contain packages to restore.**
Done Building Project "C:\Source\DevCopyJenkins\Utils\TestCIJenkinsNuGet\TestCIJenkinsNuGet.sln" (Restore target(s)).
Build succeeded.
0 Warning(s)
0 Error(s)
Time Elapsed 00:00:00.37
Related
I downloaded the file SQL2019-SSEI-Dev.exe and ran it.
I chosed media-download as well as user-defined. In both cases I got the same result.
I chosed german and english. In both cases I got the same result.
The installation-package could be downloaded without problems.
Then when it starts the installation assistent I got this message box.
I installed SQL Server Express before without problems. Before the installation of the Developer-Edition I deinstalled the Express.
I tried it several times but I am out of ideas now.
Windows Version:
net framework version:
C:\Windows\Microsoft.NET\Framework\v4.0.30319>msbuild -version
Microsoft (R)-Buildmodul, Version 4.8.4084.0
[Microsoft .NET Framework, Version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. Alle Rechte vorbehalten.
4.8.4084.0
C:\Windows\Microsoft.NET\Framework\v4.0.30319>
Need your help
I have successfully installed VS2017 on my computer .
But when I tried to install SQL server data tools 15.6.0 or 15.5.1 it gives me error as below :
Setup failed
The configuration registry key could not be opened(0x800703F3)
Thanks All!!
The latest version (15.6) of SSDT is incompatible with the latest version (15.7) of Visual Studio 2017. You currently have two choices:
Wait for an updated version of SSDT or VS2017 to be released, or
Completely uninstall VS2017 and install an older version.
If you want to go with option 2, do the following:
Run this command: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\layout\InstallCleanup.exe -f
Download and install version 15.6.7 of Visual Studio (link to the Community edition)
Download and install SSDT 15.6.0
This info was taken from a post on the Visual Studio Developer Community forum.
I recently have attempted to migrate a solution created and developed in Visual Studio (VS) 2012 to VS 2017.
I've managed to migrate all projects of my solution except for a Report Server Project. When I try to open my solution in VS 2017 I get the following message:
I click on Yes and VS automatically upgrades the project file (this is a file having the extension .rptproj)
When I now try to build the project I get the following error message:
Error Copying file Reports\Report\Project1\MyReportProject.rptproj.user to
obj\Debug\AspnetCompileMerge\Source\Reports\Report
Project1\MyReportProject.rptproj.user failed. Could not find file
'Reports\Report Project1\MyReportProject.rptproj.user'
I thought the upgrade would be performed transparently. Am I missing something? Is there any extra step I should take in order to do the upgrade?
Note: I've already downloaded and installed the latest version of Microsoft Reporting Services Projects .vsix package.
You can try the latest msbuild.exe for SSRS is here.
This includes steps of up-gradation of SSRS for both VS15 and VS17.
Once you install the latest update, depending on which version of Visual Studio you’re using, the new files enabling MSBuild for your projects will be installed in different folder path:
In Visual Studio 2017, it’ll will be a nested folder in your Visual Studio folder hierarchy. For example, the location with the Community Edition is in the Community folder:
Edit 1:
Try these steps:
1) Close Visual Studio - 17
2) Open VS-17 Installer
3) Try to install the SSDT workflow as:
I am running into an issue with SSIS project deployment using Visual Studio 2015 and SSIS 2016 [SSISDT March 2016 update] (SQL Server 2016 13.0.1300.275).
I am receiving the following error, when clicking deploy on the project or package:
Field not found:
'Microsoft.SqlServer.IntegrationServices.Wizard.Common.Model.DeploymentModel.TargetServerVersion'.
I originally assumed it was due to the fact that the project was upgraded from a previous version of SSIS, so I created a new project altogether specifically for 2016, but received the same error.
The error doesn't appear to be coming from the SQL Server itself, instead from Visual Studio 2015 and the SQLDT.
I am hoping someone else may have encountered this issue and may have a suggestion on how to proceed.
Folder capture after the build.
Output of Build:
------ Build started: Project: 340BHierarchyReDesign_Migration, Configuration: Development ------ Build started: SQL Server
Integration Services project: Incremental ... Starting project
consistency check ... Project consistency check completed. The project
is consistent. File 'C:\Users\kjackson\Documents\TFS Project
Repository\SSIS Projects
2016\340BHierarchyReDesign_Migration\340BHierarchyReDesign_Migration\obj\Development\340BHierarchyReDesign_Migration.dtproj'
get updated. 340BHierarchyReDesign_Migration ->
C:\Users\kjackson\Documents\TFS Project Repository\SSIS Projects
2016\340BHierarchyReDesign_Migration\340BHierarchyReDesign_Migration\bin\Development\340BHierarchyReDesign_Migration.ispac
Build complete -- 0 errors, 0 warnings
========== Build: 1 succeeded or up-to-date, 0 failed, 0 skipped ==========
This is a known issue with SQL 2016 and Visual Studio 2015 with SSDT, as of RC1 and RC2. There are apparently assemblies in SSDT and 2016 RC1\RC2 that are mismatched at this time and as a result you are unable to debug or deploy anything from the Visual Studio 2015 environment.
The current suggested workaround from Microsoft is to either uninstall SSDT and SQL 2016 RC1\RC2 from the computer running Visual Studio 2015 and reinstall the SSDT only. Or install an early release of the SSDT which limits you from using the 2016 features. This maybe resolved in RC3.
I am using VS 2013 and need to reference the Lync 2013 SDK. The install fails with:
Microsoft Visual Studio 2010 SP1 or higher not found
Is there any work around or do I have to downgrade to VS 2012?
Thanks,
Bill
I got it solved.
You can fix it by installing WinRAR and then right-clicking the .EXE file (the installer), extract it, and then run the 64 bit setup file. It installs to Program Files from where you can just reference the DLLs.