Weekly meeting notes

#CoApp meeting notes

NuGet 2.5 released. This version has built-in native library support.
CoApp packaging tools officially generally available. Build tools still under development.
During the meeting, various minor bugs were discovered in the output from the CoApp tools. These were corrected each time immediately upon discovery.
Documentation is readily available at http://coapp.org/pages/reference.html and http://coapp.org/pages/tutorials.html. Typos and corrections may be pointed out in the comments, via email, or submitted via pull requests.
This weeks meeting extended for many hours beyond its normal conclusion, with all additional time being spent in coaching others through the package building process.

Documentation is presently in progress in anticipation for the release of NuGet 2.5 and GA of native package building.
AutoPackage can now also generate symbol/source NuGet packages in parallel with and separate from the binary and library package files.
PTK development will resume once sufficient documentation is available to enable general usage of AutoPackage.
AutoBuild development will resume once PTK is feature complete.
OuterCurve is hosting a conference on May 8 & 9. A Hackathon will take place on May 10 & 11. We expect the Hackathon to be a prime opportunity to build packages with various community members.

We are informed that the new version of Nuget will hit public release sometime in the next two weeks.
We are still working on documentation and initial packages.
AutoPackage: Some syntax items simplified. Implicit rules and auto-included definitions expanded.

Additional example packges available online.
New syntax in AutoPackage to allow for recursive binary dependencies. This correlates to a newly established standard for releasing native nuget packages in two parts: 'developer' package and 'redist' package.
Pivots not already directly mapped to Visual Studio properties now have a UI in Visual Studio for making selections.
Possible complications raised regarding the packaging and distribution of static link libraries require additional conversations with the VC team and possibly the NuGet team.

AutoPackage is feature-complete and a temorary installer has been made for it. It is implemented as a PowerShell cmdlet and will be documented as able. At this time we are treating it as an RC build.
A preliminary zlib nuget package has been successfully made and presented in a meeting with the NuGet team. They appeared quite excited after being shown a direct comparison between using a NuGet-Native package and a the existing process for importing and linking native libraries in Visual Studio.
The DiffVHD library is being rolled into the ClrPlus toolbox as a critical component of PTK-next.
The VHD PowerShell provider is being implemented as time allows in anticipation of potential use by PTK-next.
AutoBuild development has been placed on temporary hold while packaging methods and procedures get ironed out.

PropertySheet format appears to be complete and the library for its use is available on NuGet.
The implementation to generate MSBuild property/target files for inclusion in NuGet packages now appears to be feature complete.
Planning to work on constructing AutoPackage and a temporary installer for the aforementioned by early next week.
DiffVHD library and cmdlets have been publicly released as v1.0. Community members have expressed interest and will report any issues that evaded the QA trials.
A request was made for a Powershell provider for loading VHD (and related) files as drives in powershell. This possibility is being investigated for practicality.
The AutoBuild script-service is undergoing a scheduled major revision for use with the new development tools. New release will be v2.0 and is not expected to be directly compatable with v1.0.

Provide feedback