Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Visual Studio 2022 Version 17.5.0 and Intel OneAPI 2023.0

James_Paget
Novice
‎02-27-2023 04:27 PM
1,209 Views
Solved Jump to solution

Is Intel OneAPI 2023.0 compatible with Visual Studio 2022 Version 17.5.0?  Has anyone tried it yet?

0 Kudos
1 Solution
James_Paget
Novice
‎03-01-2023 10:05 PM
1,131 Views
Solved Jump to solution
In response to Steve_Lionel

Thanks!  By the time I had a chance to try it out, they had already upgraded it to Version 17.5.1, but that version also works fine.

View solution in original post

In response to Steve_Lionel
0 Kudos
Copy link

Link Copied

2 Replies
Steve_Lionel
Honored Contributor III
‎02-27-2023 05:43 PM
1,192 Views
Solved Jump to solution

Seems OK to me. I tried a few things, everything worked.

Copy link
James_Paget
Novice
‎03-01-2023 10:05 PM
1,132 Views
Solved Jump to solution
In response to Steve_Lionel

Thanks!  By the time I had a chance to try it out, they had already upgraded it to Version 17.5.1, but that version also works fine.

In response to Steve_Lionel
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.