3 ms·

What sort of problems have you had with Visual Studio 2015? I've been using it for a while, and have found it (mostly) pretty nice to work with. I can't say I

What sort of problems have you had with Visual Studio 2015? I've been using it for a while, and have found it (mostly) pretty nice to work with. I can't say I've worked with Entity Framework before, but I've always believed it to be an abomination. Looks like I'll continue to avoid it.

soundwave106 10y ago
I wouldn't call it an abomination per se, but it is a very heavy ORM in my opinion. It works well for CRUD, but can be a dog in performance for very complex queries. (These type of queries can be offloaded into stored procs, of course... but inexperienced developers might "forge ahead" and create low-performance code in EF, unfortunately...) From my perspective, my biggest problem with EF is that Microsoft seemed to half-abandon any concept of "light weight data access layer" (like the previous Linq to SQL), and pushed Entity Framework as The One True Way to call the data layer. EF is definitely suitable for Microsoft's "core audience" of large, enterprise-y CRUD apps, but IMHO it's rather heavy for a simple web page with a few data calls. Fortunately there's things like Dapper that are great for small quick apps.
- WorldMaker 10y ago
  EF Core is much lighter-weight and tries to be a best of both worlds, pushing some of the heavier stuff into extensions/plugins rather than out of the box. This is why some of the fans of the heavy old EF dislike EF Core, but I'm happy EF Core takes an overall lighter-weight approach.
- douche 10y ago
  There's no reason you can't keep using Linq-to-SQL. It's not the new hotness, but it still works just fine. If you're doing SQL Server, I wouldn't see any reason not to use it. I may have Stockholm syndrome, though.
smt88 10y ago
Builds randomly hang, dependencies disappear when changing branches, weird errors that tell me to reinstall the IDE... everyone on my team has them. We now have a VM image that we launch in the cloud whenever we need to reset VS. It's ridiculous.
- WorldMaker 10y ago
  Fascinating. Are y'all using ReSharper by any chance? Every time I've seen those sorts of problems in VS and helped colleagues diagnose them it has been ReSharper causing them directly or indirectly. I'm not a fan of ReSharper, never install it, and it fascinates me how often VS gets blamed for ReSharper's bad behavior.
  - smt88 10y ago
    Not using ReSharper anymore. I absolutely loved it when I used it though. I'm not sure if I caused any problems or not, but I'm not taking a chance anymore.

soundwave106 10y ago

I wouldn't call it an abomination per se, but it is a very heavy ORM in my opinion. It works well for CRUD, but can be a dog in performance for very complex queries. (These type of queries can be offloaded into stored procs, of course... but inexperienced developers might "forge ahead" and create low-performance code in EF, unfortunately...) From my perspective, my biggest problem with EF is that Microsoft seemed to half-abandon any concept of "light weight data access layer" (like the previous Linq to SQL), and pushed Entity Framework as The One True Way to call the data layer. EF is definitely suitable for Microsoft's "core audience" of large, enterprise-y CRUD apps, but IMHO it's rather heavy for a simple web page with a few data calls. Fortunately there's things like Dapper that are great for small quick apps.

WorldMaker 10y ago
EF Core is much lighter-weight and tries to be a best of both worlds, pushing some of the heavier stuff into extensions/plugins rather than out of the box. This is why some of the fans of the heavy old EF dislike EF Core, but I'm happy EF Core takes an overall lighter-weight approach.
douche 10y ago
There's no reason you can't keep using Linq-to-SQL. It's not the new hotness, but it still works just fine. If you're doing SQL Server, I wouldn't see any reason not to use it. I may have Stockholm syndrome, though.

smt88 10y ago

Builds randomly hang, dependencies disappear when changing branches, weird errors that tell me to reinstall the IDE... everyone on my team has them. We now have a VM image that we launch in the cloud whenever we need to reset VS. It's ridiculous.

WorldMaker 10y ago
Fascinating. Are y'all using ReSharper by any chance? Every time I've seen those sorts of problems in VS and helped colleagues diagnose them it has been ReSharper causing them directly or indirectly. I'm not a fan of ReSharper, never install it, and it fascinates me how often VS gets blamed for ReSharper's bad behavior.
- smt88 10y ago
  Not using ReSharper anymore. I absolutely loved it when I used it though. I'm not sure if I caused any problems or not, but I'm not taking a chance anymore.