Closed ajevansch closed 7 years ago
@ajevansch good catch!! Thank you!
@ricardopolo No problem; is there a reason why the new NuGet version (2.1.109) would not be available for consumption via NuGet yet?
The appveyor build indicates it is indeed deploying the nuget package: https://ci.appveyor.com/project/tulpep/active-directory-object-picker/build/2.1.109#L158
I can see it. There is a problem with the Digital Certificate that was expired a few days ago.
I will resolve this in about 4 days. Thanks for your patience.
At the last commit that was made to change the .NET version to 3.5, the Assembly Name was changed to remove the 'Tulep' prefix.
This broke the NuGet package build - if you look at the AppVeyor output the Nuget package is not being updated.
This change just updates the powershell build file and the NuGet spec so that it will build correctly.