# Problems with Visual Studio and Intel Fortran oneAPI

**URL:** <https://fortran-lang.discourse.group/t/problems-with-visual-studio-and-intel-fortran-oneapi/8810>\
**Category:** Help\
**Created:** [November 7, 2024, 9:57am UTC](https://fortran-lang.discourse.group/t/problems-with-visual-studio-and-intel-fortran-oneapi/8810 "2024-11-07T09:57:56Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hkvzjal](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/hkvzjal/32/3055_2.png) [@hkvzjal](https://fortran-lang.discourse.group/u/hkvzjal)\
**Post date:** [November 7, 2024, 10:25am UTC](https://fortran-lang.discourse.group/t/problems-with-visual-studio-and-intel-fortran-oneapi/8810/4 "2024-11-07T10:25:09Z")

</div>

> [@mEm](#):
>
> I would test it with a VS2019 installation, and see if that works.

Please don’t … if you have VS2022 and try to install VS2019 with intel integration you are bound to a very nasty experience!!

> [@Arjen](#):
>
> Does anyone have a better solution than going back to Intel Fortran oneAPI 2024-something?

I don’t know if checking the generator option could help [Using ifx rather than ifort with cmake - #11 by hkvzjal](https://fortran-lang.discourse.group/t/using-ifx-rather-than-ifort-with-cmake/8423/11) ?

---

_[View the full topic](https://fortran-lang.discourse.group/t/problems-with-visual-studio-and-intel-fortran-oneapi/8810)._