New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New AutoFoq project prevents `msbuild BuildRelease.msbuild` command from working #177

Closed
adamchester opened this Issue Sep 22, 2013 · 7 comments

Comments

3 participants
@adamchester
Member

adamchester commented Sep 22, 2013

Firstly, I don't know if it's correct to run msbuild buildrelease.msbuild but it's always worked for me before. The logic behind me originally using this command that BuildRelease.ps1 does two things: increment versions and then build solutions. When I'm validating my local changes, I don't want to increment versions, but I do want to do everything else including run tests, analyse, etc.

I just updated master on my local repo, and run msbuild BuildRelease.msbuild.

I get the following error:

Build FAILED.

"C:\Files\Repos\AutoFixture-adamchester\buildrelease.msbuild" (default target) (1) ->
"C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoq.sln" (default target) (15) ->
"C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoq\AutoFoq.fsproj" (default target) (16) ->
  C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoq\AutoFoq.fsproj : error MSB4057: The target "Build" does not exist
in the project.


"C:\Files\Repos\AutoFixture-adamchester\buildrelease.msbuild" (default target) (1) ->
"C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoq.sln" (default target) (15) ->
"C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoqUnitTest\AutoFoqUnitTest.fsproj" (default target) (17) ->
  C:\Files\Repos\AutoFixture-adamchester\Src\AutoFoqUnitTest\AutoFoqUnitTest.fsproj : error MSB4057: The target "Build"
 does not exist in the project.

    0 Warning(s)
    2 Error(s)

Time Elapsed 00:00:03.44
@adamchester

This comment has been minimized.

Show comment
Hide comment
@adamchester

adamchester Sep 22, 2013

Member

Note: opening the new AutoFoq.sln in Visual Studio 2013 RC automatically runs the migration wizard. It makes some changes to the projects in question that fixed the issue.

Member

adamchester commented Sep 22, 2013

Note: opening the new AutoFoq.sln in Visual Studio 2013 RC automatically runs the migration wizard. It makes some changes to the projects in question that fixed the issue.

@adamchester

This comment has been minimized.

Show comment
Hide comment
@adamchester

adamchester Sep 22, 2013

Member

As you may have noticed in the above pull request, the problem appears to be related to VS 2013 RC, so perhaps we should wait and see what (if anything) changes in the final VS 2013 release before considering this change.

Member

adamchester commented Sep 22, 2013

As you may have noticed in the above pull request, the problem appears to be related to VS 2013 RC, so perhaps we should wait and see what (if anything) changes in the final VS 2013 release before considering this change.

@ploeh

This comment has been minimized.

Show comment
Hide comment
@ploeh

ploeh Sep 22, 2013

Member

FWIW, I usually just run the powershell script and do a git reset --hard afterwords, but explicitly running msbuild buildrelease.msbuild should be fine too.

Member

ploeh commented Sep 22, 2013

FWIW, I usually just run the powershell script and do a git reset --hard afterwords, but explicitly running msbuild buildrelease.msbuild should be fine too.

@moodmosaic

This comment has been minimized.

Show comment
Hide comment
@moodmosaic

moodmosaic Sep 22, 2013

Member

FWIW, this error message is the same with the one we had on the CI server.

It's a bit strange since I don't have VS 2013 installed (yet) and I can successfully run the build scripts.

As it looks like, there are some issues regarding the (various) install locations of the F# build targets, compiler, and runtime..

Member

moodmosaic commented Sep 22, 2013

FWIW, this error message is the same with the one we had on the CI server.

It's a bit strange since I don't have VS 2013 installed (yet) and I can successfully run the build scripts.

As it looks like, there are some issues regarding the (various) install locations of the F# build targets, compiler, and runtime..

@adamchester

This comment has been minimized.

Show comment
Hide comment
@adamchester

adamchester Sep 22, 2013

Member

Well it looks like Microsoft has baked in the upgrade logic to visual studio, so we should probably use theirs?

Regards,
Adam Chester

On 22 Sep 2013, at 5:14 pm, Nikos Baxevanis notifications@github.com wrote:

FWIW, this error message is the same with the one we had on the CI server.

It's a bit strange since I don't have VS 2013 (yet) and I can successfully run the build scripts.

As it looks like, there are some issues regarding the (various) install locations of the F# build targets, compiler, and runtime..


Reply to this email directly or view it on GitHub.

Member

adamchester commented Sep 22, 2013

Well it looks like Microsoft has baked in the upgrade logic to visual studio, so we should probably use theirs?

Regards,
Adam Chester

On 22 Sep 2013, at 5:14 pm, Nikos Baxevanis notifications@github.com wrote:

FWIW, this error message is the same with the one we had on the CI server.

It's a bit strange since I don't have VS 2013 (yet) and I can successfully run the build scripts.

As it looks like, there are some issues regarding the (various) install locations of the F# build targets, compiler, and runtime..


Reply to this email directly or view it on GitHub.

@moodmosaic

This comment has been minimized.

Show comment
Hide comment
@moodmosaic

moodmosaic Sep 22, 2013

Member

#178 is the way to go, I think :) (At least for VS 2012, VS 2013, and the CI server.)

Member

moodmosaic commented Sep 22, 2013

#178 is the way to go, I think :) (At least for VS 2012, VS 2013, and the CI server.)

@ploeh ploeh closed this in 0338d4e Sep 22, 2013

@ploeh

This comment has been minimized.

Show comment
Hide comment
@ploeh

ploeh Sep 22, 2013

Member

Resolved by #178

Member

ploeh commented Sep 22, 2013

Resolved by #178

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment