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

Windows side by side deployment ( aka sxs)

carlls
Beginner
‎02-15-2010 11:31 AM
549 Views

Greetings:

I am trying to avoid dll hell and am considering using the windows side by side approach to things. (http://msdn.microsoft.com/en-us/library/aa376307(VS.85).aspx)

It appears since VS 2005 MS installs dlls in a dir like C:/windows/winsxs, and these files can be pointed to via the manifest file.

Does Intel FORTRAN support a similar philosophy?

Now to head off the obvious threads about Intel DLLs being backward compatible... I do know that is the claim and for the most part believe it. However applications with bugs may work just fine in version X.X dlls, but fail miserably in version X.Y dlls.

So with that in mind the side by side releases seem a reasonable solution.

Anybody else doing this?

Regards

Carl

0 Kudos

Link Copied

1 Reply
IDZ_A_Intel
Employee
‎02-15-2010 01:54 PM
550 Views
We do not provide our DLLs as shared assemblies. We looked into doing so, but developers at Microsoft convinced us not to do it, though I don't know what the specific issues were. Shared assemblies solve some problems but create others.
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.