Skip to content

Fix how msbuild condition is created based on target frameworks - #3943

Merged
forki merged 2 commits into
fsprojects:masterfrom
mk185147:msbuild-condition-fix
Nov 17, 2020
Merged

Fix how msbuild condition is created based on target frameworks#3943
forki merged 2 commits into
fsprojects:masterfrom
mk185147:msbuild-condition-fix

Conversation

@mk185147

Copy link
Copy Markdown
Contributor

this is fix of #3939

The problem was that when you used in proj file e.g. target framework net5.0-windows it was not matching msbuild condition '$(TargetFramework)' == 'net5.0-windows7.0' which was created for the net5.0-windows target framework.

Generally, there are many ways how to write the same TargetFramework. Hence, I switched to the form like "($(TargetFrameworkIdentifier) == '.NETCoreApp' And ($(TargetFrameworkVersion) == 'v5.0' And '$(TargetPlatformIdentifier)' == 'Windows'))" like it was done on other place in Paket

@forki

forki commented Nov 16, 2020

Copy link
Copy Markdown
Member

the travis is red. unfortunately

@mk185147

Copy link
Copy Markdown
Contributor Author

@forki I checked it and it seems like some infrastructure problem:
EXEC : The remote server returned an error : (429) too many requests. (Github - cached) [/home/travis/build/fsprojects/Paket/src/Paket/Paket.fsproj]

@forki forki closed this Nov 16, 2020
@forki forki reopened this Nov 16, 2020
@forki

forki commented Nov 16, 2020

Copy link
Copy Markdown
Member

ok let's rerun this

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants