Closed mani0070 closed 9 years ago
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442
I haven't tested OneBuild with Azure Cloud projects (.ccproj), if you take a look at the logs you'll see it's looking here for the targets, which suggests it's trying the VS 2012 path:
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found.
You will also see I've hardcoded a default msbuildPath in the module that does the compilation:
https://github.com/lholman/OneBuild/blob/master/tools/powershell/modules/New-CompiledSolution.psm1
Maybe overriding that may work (aren't MS starting to ship msbuild with VS rather than the .NET framework now)?
A question for you, are these targets shipped with VS2013, or a separate install?
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 14:58 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442 — Reply to this email directly or view it on GitHub.=
OK sure.
Yes I think they do ship with visual studio.
I didn't install any tools other than visual studio 2013. BTW when I compile in visual studio 2013 it just works. Will catch up on Tuesday to make it more slicker
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 18:16 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I may split this out in to another issue as the original is solved
That said, I also haven't tested OneBuild with Azure Cloud projects (.ccproj), if you take a look at the logs you'll see it's looking here for the targets, which suggests it's trying the VS 2012 path:
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found.
You will also see I've hardcoded a default msbuildPath in the module that does the compilation:
https://github.com/lholman/OneBuild/blob/master/tools/powershell/modules/New-CompiledSolution.psm1
Maybe overriding that may work (aren't MS starting to ship msbuild with VS rather than the .NET framework now)?
A question for you, are these targets shipped with VS2013, or a separate install?
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 14:58 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64993967
It'll probably be enough to get the right path to msbuild then, you can override it by parsing in a parameter value when we call that module from OneBuild.build.ps1 in the Invoke-Compile task. Although upgrading OneBuild will obviously over write any changes.
If that works I'll think about a way to get the appropriate msbuild path dependent on which version of VS is installed.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 19:33 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
OK sure.
Yes I think they do ship with visual studio.
I didn't install any tools other than visual studio 2013. BTW when I compile in visual studio 2013 it just works. Will catch up on Tuesday to make it more slicker
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 18:16 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I may split this out in to another issue as the original is solved
That said, I also haven't tested OneBuild with Azure Cloud projects (.ccproj), if you take a look at the logs you'll see it's looking here for the targets, which suggests it's trying the VS 2012 path:
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found.
You will also see I've hardcoded a default msbuildPath in the module that does the compilation:
https://github.com/lholman/OneBuild/blob/master/tools/powershell/modules/New-CompiledSolution.psm1
Maybe overriding that may work (aren't MS starting to ship msbuild with VS rather than the .NET framework now)?
A question for you, are these targets shipped with VS2013, or a separate install?
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 14:58 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64993967 — Reply to this email directly or view it on GitHub.=
I like that idea of getting msbuild path. Thanks . sorry for bugging. :-)
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 19:41 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
It'll probably be enough to get the right path to msbuild then, you can override it by parsing in a parameter value when we call that module from OneBuild.build.ps1 in the Invoke-Compile task. Although upgrading OneBuild will obviously over write any changes.
If that works I'll think about a way to get the appropriate msbuild path dependent on which version of VS is installed.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 19:33 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
OK sure.
Yes I think they do ship with visual studio.
I didn't install any tools other than visual studio 2013. BTW when I compile in visual studio 2013 it just works. Will catch up on Tuesday to make it more slicker
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 18:16 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I may split this out in to another issue as the original is solved
That said, I also haven't tested OneBuild with Azure Cloud projects (.ccproj), if you take a look at the logs you'll see it's looking here for the targets, which suggests it's trying the VS 2012 path:
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found.
You will also see I've hardcoded a default msbuildPath in the module that does the compilation:
https://github.com/lholman/OneBuild/blob/master/tools/powershell/modules/New-CompiledSolution.psm1
Maybe overriding that may work (aren't MS starting to ship msbuild with VS rather than the .NET framework now)?
A question for you, are these targets shipped with VS2013, or a separate install?
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 14:58 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64993967 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64997129
If you could give it a go by changing it to what you think it should be and letting me know if it works that'd be great.
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 19:49 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I like that idea of getting msbuild path. Thanks . sorry for bugging. :-)
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 19:41 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
It'll probably be enough to get the right path to msbuild then, you can override it by parsing in a parameter value when we call that module from OneBuild.build.ps1 in the Invoke-Compile task. Although upgrading OneBuild will obviously over write any changes.
If that works I'll think about a way to get the appropriate msbuild path dependent on which version of VS is installed.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 19:33 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
OK sure.
Yes I think they do ship with visual studio.
I didn't install any tools other than visual studio 2013. BTW when I compile in visual studio 2013 it just works. Will catch up on Tuesday to make it more slicker
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 18:16 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I may split this out in to another issue as the original is solved
That said, I also haven't tested OneBuild with Azure Cloud projects (.ccproj), if you take a look at the logs you'll see it's looking here for the targets, which suggests it's trying the VS 2012 path:
The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found.
You will also see I've hardcoded a default msbuildPath in the module that does the compilation:
https://github.com/lholman/OneBuild/blob/master/tools/powershell/modules/New-CompiledSolution.psm1
Maybe overriding that may work (aren't MS starting to ship msbuild with VS rather than the .NET framework now)?
A question for you, are these targets shipped with VS2013, or a separate install?
ll
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 30/11/2014 14:58 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
I'm using 2013 and is there any way to pull targets automatically from visual studio into msbuild If not available?
--- Original Message ---
From: "Lloyd Holman" notifications@github.com Sent: 30 November 2014 14:48 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Manimaran Chandrasekaran" mani@dinventive.com Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
Hmmm, what version of Visual Studio are you running out of interest, 2012? Also, it would seem those targets aren't available from a standard command prompt.
-----Original Message----- From: "Manimaran Chandrasekaran" notifications@github.com Sent: 29/11/2014 07:56 To: "lholman/OneBuild" OneBuild@noreply.github.com Cc: "Lloyd Holman" lloyd.holman@datumgenerics.net Subject: Re: [OneBuild] Set-BuildNumberWithGitCommitDetail - Failed (#12)
This second option works for me .. but the next issue is targets are not available and failing
Do we have some nicer way to make this happen.
WARNING: Setting [minor] version number to: 1.
Build FAILED. 5 tasks, 2 errors, 3 warnings 00:00:01.9437807
Error compiling solution file: C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln.
Whilst executing MsBuild for solution file C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln, MsBuild.exe
exited with error message: Microsoft (R) Build Engine version 4.0.30319.33440 [Microsoft .NET Framework, version 4.0.30319.34014] Copyright (C) Microsoft
Corporation. All rights reserved. Build started 29/11/2014 07:53:27. 1>Project "C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1.sln" on node 1 (ReBuild;Clean target(s)). 1>ValidateSolutionConfiguration: Building
solution configuration "Debug|Any CPU". 1>Project "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1.sln"
(1) is building "C:\Users\mani_000\Documents\Visual Studio 2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj" (2) on node 1
(Rebuild target(s)). 2>C:\Users\mani_000\Documents\Visual Studio
2013\Projects\AzureCloudService1\AzureCloudService1\AzureCloudServiceACLDemo.ccproj(63,3): error MSB4019: The imported project "C:\Program Files
(x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.5\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the
r
n ...
Regards, Mani +447896806199
Sent from Surface
From: Lloyd Holman Sent: Friday, 28 November 2014 16:03 To: lholman/OneBuild Cc: Manimaran Chandrasekaran
Ahhh, I think this is an edge case when you have no git repo in the directory, can you try this? c:[path-to-solution]>\git init c:[path-to-solution]>\Build.bat
If that still doesn't work then try making a new commit locally, i.e. c:[path-to-solution]>\git add --all c:[path-to-solution]>\git commit -am "Initial commit" c:[path-to-solution]>\Build.bat
Could you let me know if either work, I'll put a test in around the Set-BuildNumberWithGitCommitDetail.psm1 module to check for a git repo first and give a better Error if it turns out to be the above.
— Reply to this email directly or view it on GitHub. — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64987442 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64993967 — Reply to this email directly or view it on GitHub.=
Reply to this email directly or view it on GitHub: https://github.com/lholman/OneBuild/issues/12#issuecomment-64997129 — Reply to this email directly or view it on GitHub.=
@mani0070 did you get any success with overriding the path to MSBuild? If that works I'll put some tests around the New-CompiledSolution module and identify the latest version of MSBuild installed.
Note: I've split the original issue with GIT out to https://github.com/lholman/OneBuild/issues/13
The full story for the location of MSBuild can be found here http://blogs.msdn.com/b/visualstudio/archive/2013/07/24/msbuild-is-now-part-of-visual-studio.aspx my summary below.
Prior to Visual Studio 2013 MSBuild was part of the .NET Framework. The MSBuild [ToolsVersion] matches the [major].[minor] assembly version for the corresponding .NET Framework versions 2.0.x, 3.5.x and 4.0.x (including 4.5.x), e.g.
Locations are as follows
From Visual Studio 2013 MSBuild is now shipped and versioned with Visual Studio, jumping to assembly version 12.0 (from 4.0) with Visual Studio 2013, e.g.
Locations are as follows
As later versions of MSBuild are no longer shipped with Visual Studio we need to install it, there are two options:
Thankfully someone has wrapped the second option and published Microsoft Build Tools 2013 to Chocolatey so you can also do C:\>https://chocolatey.org/packages/microsoft-build-tools
.
There seems to be no official standalone download of Microsoft Build Tools 2014+ which is a bit of a concern for those of us that don't want a fully fledged Visual Studio IDE install on our non-MS build servers/agents.
A bit of clarity on how OneBuild relies on MSBuild. MSBuild is referenced in one place within the New-CompiledSolution
module, more specifically as part of the Invoke-MsBuildCompilationForSolution function, only two targets of MSSBuild are used, namely Clean
and Rebuild
. From a build pipeline perspective these functions are executed from OneBuilds Invoke-Build Invoke-Compile task
...
$output = & $msbuildPath $solutionFile /t:ReBuild /t:Clean /p:Configuration=$configMode /p:PlatformTarget=AnyCPU /m 2>&1
...
That's it, OneBuild doesn't use MSBuild for anything more than as a convenience allowing us to target the compilation of a solution file.
Building on the existing Invoke-Compile convention within the OneBuild documentation OneBuild and more specifically the New-CompiledSolution
module will attempt to identify the appropriate version of MSBuild to use, as follows:
Feature: Compilation
In order to compile a Visual Studio solution
As a user of OneBuild
I want OneBuild to perform compilation with no configuration
Scenario: Select the correct MSBuild version to use for compilation
Given There is one Visual Studio solution file named "ASolutionFile.sln" in the "$OneBuildInstallationPath"
And "$OneBuildInstallationPath\ASolutionFile.sln" contains a reference to the project "$OneBuildInstallationPath\ConsoleApplication\ConsoleApplication.csproj"
And "ConsoleApplication\ConsoleApplication.csproj" has a property "ToolsVersion" in the "Project" element set to the value "4.0"
When OneBuild invoke MSBuild
Then MSBuild is executed from the location "C:\Windows\Microsoft.NET\Framework64\4.0\MSBuild.exe"
Scenario: Select a Visual Studio solution file to compile
Given There is one Visual Studio solution file named "SolutionFile.sln" in the "$OneBuildInstallationPath"
And There is one Visual Studio solution file named "ASolutionFile.sln" in the "$OneBuildInstallationPath"
When OneBuild invokes MSBuild
Then MSBuild should attempt to compile "$OneBuildInstallationPath\ASolutionFile.sln"
For now and until we know any better, a few assumptions will be made.
Closed as part of https://github.com/lholman/OneBuild/releases/tag/v1.1
Do we have some nicer way to make this happen, targets are not available and failing