4 ms·

> I don't like Visual Studio as IDE, but VS Code is an acceptable alternative tool, although I personally prefer the non-free JetBrains Rider. I've used Visual

by bbarn 4y ago

> I don't like Visual Studio as IDE, but VS Code is an acceptable alternative tool, although I personally prefer the non-free JetBrains Rider. I've used Visual Studio for 20 years now, and while the tooling has come a long way, I'm starting to feel like MS and the community are abandoning it for VS Code. I don't mind VS code, but unfortunately the stack I'm working in (Dynamics 365) requires plugins for Visual Studio that tend to lag behind the release cycle of Visual Studio versions by a few years. I use Rider for .net core projects on my mac and it's fantastic. In fact my biggest criticism of my day to day job is Microsoft's support for this incredibly enterprisey framework I have to work in.

jve 4y ago
Hey fellow Dynamics 365 (CRM?) developer. I see they move in VSCode direction with tools like Power Platform CLI [1], power platform tools extension [2]. PCF (PowerAps Component framework) enabling to develop UI components in frontend framework-of-choice... however none of that is available (yet?) for On-Premise deployment so we're 2nd class citizens. Because of that, haven't been able to play with this and try out so don't know how far that tooling goes. As a platform, I really like it. Sane, consistent (except some very early stuff there), the backend extensibility - thumbs up for that. [1] https://docs.microsoft.com/en-us/power-platform/developer/cli/introduction https://docs.microsoft.com/en-us/power-platform/developer/cl... [2] https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.powerplatform-vscode https://marketplace.visualstudio.com/items?itemName=microsof...
- bbarn 4y ago
  F&O, sadly...
  - jve 4y ago
    F&O would be former AX? That seems highly rewarded field. I know it only from SQL point of view - It helped grow my SQL skills when SQL would be brought to it's knees (along with the business) due to skewed data distribution and occasional query plan invalidation.
    - bbarn 4y ago
      Yep, it's the replacement for AX. I can't say I love working in it, but the clients are massive and as such, it can be a rewarding financial choice. The tooling is poor and the APIs are a bit difficult but it's made for some fun workarounds :)

by bbarn 4y ago

jve 4y ago

Hey fellow Dynamics 365 (CRM?) developer. I see they move in VSCode direction with tools like Power Platform CLI [1], power platform tools extension [2]. PCF (PowerAps Component framework) enabling to develop UI components in frontend framework-of-choice... however none of that is available (yet?) for On-Premise deployment so we're 2nd class citizens. Because of that, haven't been able to play with this and try out so don't know how far that tooling goes. As a platform, I really like it. Sane, consistent (except some very early stuff there), the backend extensibility - thumbs up for that. [1] https://docs.microsoft.com/en-us/power-platform/developer/cli/introduction https://docs.microsoft.com/en-us/power-platform/developer/cl... [2] https://marketplace.visualstudio.com/items?itemName=microsoft-IsvExpTools.powerplatform-vscode https://marketplace.visualstudio.com/items?itemName=microsof...

bbarn 4y ago
F&O, sadly...
- jve 4y ago
  F&O would be former AX? That seems highly rewarded field. I know it only from SQL point of view - It helped grow my SQL skills when SQL would be brought to it's knees (along with the business) due to skewed data distribution and occasional query plan invalidation.
  - bbarn 4y ago
    Yep, it's the replacement for AX. I can't say I love working in it, but the clients are massive and as such, it can be a rewarding financial choice. The tooling is poor and the APIs are a bit difficult but it's made for some fun workarounds :)