Hi Mads -
I just ran the lossy image compression on a project's image folder. It worked correctly on most files but several ended up empty, 0 bytes:
7/26/2016 4:08:58 PM: Optimized powerflex1_thumb.jpg in 0.09 seconds
Before: 11048 bytes
After: 0 bytes
Saving: 11048 bytes / 100%
That's a bit too much optimization for my taste. The download speed is great but the user experience is compromised. ;-)
I'm running VS 2015 Pro Update 3 with KB3165756 and Web Essentials 3.0.230.
I am uploading images from a webform, then resizing and saving different versions of the file. I am using BitMap images to draw new images.
Is there a way (extension) to compress images programmatically just like you do it in this tool?
I came across this great tool and thought of trying it with in my project which uses many images. Unfortunately after installing it on any image if i run this the visual studio crashing. It seems its working for others well. let me know if any body know the reason for this crash?
Hello, the tool works very nice! I only don't see the output from it in the Output window. The dropdown also doesn't show an option named 'Image Optimizer'. Am I overlooking something?
I'm using VS2015 RTM.
Thanks in advance!
this toll is awesome. They save me a lot of time.
But unfortunately today it just stop working
I tried remove and install again, restart VS but noting help. Pls tell me if someone have solution for this problem.
Message which I got:
------ Image optimization started -----
The remote name could not be resolved: 'smushit.eperf.vip.ac4.yahoo.com'
D:\Current\images\ActivationInstructions01.png - using http://smushit.com
1 skipped. 0 optimized. Total savings 0%
------ Image optimization finished -----
I am having this same issue ("An exception occurred during a WebClient request"), but I don't believe it is a firewall problem. I watched the request/response in Fiddler, and it very clearly gets a response of 200 with a JSON object in the payload describing how much the image was "smushed" and where the new image resides. I don't see a follow-up request that actually retrieves the smushed image, though, so I'm guessing this is where the error is occurring. Any ideas?