jcreamer898
commented
10 years ago I'll have a look. — Sent from Mailbox
On Sat, Jul 5, 2014 at 12:38 PM, Douglas Neiner notifications@github.com wrote:
The AmplifyJS Nuget package has been needing to be updated with the latest code for a while. This request adds the
nuspecfile into Source control (as well as the associated readme) and maps the built output of Amplify to match the existing Nuget structure. The only new addition is theamplifyfolder with individual components inside. The finished package files look like this:/content /Scripts /amplify amplify.core.js amplify.core.min.js amplify.request.js amplify.request.min.js amplify.store.js amplify.store.min.js amplify-vsdoc.js amplify.js amplify.min.js GPL-LICENSE.txt MIT-LICENSE.txt README.txtAfter discussing with @elijahmanor I opted to not put the
amplify.jsandamplify.min.jsfiles in the/amplifydirectory so those upgrading from an older version of the package wouldn't have trouble with the files moving. If @jcreamer898 or anyone else with more experience in .NET and Nuget could chime in on this commit, it would be appreciated! You can merge this Pull Request by running: git pull https://github.com/appendto/amplify nuget Or you can view, comment on it, or merge it online at: https://github.com/appendto/amplify/pull/100 -- Commit Summary --
Added updated Nuget package spec and Nuget readme file -- File Changes -- A AmplifyJS.nuspec (33) A nuget-readme.txt (24) -- Patch Links -- https://github.com/appendto/amplify/pull/100.patch https://github.com/appendto/amplify/pull/100.diff
Reply to this email directly or view it on GitHub: https://github.com/appendto/amplify/pull/100
dcneiner
The AmplifyJS NuGet package has been needing to be updated with the latest code for a while. This request adds the
nuspecfile into Source control (as well as the associated readme) and maps the built output of Amplify to match the existing NuGet structure. The only new addition is theamplifyfolder with individual components inside. The finished package files look like this:After discussing with @elijahmanor I opted to not put the
amplify.jsandamplify.min.jsfiles in the/amplifydirectory so those upgrading from an older version of the package wouldn't have trouble with the files moving.If @jcreamer898 or anyone else with more experience in .NET and NuGet could chime in on this commit, it would be appreciated!