Skip to content
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.

Sign up for GitHub

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

Jump to bottom

xproj to csproj migration missing BaseIntermediateOutputPath and OutputPath #567

Closed
mohamedmansour opened this issue Mar 23, 2017 · 3 comments
Closed

xproj to csproj migration missing BaseIntermediateOutputPath and OutputPath #567

mohamedmansour opened this issue Mar 23, 2017 · 3 comments

Comments

@mohamedmansour
Copy link

Hello, I just migrated from xproj to csproj from the Visual Studio 2017 process. And the migration missed two things:

  • OutputPath
  • BaseIntermediateOutputPath

When I filled them in manually, the OutputPath functioned correctly but the BaseIntermediateOutputPath didn't work. Who can help out?

<OutputPath>..\bin\</OutputPath>
<BaseIntermediateOutputPath Condition="'$(BaseIntermediateOutputPath)'=='' ">..\obj</BaseIntermediateOutputPath>
@leecow
Copy link
Member

leecow commented Mar 23, 2017

Hi @mohamedmansour - you can use http://landinghub.visualstudio.com/migrate-dotnetcore to connect with folks closest to migration.

@dsplaisted
Copy link
Member

See dotnet/msbuild#1603 (comment) for information on how to do this correctly.

@Petermarcu
Copy link
Member

I'm going to close this for now. You can get support for migrate here: http://landinghub.visualstudio.com/migrate-dotnetcore and it looks like @dsplaisted has pointed to the way to handle this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mohamedmansour @dsplaisted @leecow @Petermarcu