- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Visual Studio crashes if I add an extension for a non-Intel editor to IVF. For example, lets say I have an editor that recognizes files with "For2003" extensions. (Motivation for this is lack of support for features such as intellisense, auto-outlining, object browsing etc.) I want to add files of this type to an IVF project/solution in Visual Studio.
If I add such file to source files in VS-IDE, the file does not get compiled by IVF "as is". I believe for it to get compiled I need to add it through Tool --> Options --> IVF --> General --> Fortran File Extensions. I did that and now the file gets compiled and I see the enhanced features in the new file as well. However, as soon as I try to edit this file while under IVF project/solution, Visual Studio crashes.
But the following two scenarios work. (a) Open two instances of visual studio. In one is the IVF project/solution. In another only the files. There is no problem with either file type in the latter. That is I can use the advanced editor without VS-crash. The former instance is used only to build and compile. (b) Compile and build using command line (with appropriate switches such as /free /Tf etc which, I believe, have the same effect as adding extra extensions through Tools --> Options in VS). Then open and attach the executable to VS using devenv from command line. I can drag+drop files to this instance of VS and edit using the advanced editor. I can also save the resulting solution in VS.
In summary, two different Fortran editors are integrated in Visual Studio. Is there something on IVF's side that is causing this problem (i.e. the Visual Studio crash mentioned earlier?
Abhi
Visual Studio crashes if I add an extension for a non-Intel editor to IVF. For example, lets say I have an editor that recognizes files with "For2003" extensions. (Motivation for this is lack of support for features such as intellisense, auto-outlining, object browsing etc.) I want to add files of this type to an IVF project/solution in Visual Studio.
If I add such file to source files in VS-IDE, the file does not get compiled by IVF "as is". I believe for it to get compiled I need to add it through Tool --> Options --> IVF --> General --> Fortran File Extensions. I did that and now the file gets compiled and I see the enhanced features in the new file as well. However, as soon as I try to edit this file while under IVF project/solution, Visual Studio crashes.
But the following two scenarios work. (a) Open two instances of visual studio. In one is the IVF project/solution. In another only the files. There is no problem with either file type in the latter. That is I can use the advanced editor without VS-crash. The former instance is used only to build and compile. (b) Compile and build using command line (with appropriate switches such as /free /Tf etc which, I believe, have the same effect as adding extra extensions through Tools --> Options in VS). Then open and attach the executable to VS using devenv from command line. I can drag+drop files to this instance of VS and edit using the advanced editor. I can also save the resulting solution in VS.
In summary, two different Fortran editors are integrated in Visual Studio. Is there something on IVF's side that is causing this problem (i.e. the Visual Studio crash mentioned earlier?
Abhi
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page