Visual Studio Community 2013 - "free" IDE with resource editor

[ZlamalJakub]

Microsoft relased Visual Studio Community 2013 which is full version of Visual Studio which is available at no cost for non-enterprise application development.

I have tried to install Intel Fortran to this version of VS and everything seems work well even resource editor.

[Paul_Curtis]

Yes!!   I downloaded VS-Community 2013, and re-installed IVF2015 to switch the IVF integrations from VS2012 to VS2013, works perfectly.  VS2013 seems to be better than VS2012 (tho neither brings anything to the party that wasn't present in VS2008).  I will have to check whether WinXP is natively supported as a target in VS2013, or whether the fix is needed as was the case for VS2012.

[j0e]

Has anyone else tried VS community 2013 (here http://www.visualstudio.com/en-us/visual-studio-community-vs.aspx)  with IVF?  I'm running IVF with VS 2010, but might change over if no one has found problems.

-joe

[Steven_L_Intel1]

We're trying this now - so far it looks good.

[Steven_L_Intel1]

Seems to work fine. If you want to use it, make sure that you meet the criteria for free use as described at http://www.visualstudio.com/support/legal/dn877550

[DavidWhite]

Steve,

How do I get the IVF2015 installer to recognise the presence of VS Community 2013?

I have installed VS Community 2013, but I am now installing IVF2015 Update 1, and the only option given was to integrate with the existing (bundled) VS2010.  Do I need to do a complete uninstall fo IVF2015 first?

Thanks,

David

[DavidWhite]

Solve the integration issue.  Rerunning the installer using the Modify option enabled me to select VS2013.  Not sure why the installer did not recognize it was installed the first time through.

David

[PeterTheRascal]

** I did submit this question to Premier Support who said they would investigate but  "VS community 2013 doesn't meet the system requirement"

I have recently installed on recent Win7/64 notebook w_fcompxe_2015.1.148.exe+VS Community 2013

I am having trouble with my new DLL build but find even sample FCALL has the same issues. As do DLLs that work on other machines.

[1] Project : warning PRJ0018 : The following environment variables were not found: >$(FNL_DIR).  This may or may not be related to other issues

[2] The DLL is not usable on the build machine. Dependency Walker shows the same problem even on DLLs that work on other machines (full Dedends dump attached)

API-MS-WIN-APPMODEL-RUNTIME-L1-1-0.DLL         Error opening file. The system cannot find the file specified

etc etc

I have un -installed the Fortran and re-installed but that had no impact

Thanks

[Steven_L_Intel1]

We do support VS2013 Community Edition now (in our 2015 product) but the message may not have gotten to all the Premier Support engineers. I'll spread the word.

The build warning is because you configured VS to look for IMSL but IMSL isn't installed.

As for your other problem, I don't know what you mean by "sample FCALL" since I don't see we have a sample by that name. We do have Fortan-Calls-C and C-Calls-Fortran - I built and ran both of those with Community Edition without issue. The DLL you've mentioned is not used by Fortran. However, a Google search for it tells me that the report by Dependency Walker that it is missing is a "red herring" - it isn't important.  There are often some "delay loaded" DLLs that are missing and are harmless.

What is the error you get when trying to run the program? You didn't say.

[Paul_Curtis]

No free lunch from Microsoft, and no "free" Visual Studio either, turns out this was a promo offer only and the "free" installation expires after 3 months or thereabouts unless validated by a purchase (for $1,300).  If there was fine print to this effect in the original offer, I sure missed it.  And I was recalling Ballmer's famous "Developers, developers, developers!" rant and assumed MS had finally woken up and commenced a new marketing foray to actually woo and support and encourage Windows developers.  Not.

[DavidWhite]

Paul,

Not sure whether I have had it installed for 3 months yet.  Just tried my copy - it said my 30 day trial had expired.  I them logged into my microsoft account, and it downloaded a new license.

Have you done this?  Does these updates then die after three months?  I have checked all the documentation, there is no indication of an expiry period, except that it says that some of the tools are trial versions with only 30 day licenses.

David

[Steven_L_Intel1]

I've had my copy installed for more than 30 days.  The license terms say "The software may prompt you from time to time to obtain a license key, such as by signing into a Microsoft account. If you do not obtain and enter a new license key when prompted, you may not be able to use the software and access your data in the software. " but that's not the same as forcing you to pay. Indeed, on one of my systems VS13 Professional keeps asking me to log in every month or so, but elsewhere it doesn't.

I don't see anything about it being a trial or expiring.

[andrew_4619]

David White wrote:
Not sure whether I have had it installed for 3 months yet.  Just tried my copy - it said my 30 day trial had expired.  I them logged into my microsoft account, and it downloaded a new license.

Same for me, logged in and it was back up and running. I think the want you to periodically access a Microsoft account  as a sales opportunity..

[PeterTheRascal]

Upgrade issues (Steve)

I am very pleased VS Community 2013 is supported, and this has encouraged me to work through my Fortran DLL library issues.  I confess I had always assumed Depends was very useful and, in the past, have only had occasional confusion easily sorted by simple paths. Here the code all now works despite the Depends “issues”.

One remaining upgrade issue which  may be VS related, or a glitch just in of w_fcompxe_2015.1.148.exe.   I have had to link to an older MKL as the new include  mkl_xxxx.mod

C:\Program Files (x86)\Intel\Composer XE 2013\mkl\include\ia32 -   Has mkl_lapack95.mod. mkl, mkl_xxxx.mod

C:\Program Files (x86)\Intel\Composer XE 2015\mkl\include\ia32   -  Has no mkl_xxxx.mod

Thanks, Peter

[PeterTheRascal]

Free lunch?   Free for small teams (up to 5) and small companies (<$1m turnover). MS will not lose big customers but may keep a few for moving to “open source”?       http://www.visualstudio.com/support/legal/dn877550

[TimP]

It appears to permit everyone to build open sourced applications.

[mecej4]

Re #14: Peter, since a couple of releases, the MKL include directories contain blas95.mod and lapack95.mod as in the Netlib release of Lapack95. Earlier version of MKL had the filenames decorated with 'mkl', and even earlier versions gave you only the source files and makefiles to build Lapack95 and Blas95 yourself. The files are functionally the same, apart from the name changes.