deadlydog

personal statement

My name is Daniel Schroeder and I love to create software for other developers, and software that increases efficiency and productivity. Automate everything!

activity stream

January 22, 2017 - New-NuGetPackage PowerShell Script: Committed ad18a705cf6b8cf4318ca2ade0a9d330e4fc4f10, Pushed new version of NuGet package to gallery.

January 22, 2017 - New-NuGetPackage PowerShell Script: Committed 17cfc44f7a12e7580b34461f05a79d7a8d7cc6b4, - Now include the default Push source in the command to NuGet.exe when user does not specify one (as it's now a required parameter)

January 22, 2017 - New-NuGetPackage PowerShell Script: Committed 3044020b448fd9b6dfea531bc9c26b53cbf6540c, Updating version number of script since adding functionality to force NuGet.exe to output English.

January 22, 2017 - New-NuGetPackage PowerShell Script: Committed 3044020b448fd9b6dfea531bc9c26b53cbf6540c, Updating version number of script since adding functionality to force NuGet.exe to output English.

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: Build process failed: Could not determine where NuGet Package was create ...

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: Getting "Could not determine where NuGet Package was created to" error when using custom .nuspec

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: Private NuGet servers

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: On Compilation despite error package created

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: Doesn't work with Windows 10 Universal Class Libraries

January 22, 2017 - New-NuGetPackage PowerShell Script: Commented work item: Build process failed: Could not determine where NuGet Package was create ...