tinify / tinify-net Goto Github PK

In order to setup the automatic push to Nuget after a repository tag, I need the encrypted value of the nuget api key.

You can use this page to make it:
https://ci.appveyor.com/tools/encrypt

I am implementing in VB.net

I need a version of this DLL with a strong name key, our solution gets installed in the GAC on the server and requires it.

I Forked to create a version and deployed it and I am getting the above error.

Any ideas ?

Setup the AppVeyour build in order to:

• Apply the build number to package suffix (only on dev versions)
• Build the Pull Requests, branches and master
• Run the tests and provide feedback to github Pull Request
• If on master, run the IntegrationTests (we don't run them on PR's because secure variables could be shown by changing the config file to output the value to the build log.
• If on master, deploy the artifacts to Myget
• If a tag is present, deploy the artifacts to Nuget

Create an AppVeyor account in order to setup the continuous build of Pull Requests, master branches and releases to Nuget/Myget

With the deprecation of older .Net Frameworks and older .Net Core versions, it seems like it would be good to move the library to target .Net standard2.1. This would allow access to features from newer C# versions that would allow for some performance enhancements as well as some other code cleanup. I would be happy to take on the work.

class Exception : System.Exception {}? Really?

Create a Myget account to place the nupkg files that are generated from the master branch.
These are expecially usefull in order to be able to test the bits not yet released.
A public feed is free.

I believe the current build is failing due to an issue with an older version of the MSBuild tools that had an issue with the Remove tag in a project file. The current build is targeting 'Previous Visual Studio 2017'. With VS2022 out, it would probably be reasonable to bump the build to the current release.

I have the following code:
`public async Task<byte[]> CompressImageFromUrlAsync(string url)
{
var a1 = Tinify.CompressionCount;
var source =
await Tinify.FromUrl(url).ConfigureAwait(false); // <- CompressionCount inc here
var a2 = Tinify.CompressionCount;
var copyrighted = source.Preserve("copyright");
var a3 = Tinify.CompressionCount;
var outputBuffer = await copyrighted.ToBuffer().ConfigureAwait(false); // <- CompressionCount inc here
var a4 = Tinify.CompressionCount;

        Debug.WriteLine($"CompressImageFromUrl checkpoints: {a1}, {a2}, {a3}, {a4}");

        return outputBuffer;
    }`

It looks like my CompressionCount is being double charged. It's incremented in both the FromUrl() call and the ToBuffer() call. Unless I'm missing something.. ?

For non windows platforms there are some issues with the certificates validations on nonssl installs. There should be a workaround to skip that validation while Microsoft works on this issue