Update example code on README.md about photosauce HOT 9 CLOSED

Thanks for the feedback, but I'm not following. The sample code is valid.

Are you saying the sample made you think you could only output to a file, or did you have a problem running it?

from photosauce.

Yes I get an error stating that I need to be using Stream and not FileStream. I copied the example on the readme and it gives me that same error.

from photosauce.

Stream is an abstract class, so you can't possibly pass one to anything. You need to use a concrete implementation of Stream, and FileStream is one such implementation. I can't imagine what's giving you the error you mentioned, unless you're using some other class called FileStream and not a System.IO.FileStream.

from photosauce.

I'm using System.IO.FileStream and still seeing that error, I'm attaching what VS is displaying to me.

from photosauce.

I'm baffled. The first overload in that list matches the method it says it can't resolve. I've just tried the example code in a new project, and it's working as expected. Here's my VS (tried it in 2015 and 2017, .NET 4.6 and .NET Core 1.1) showing it has resolved the correct (string, Stream, ProcessImageSettings) overload with those arguments.

I did find a problem with the nuget package, though. It has a frameworkAssembly reference to System.Runtime, which might be causing a conflict between versions of some of the System classes. If you're on the full .NET Framework, can you check your project references and see if System.Runtime is there? If you see it, try removing it.

from photosauce.

I do see System.Runtime in there, but it's not letting me remove it. I'm using .NET core 1.1 btw

from photosauce.

Ah, ok. it needs to be there for .NET Core. I'm still investigating. You on VS 2017?

from photosauce.

Yes, so interesting enough, it builds without error but I still see the error. I'm curious if ReSharper is the problem here. I tried it on another copy of VS and it seems to be fine.

I'm guessing ReSharper is just being super picky or maybe I discovered a bug :)

from photosauce.

Good to know. I reckon it's a conflict with resolving those System classes, but I'm not sure if ReSharper is at fault or if I've done something strange. I'll do a bit more testing. Thanks for the heads-up anyway.

from photosauce.