I have setup my own Team Foundation Build server and I am using Visual Studio Online to host my project online. I have a django project which I am trying to deploy on windows azure cloud service. The project can be published from my dev machine without any errors however when the build server tries to build it, it gives the following error during uploading the package:
Exception Message: Could not load file or assembly 'Microsoft.WindowsAzure.Storage, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified. (type FileNotFoundException)
I checked in .pyproj and found a reference to Microsoft.WindowsAzure.Storage but there the version is 2.1.0.0 and that is the version that is installed on the server as well.
Also there are no errors during the build process but only during the deployment stage. How do I make Msbuild use Storage version 2.1.0.0 instead of 2.0.0.0 . Also, which SDK version contains Storage version 2.0.0.0
I just had this problem. This is the same problem as TFS Build Controller : "Could not load file or assembly 'Microsoft.WindowsAzure.StorageClient, Version=1.7.0.0".
You'll need to copy Microsoft.WindowsAzure.Storage.dll version 2.0.0.0 to "C:\Program Files\Microsoft Team Foundation Server 12.0\Tools", and then restart the Visual Studio Team Foundation Build Service Host 2013 service.
Related
I am attempting to install SSDT v15.6.0 into an existing Visual Studio Team Explorer 2017 instance. When I run the SSDT installer, I can select Visual Studio Team Explorer 2017 from this list of existing Visual Studio instances. If I do not choose a any options (other than the required SQL Server Database option). The installation completes successfully.
If I however attempt to pick any/all of the other options the installation fails. From looking at the log files, it appears that the installation of the VSIX is failing due to a required component missing.
Below is the snippet of the SSDT-Setup installation log file which indicates that the VSIX failed to install.
[167C:1A6C][2018-05-16T15:40:41]i301: Applying execute package: Microsoft.DataTools.IntegrationServices, action: Install, path: C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe, arguments: '"C:\ProgramData\Package Cache\9864EE5369359DB622D0234B6C6B7640B949140C\VSIXBootstrapper.exe" /q /admin /instanceIds:"68f392fc" /logFile:"C:\Users\golaat\AppData\Local\Temp\SsdtSetup\SSDT-Setup-ENU_20180516153141_009_Microsoft.DataTools.IntegrationServices.log" "payload\Microsoft.DataTools.IntegrationServices.vsix"'
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Process returned error: 0x80131500
[167C:1A6C][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to execute EXE package.
[1D80:1858][2018-05-16T15:41:13]e000: Error 0x80131500: Failed to configure per-machine EXE package.
Looking at the log file for the installation of the VSIX it seems like a required component is missing:
5/16/2018 3:41:05 PM - BEGIN: Targetting Visual Studio Team Explorer 2017,15.0.27428.2043
5/16/2018 3:41:05 PM - BEGIN: Execute batch install
5/16/2018 3:41:08 PM - BEGIN: Preparing extension Microsoft Integration Services Projects
5/16/2018 3:41:08 PM - Loading extension: Microsoft Integration Services Projects
5/16/2018 3:41:10 PM - JSON file loaded
5/16/2018 3:41:10 PM - The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).
5/16/2018 3:41:10 PM - END: Execute batch install
5/16/2018 3:41:10 PM - END: Installing
5/16/2018 3:41:10 PM - Common folder deleted: C:\Users\golaat\AppData\Local\Temp\s0ggmkmo.cwz
5/16/2018 3:41:10 PM - Microsoft.VisualStudio.Setup.Dependencies.DependencyGraphConstructionException: The dependent package of 'Component.D1B09713-C12E-43CC-9EF4-6562298285AB,version=1.4' cannot be found: Microsoft.VisualStudio.Component.SQL.SSDT,version=[15.0,16.0).
Is there a way to identify this missing component an perhaps install it manually?
This is how I fixed it :
Run installer normally to the end and let it fail.
When it fails the window will have a link to the log file, open it.
In this log file, 1 or 2 lines before the error(Process returned error: 0x80131500) problem component location will be revealed, something like this:
[6748:674C][2020-07-29T09:44:03]i301: Applying execute package:
ISVsix, action: Install, path: C:\ProgramData\Package
Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe,
arguments: '"C:\ProgramData\Package
Cache\15160B731819F56D87A626F9A2777550340022D7\VSIXBootstrapper.exe"
/q /admin /instanceIds:"5403e431"
/logFile:"C:\Users\xxxx\AppData\Local\Temp\SsdtisSetup\Microsoft.DataTools.IntegrationServices_20200729093525_11_ISVsix.log"
"payload\Microsoft.DataTools.IntegrationServices.vsix"
You have to combine location of the VSIXBootstrapper with vsix component location. In my case I had vsix file under C:\ProgramData\Package Cache\15160B731819F56D87A626F9A2777550340022D7\payload
Copy failing component(.vsix), in this case Microsoft.DataTools.IntegrationServices.vsix to some folder before it gets deleted. If it already got deleted then restart the installer and search for this component in parent folders.
Restart your computer. I was getting "Another installation running .." error before I did.
Go to the folder where you copied the failing component and install the .vsix manually. This time it should install normally.
Repeat step 1 but this time hoping it will work normally.
I hope this at least gets you in the right direction.
This is currently broken due to a bug in Visual Studio - see this post on the Developer Community site:
SSDT cannot install onto 15.7 version of Visual Studio
It'll be fixed in a forthcoming Visual Studio update, but if you can't wait for that a workaround is to completely uninstall Visual Studio and install an older version. See my answer here for instructions:
https://stackoverflow.com/a/50349464/1184850
With the release of SSDT 15.7.1, Team Explorer no longer shows up as an existing Visual Studio install instance option within SSDT. At first I was concerned that the SSDT install would install a Visual Studio shell with no TFS connectivity, however this was not the case. It appears that the SSDT install of the Visual Studio shell picks up on the fact that Visual Studio Team Explorer 2017 is already installed on the machine and the SSDT Visual Studio shell instance has full TFS Connectivity!
I found a solution, follow these steps:
Download SQL Server and install it. In the Feature Selection step install Integration Service
Now download Visual Studio installer and install .NET desktop development and Data storage and processing
Now run Visual Studio and go to Extensions > Manage Extensions > Online, and search for SQL Server Integration Services Projects. Download and install that
You are now good to go.
We're running the following command for building and packaging Visual Studio Solutions:
MSBuild.exe *slnfile* /p:DeployOnBuild=true /p:CreatePackageOnPublish=true
It appears this creates packages for Web Applications but not Web Services. I don't even see a "Publish" option in Visual Studio for Web Service projects. How do I package these for deployment?
It turns out the developer didn't create a Web Application project, they created a simple empty C# project. I converted the project to Web Application and it works.
I'm following a tutorial to create a cross-platform app using xamarin.forms
except that I'm using Windows 7 and hence I skipped those steps for UWP part.
Now when I trying to build the solution, I'm getting the below error message
1> No way to resolve conflict between "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" and "mscorlib, Version=2.0.5.0, Culture=neutral, PublicKeyToken=7cec85d7bea7798e". Choosing "mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" arbitrarily.
Based on findings on the net it seems that something to do with versioning messed up however this should not happen as it's a new solution from scratch.
I've also checked the properties that stated as below:
- "Compile using android version (Android 7.1(Nougat))"
- Android Manifest "Target Android version" Use compile using SDK version
Well to be exact, the build was successful but with error logging as output. Please refer to below image
May I know what else I can try?
You can fix this by issuing an update-package -reinstall command in the Package Manager Console.
Make sure that your Xamarin (Visual Studio) installation version is the same as the Xamarin NuGet packages your using.
I recommend to:
Update Xamarin and your Xamarin NuGet packages to the latest versions.
Clean (in build menu)
Rebuild (in build menu)
Try again, if it does not work, continue steps:
Update all your Android related installations (using the SDK manager)
Check the paths for JDK, SDK and NDK in Visual Studio => Options => Xamarin
Try again
It could also be, that you are using a third-party NuGet package that is not compatible with your installed versions. Try removing NuGet packages to isolate the problem.
Unfortunately, there could be many things wrong here, but mostly it is related to versions and installations. Hope this helps.
It looks like you're trying to deploy to a device that does not meet the target requirements.
Verify that the version of the device or emulator you're working on is at least what is shown in your Android Build Options.
To troubleshoot any issues, I'd recommend opening the Android SDK Manager and downloading the Build and SDK tools that match the device you're planning to test on, and rebuild your project targeting the new SDK.
I have downloaded visual studio 2017 enterprise setup. Installation is fails while installing "Microsoft.VisualStudio.AspNetDiagnosticPack.Msi"
I am trying to install it on windows 8.1 (x64)
following is the error log
The product failed to install the listed workloads and components due to one or more package failures.
Incomplete workloads
.NET desktop development (Microsoft.VisualStudio.Workload.ManagedDesktop,version=15.0.26208.0)
ASP.NET and web development (Microsoft.VisualStudio.Workload.NetWeb,version=15.0.26208.0)
Incomplete components
ASP.NET and web development tools (Microsoft.VisualStudio.Component.Web,version=15.0.26208.0)
Container development tools (Microsoft.VisualStudio.Component.DockerTools,version=15.0.26208.0)
JavaScript and TypeScript language support (Microsoft.VisualStudio.Component.JavaScript.TypeScript,version=15.0.26208.0)
Windows Communication Foundation (Microsoft.VisualStudio.Component.Wcf.Tooling,version=15.0.26208.0)
You can search for solutions using the information below, modify your selections for the above workloads and components and retry the installation, or remove the product from your machine.
Following is a collection of individual package failures that led to the incomplete workloads and components above. To search for existing reports of these specific problems, please copy and paste the URL from each package failure into a web browser. If the issue has already been reported, you can find solutions or workarounds there. If the issue has not been reported, you can create a new issue where other people will be able to find solutions or workarounds.
Package 'Microsoft.VisualStudio.AspNetDiagnosticPack.Msi,version=15.0.30223.0' failed to install.
Search URL: https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.VisualStudio.AspNetDiagnosticPack.Msi;PackageAction=Install;ReturnCode=1603
Impacted workloads
.NET desktop development (Microsoft.VisualStudio.Workload.ManagedDesktop,version=15.0.26208.0)
ASP.NET and web development (Microsoft.VisualStudio.Workload.NetWeb,version=15.0.26208.0)
Impacted components
ASP.NET and web development tools (Microsoft.VisualStudio.Component.Web,version=15.0.26208.0)
Container development tools (Microsoft.VisualStudio.Component.DockerTools,version=15.0.26208.0)
JavaScript and TypeScript language support (Microsoft.VisualStudio.Component.JavaScript.TypeScript,version=15.0.26208.0)
Windows Communication Foundation (Microsoft.VisualStudio.Component.Wcf.Tooling,version=15.0.26208.0)
Log
C:\Users\Sagar\AppData\Local\Temp\dd_setup_20170830001200_003_Microsoft.VisualStudio.AspNetDiagnosticPack.Msi.log
Details
MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.VisualStudio.AspNetDiagnosticPack.Msi,version=15.0.30223.0\AspNetDiagnosticPack.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7" VSEXTUI="1"
Return code: 1603
Return code details: Fatal error during installation.`
Please help me to solve this issue.
Thanks in advance.
I am trying to setup a CI build process with Azure WebJobs. I have a ASP.NET MVC5 and a WebJob project in the solution and several class library projects. I have a working Visual Studio Online (VSO) build definition already setup to deploy the MVC project. However, when I add the WebJob project to the solution the build process fails with:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\Web\Microsoft.Web.Publishing.targets (2586, 5) Copying file C:\a\1\a**\*.* to obj\Release\Package\PackageTmp\app_data\jobs\triggered\LoyaltyClub\*.* failed. Illegal characters in path.
Any ideas how I can fix this? Both the MVC and WebJob projects are using version 1.0.7 of the Microsoft.Web.WebJobs.Publish Nuget package.