4 ms·

It really depends on how much you are dependent on third parties that don't update. I've been stalled at 3.5 then 4.5 waiting on my dependencies in the past.

Someone1234 8y ago
Just curious what dependencies are causing you so many issues?
- thrower123 8y ago
  Skype for Business SDKs, primarily. That is basically our business. Teams is the new hotness, but doesn't have any Api access.
  - Someone1234 8y ago
    Makes sense. They keep claiming Skype for Business is dead, but Teams in my opinion is very far away from being a realistic replacement. I've not been very impressed with the desktop application at all (although the web-site is "fine").
    - jgalentine007 8y ago
      I have deployed teams in 'island' mode for our org and I'm a bit disappointed with it - we've had firewall problems with external attendees and have had to switch back to skype for that case. A few users have had the teams client crash repeatedly during calls. I don't see how anyone will move to it with issues like these.
  - maxxxxx 8y ago
    Could you encapsulate these dependencies into a separate service? I did that a while ago in a similar situation but as always it depends on your specific situation.
- breakingcups 8y ago
  One big one that isn't mentioned yet is Entity Framework. Now, before you say "But there's an Entity Framework Core!" it's not the same at all. It has nowhere near the same amount of features and performance nor integration into Visual Studio like EF has. This is the biggest blocker for us to move completely to .NET Core.
  - moogly 8y ago
    EF6 is part of .NET Core 3.0: https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on-net-core-3-0-and-net-framework-4-8/ https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on...
    - pjmlp 8y ago
      Partially, there is no guarantee of all EF 6 related tooling like the data designers will fully work with the Core 3.0, just the actual code execution.

Someone1234 8y ago

Just curious what dependencies are causing you so many issues?

thrower123 8y ago
Skype for Business SDKs, primarily. That is basically our business. Teams is the new hotness, but doesn't have any Api access.
- Someone1234 8y ago
  Makes sense. They keep claiming Skype for Business is dead, but Teams in my opinion is very far away from being a realistic replacement. I've not been very impressed with the desktop application at all (although the web-site is "fine").
  - jgalentine007 8y ago
    I have deployed teams in 'island' mode for our org and I'm a bit disappointed with it - we've had firewall problems with external attendees and have had to switch back to skype for that case. A few users have had the teams client crash repeatedly during calls. I don't see how anyone will move to it with issues like these.
- maxxxxx 8y ago
  Could you encapsulate these dependencies into a separate service? I did that a while ago in a similar situation but as always it depends on your specific situation.
breakingcups 8y ago
One big one that isn't mentioned yet is Entity Framework. Now, before you say "But there's an Entity Framework Core!" it's not the same at all. It has nowhere near the same amount of features and performance nor integration into Visual Studio like EF has. This is the biggest blocker for us to move completely to .NET Core.
- moogly 8y ago
  EF6 is part of .NET Core 3.0: https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on-net-core-3-0-and-net-framework-4-8/ https://blogs.msdn.microsoft.com/dotnet/2018/10/04/update-on...
  - pjmlp 8y ago
    Partially, there is no guarantee of all EF 6 related tooling like the data designers will fully work with the Core 3.0, just the actual code execution.