-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Cleanup project #2182
Cleanup project #2182
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have a Windows build environment, so I can't test the ps1, but the rest of it looks fine.
Does the new csproj in #2177 need any updates along these lines?
I'll check and make a PR on you repo is it needs some changes |
Update to MSBuildToolsPath Update builds Format App.config Fix included version files Cleanup last bits in project files
Cleaned up last bits and updated some nuget packages. |
Do you want another reviewer to take a look? I'd be fine with merging this, but I don't want to short-circuit the review process if that's not how things are supposed to be done. |
I definitely want someone to review the powershell build script before merging this. |
build.ps1
Outdated
$CakeVersion = (Select-Xml -Xml ([xml](Get-Content $PackagesConfigFile)) -XPath "//package[@id='Cake'][1]/@version").Node.Value | ||
$CakeExe = "${PackagesDir}/Cake.${CakeVersion}/Cake.exe" | ||
$CakeExe = "${PackagesDir}\Cake.${CakeVersion}\Cake.exe" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since Windows is fine with the forward slashes, but Linux treats them as escape characters, it makes sense to me to use forward slashes to make the two build scripts easy to keep in sync. Is there a particular reason to switch to backslashes other than "that's how Windows users see paths?"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, this change isn't really necessary as both forward- and backslashes are valid path separators on Windows.
Reverted the slashes in the build script. Unless someone wants some more changes, this is ready to merge. |
Cleaned up the repo by removing unused references. Also fixed the paths in the powershell build script.
I need some feedback on the powershell build script.
Changes:
.gitattributes
and.gitignore
files, so we use the global ones.gitattributes
App.config
'sToolsVersion
to 15.0MSBuildToolsPath
, asMSBuildBinPath
was deprecatedInclude
's alphabeticallyLICENSE
toLICENSE.md
log4net
Newtonsoft.Json
Microsoft.CSharp
CommandLineParser
to 1.9.71.2 (now uses .NET 4.5)TxFileManager
to use .NET 4.5SharpZipLib
to 0.86.5.1CommandLine
ChinhDo.Transactions.FileManager
System.*
referencesMicrosoft.CSharp
System.*
referencesuserInstalled
tag, as this was deprecated 2 years agoSharpZipLib
to 0.86.5.1SharpZipLib
to 0.86.5.1Moq
to 4.7.145NUnit
to 3.9.0System.Configuration
.version
files