<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Integration with Visual Studio apps in Software Archive</title>
    <link>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971480#M24048</link>
    <description>VB is in its own world - it does not share the MSVC/CVF Developer Studio environment.  Perhaps this will change in the future.&lt;BR /&gt;&lt;BR /&gt;You can, however, debug CVF DLLs that you call from VB.  Our Knowledge Base has an article on this.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
    <pubDate>Sun, 21 Oct 2001 10:01:39 GMT</pubDate>
    <dc:creator>Steven_L_Intel1</dc:creator>
    <dc:date>2001-10-21T10:01:39Z</dc:date>
    <item>
      <title>Integration with Visual Studio apps</title>
      <link>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971479#M24047</link>
      <description>I'm having trouble getting CVF 6.6 to integrate with Visual Basic 6.0.... &lt;BR /&gt; &lt;BR /&gt;I have VB 6.0 and VC++ already installed (separate applications, not purchased as Vis Studio), and they don't seem to recognize each other, either....  CVF "sees" VC++, but not VB.  VC++ sees CVF, but not VB...  VB sees neither.... &lt;BR /&gt; &lt;BR /&gt;What to do?</description>
      <pubDate>Sun, 21 Oct 2001 06:46:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971479#M24047</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2001-10-21T06:46:37Z</dc:date>
    </item>
    <item>
      <title>Re: Integration with Visual Studio apps</title>
      <link>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971480#M24048</link>
      <description>VB is in its own world - it does not share the MSVC/CVF Developer Studio environment.  Perhaps this will change in the future.&lt;BR /&gt;&lt;BR /&gt;You can, however, debug CVF DLLs that you call from VB.  Our Knowledge Base has an article on this.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Sun, 21 Oct 2001 10:01:39 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971480#M24048</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2001-10-21T10:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: Integration with Visual Studio apps</title>
      <link>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971481#M24049</link>
      <description>I have had a code package for the last 5 years that combines a Visual Basic GUI with a Fortran simulation.   &lt;BR /&gt;When I run from the VB side all seems to be OK.  &lt;BR /&gt; When I run from the Fortran 6.5.0 side it:  &lt;BR /&gt;(1) gives an error DFDEV.exe - No Disk, "There is no disk in the drive. Please insert a disk into drive Deviveharddisk2dr4",  &lt;BR /&gt;(2) brings up the GUI behind the FORTRAN screen,  &lt;BR /&gt;(3) no VB icon appears on the bottom of the screen.   &lt;BR /&gt;How far back must I go to get the features I am used to? Or, is there a unique loading pattern I can use?  &lt;BR /&gt; I have the "Visual Studio 6.0 Professional Edition" &lt;BR /&gt; &lt;BR /&gt;Thank you</description>
      <pubDate>Wed, 31 Oct 2001 02:43:01 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971481#M24049</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2001-10-31T02:43:01Z</dc:date>
    </item>
    <item>
      <title>Re: Integration with Visual Studio apps</title>
      <link>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971482#M24050</link>
      <description>This is a Visual Studio problem that people see with Visual C++ as well.  The solution seems to be to delete the .OPT and .NCB (if any) files from the project folder and re-open Developer Studio.  (The files will get recreated.)  Any breakpoints you had set will need to be recreated.&lt;BR /&gt;&lt;BR /&gt;Steve</description>
      <pubDate>Wed, 31 Oct 2001 02:58:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Software-Archive/Integration-with-Visual-Studio-apps/m-p/971482#M24050</guid>
      <dc:creator>Steven_L_Intel1</dc:creator>
      <dc:date>2001-10-31T02:58:53Z</dc:date>
    </item>
  </channel>
</rss>

