Soundman32

Same here... ``` FFImageLoading.Exceptions.DownloadAggregateException: One or more errors occurred. (Headers timeout) ---> FFImageLoading.Exceptions.DownloadHeadersTimeoutException: Headers timeout at FFImageLoading.Cache.DownloadCache.DownloadAsync (System.String url, System.Threading.CancellationToken token, System.Net.Http.HttpClient client, FFImageLoading.Work.TaskParameter parameters, FFImageLoading.DownloadInformation downloadInformation) [0x007c3] in C:\projects\ffimageloading\source\FFImageLoading.Common\Cache\DownloadCache.cs:195...

> Here is a "solution" that works fine. Ignoring certificate validation errors is a workaround, but it's not really solving the problem, it's just bypassing security.

I don't think the documentation specifically shows how to _display_ a formatted date. It has "31 3 1980" in the examples, but this is not specifically spelt out in [date...

"Effective date must have a day that is a number" - why are you allowing them to type in non-numbers in the first place?

Is it still in beta?

I have this too. Previous migration is created without a problem, but if I immediately add another migration (with zero change), then this exception is thrown.

I tried with -verbose and got this: _No application service provider was found. Finding DbContext classes in the project... Found DbContext 'ApplicationDbContext'. Using DbContext factory 'DesignTimeDbContextFactory'. Using context 'ApplicationDbContext'. Finding...

I think I've found the problem. I changed my code from: builder.Property(p => p.ConcurrencyToken) .HasColumnName("concurrencyToken"); to builder.Property(p => p.ConcurrencyToken) .IsRowVersion() .HasColumnName("concurrencyToken"); And then I can no longer create any migrations...

More info: My concurrency token type was `byte[]`. This generated a migration that failed when looking up the mapping type. I changed my concurrency token to DateTime, and it all...

Just to add another scenario. The Oracle system I'm currently working on, has primary keys of NUMBER(10) and foreign keys of NUMBER(19). This is currently worked around because it's .NET...