search

coapp / coapp.powershell

ClrPlus Signing
52 stars 43 forks source link

Dynamic only packet not created when the word "static" is found into .autopkg file #123

Closed StefanoBettega closed 8 years ago

StefanoBettega commented 8 years ago

Hello, I would like to report a strange behavior of CoApp Powershell Developer Tools Version: 1.23.521.0.

We are evaluating NuGet package usage for internal DLL/LIB development, and CoApp as tool to pack native libraries. Can't actually upgrade to the latest developed version (2.x) as package overlay is not suitable for our purposes, it can't be disabled on last downloadable package and sources downloaded from GitHub does not compile.

For testing purposes we created some .LIB, .DLL and mixed .LIB/.DLL projects, that will be referenced from a test client through a wrapper DLL. This DLL will be the global NuGet package consumed by the client test application.

I'm using the following script to pack the DLL (had to change extension to .txt to upload file): library.autopkg.txt

If I launch Write-NuGetPackage on it this is the result:

Write-NuGetPackage : Unmatched configuration choice 'Static At D:\tmp\final_test\aggregator_dll\nuget\buildAndPack.ps1:2 char:1

  • Write-NuGetPackage .\library.autopkg
  • 
- CategoryInfo          : NotSpecified: (:) [Write-NuGetPackage], ClrPlusException
- FullyQualifiedErrorId : ClrPlus.Core.Exceptions.ClrPlusException,CoApp.Powershell.Commands.WriteNuGetPackage

In the .autpkg file the only reference to "static" is at line 69, into the description of the package. If I remove that "static" replacing it with LIB, packages are correctly created.

Please note that the same error occours if I write static into a commented line, or if I write any word that contains static in the middle (for instance a nonsense word like "astatica").

StefanoBettega commented 8 years ago

Using the last repository version this issue is no more present, but it seems that creating a static only or a dynamic only package is not supported.