-
I ran into a real head scratcher today, and I think I figured out the root cause. I wrote up the whole issue at https://github.com/IntelliTect/Coalesce/issues/25, which I'd encourage a read through of…
-
- Doesn't appear to be used by Coalesce
- likely not by anything else (project is outdated)?
- Since Coalesce doesn't rely on it, if we want to keep it, it should probably reside in our IntelliTect…
-
There is an issue in both EF Core & Linq.Dynamic (https://github.com/StefH/System.Linq.Dynamic.Core), but arguably Linq.Dynamic is more at fault than EF Core, since it is (in part) designed to work wi…
-
Let's rename the live branch to something like "Production" and have it be consistent with other GitHub hosted websites in the IntelliTect organization. See https://github.com/IntelliTect/CI/issues/2…
-
_From @MarkMichaelis on January 17, 2017 22:4_
After migrating a solution, the following warning appeared:
`Severity Code Description Project File Line Suppression State
Warning MSB3270 There was a…
-
After migrating a solution, the following warning appeared:
`Severity Code Description Project File Line Suppression State
Warning MSB3270 There was a mismatch between the processor architecture of …
-
The output of the migration report is confusing if the only project fails:
```
~/Documents/git/Coalesce/src/Coalesce.Web (master)
$ dotnet migrate -s
Project Coalesce.Web migration failed (C:\User…
-
Repro: https://github.com/gulbanana/repro-netstandard-httpclient
These two projects were created with VS2017 RC Refresh. Neither contains any meaningful code. `netstdlib` builds ok, but `netfxlib` fa…
-
We should consider a different name so that the project name provides at least a vague idea of what the class does.
Perhaps rename the repo to something like IntelliTect.CommandLineUtils and the class…
-