I want to build my windows 8 application on tfs but I have a problem with Bing maps sdk. There are no Bing maps dll that I can easily add it to references. How can I solve the problem? I got this error in tfs build log file.
"C:\Builds\1\...sln" (default target) (1) ->
"C:\Builds\1\...csproj" (default target) (2) ->
"C:\Builds\1\...csproj" (default target) (19) ->
(ResolveSDKReferences target) ->
C:\Program Files (x86)\MSBuild\12.0\bin\amd64\Microsoft.Common.CurrentVersion.targets(1886,5): error MSB3774: Could not find SDK "Bing.Maps.Xaml, Version=1.313.0825.0". [C:\Builds\1\...csproj]
You need to install the Bing make SDK to the build server for the build to work properly.
Generally you will need to install everything that you need to install locally to build. Your build server is a consistent mirror of your development environment.
I solve the problem with this visual studio extension :)
https://visualstudiogallery.msdn.microsoft.com/1f027247-1e01-4ec6-8f5b-70dabb375217
Related
I have a .net core class library I am attempting to build into a nugget package. however, on my build server (running team city), I am getting the following error:
C:\TeamCity\buildAgent\work\3c6531587491c25e\MySolution\MyProject.csproj
error MSB4019: The imported project "C:\Program Files (x86)\Microsoft
Visual
Studio\2017\BuildTools\MSBuild\Sdks\Microsoft.NET.Sdk\Sdk\Sdk.props"
was not found. Confirm that the path in the declaration is
correct, and that the file exists on disk.
When I look in this directory, I ma missing the "Microsoft.NET.Sdk" folder from my build server. where do I get these tools without having to install visual studio?
Thanks!
See the tracking issue on GitHub: https://github.com/Microsoft/msbuild/issues/1697
If you don't want to touch your build tools installation (by copying SDK files), you can also set the MSBuildSDKsPath environment variable to the location of the SDKs carried in the .net CLI (usually C:\Program Files\dotnet\sdk\1.0.0\Sdks\)
I downloaded the WinPcap sources 4.1.3 as well as the corresponding AirPcap developer kit. I followed the build instructions described from the WinPcap website 1:
I loaded the project contained in the directory PacketNTx\dll\project with VS2013 (running on Windows 7 Professional x64). When I try to build the default project configuration (Debug, Win32) I get the error that the include file "netmon.h" cannot be opened. I also searched the web and found that this file is part of the wiretap library included in the Wireshark source code...
Can anyone suggest how to build the default configuration of the WinPcap packet.dll and wpcap.dll?
Thanks in advance!
best regards!
I'm running MSBuild 4.0 against my .net 4.0 solution and I am getting a lot of error similar to the following:
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\BC_HCIM.msbuild" (default target) (1) ->
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\BC_HCIM.sln" (Build target) (2:2) ->
"E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\src\Common\HCIM.Distribution.Service\HCIM.Distribution.Service.csproj" (default target) (46:3) ->
(CoreCompile target) ->
DistributionProcessor.cs(6,32): error CS0234: The type or namespace name 'Distribution' does not exist in the namespace 'HCIM.BusinessTransaction' (are you missing an assembly reference?) [E:\Hudson\jobs\HCIM 7.0.0\workspace\7.0.0\HCIM_Dev\src\Common\HCIM.Distribution.Service\HCIM.Distribution.Service.csproj]
When I build this in the IDE, it compiles fine (VS 2015, VS 2013), however on Jenkins and when I locally run my script, these are the errors that comes up.
Looking at the IDE and the .csproj files I see that these assemblies are referenced accordingly.
Thoughts?
This sounds like an msbuild and/or framework version issue. Here's a few things to check:
What framework version are your projects referencing? Maybe one is targeting a higher version than 4.0
Make sure this framework version is installed on build server.
Try adjusting your script to use the same msbuild version as the IDE
Note Msbuild is not part of the framework since VS2013 but a separate download is available for running on your build server.
Does AppHarbor support ASP.NET Core?
When I tried to deploy my sample application (From the Visual Studio 2015 RC templates) I got the following build log in AppHarbor:
Build started 5/4/2015 2:28:38 PM.
1>Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" on node 1 (default targets).
1>ValidateSolutionConfiguration:
Building solution configuration "Release|Any CPU".
1>Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (1) is building "D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (2) on node 1 (default targets).
2>D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj(7,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\DNX\Microsoft.DNX.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
2>Done Building Project "D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (default targets) -- FAILED.
1>Done Building Project "D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (default targets) -- FAILED.
Build FAILED.
"D:\temp\g3zdb4oh.rcv\input\ASPNetTest.sln" (default target) (1) ->
"D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj" (default target) (2) ->
D:\temp\g3zdb4oh.rcv\input\src\ASPNetTest\ASPNetTest.xproj(7,3): error MSB4019: The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\DNX\Microsoft.DNX.Props" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk.
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:00.03
The code that I tried to deploy was this:
https://github.com/yngndrw/ASPNetTest
I'm not sure if I missed something or if AppHarbor doesn't support this yet ?
Rune from AppHarbor has responded to my question:
Hi,
ASP.NET 5 / vNext and .NET 4.6 is not officially supported yet as they are still at the RC state - official support will be rolled out and deployed across all servers when they reach RTM. Note however that for vNext / ASP.NET 5 application you may still be able to run those applications on AppHarbor, but for now you'd have to work around the missing build targets projects, as those are not currently available on AppHarbor's build servers.
AppHarbor will continue to support earlier versions of the .NET Framework including 4+, and there are no plans to discontinue support for applications requiring those frameworks when vNext and .NET 4.6 is officially supported.
We may also introduce beta support or guidelines for deploying apps using the newer frameworks prior to the official RCs. I'll make sure to update this thread if/when we do this.
Best,
Rune
I will update further once support is added. Thanks.
I have a build server build on Teamcity.
I'm trying to build a package using it, but I get an error.
The target "Package" does not exist in the project
I googled about this issue and found out I need to install Web Deploy. So I did. I've installed Web Deploy 3.5, but the error is still present. I've even did a reset.
This was top result on DuckDuckGo for me, so I feel this is an appropriate place to share Troy Hunt's wisdom. My "ProjectFile" was a Solution file. Solution files do not support the "Package" Target directly. My Build scripts (written in Cake in this case) were attempting to package the solution instead of the applicable projects.