Skip to content

Change project file condition handling to be case-insensitive - #1890

Merged
forki merged 4 commits into
fsprojects:masterfrom
allykzam:master
Aug 26, 2016
Merged

forki merged 4 commits into
fsprojects:masterfrom
allykzam:master

Conversation

@allykzam

Copy link
Copy Markdown
Contributor

Had to fiddle with the test a bit because one of the test projects uses the given build configuration as part of its output path, but this should fix #1889.

Test fails currently because output path detected does not match
configuration name perfectly
`Project1.fsprojtest` specifies its output path as
`bin\$(Configuration)\`, which means that the exact configuration passed
in will be the result. However, the other test project files have
hard-coded output paths. This handles both cases.
@allykzam

Copy link
Copy Markdown
Contributor Author

Uhh, soo, travis is out of disk space?

Per @cloudRoutine, it's faster than InvariantCultureIgnoreCase is, and
still makes this code case-insensitive.
@forki

forki commented Aug 25, 2016

Copy link
Copy Markdown
Member

I'm not sure with which person I have to sleep with to get this bigger.

@forki

forki commented Aug 26, 2016

Copy link
Copy Markdown
Member

regarding mono build issue: travis-ci/travis-ci#6524

@forki
forki merged commit 0ddc394 into fsprojects:master Aug 26, 2016
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.

paket pack buildconfig is case sensitive

2 participants