Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail From: "Thorsten Albers" Newsgroups: alt.comp.lang.vb,alt.comp.lang.visualbasic,comp.lang.basic.misc,comp.lang.basic.visual.misc,microsoft.public.dotnet.languages.vb,microsoft.public.dotnet.languages.vb.upgrade Subject: Re: Upgrading older VB programs (sans Project Files) to VB.NET Date: Thu, 5 Jan 2012 16:33:05 +0000 (UTC) Organization: Albert-Ludwigs-Universität Freiburg Lines: 18 Message-ID: <01cccbc7$b3740f80$6d01a8c0@k8s8x> References: Injection-Date: Thu, 5 Jan 2012 16:33:05 +0000 (UTC) Injection-Info: mx04.eternal-september.org; posting-host="YTz2i+brujCtf/+zTHlciA"; logging-data="4521"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX18pRD2Zvd/WEoXG5yHc9bBz" X-Newsreader: Microsoft Internet News 4.70.1155 Cancel-Lock: sha1:ff0bK6dHl8Qk1+yVuz4jIoQnlXM= Xref: x330-a1.tempe.blueboxinc.net comp.lang.basic.misc:190 comp.lang.basic.visual.misc:606 Ubiquitous schrieb im Beitrag ... > I have some old Visual Basic programs I'd like to upgrade to .NET because > they currently require obsolete drivers like "VBRUN300.DLL" to run. I > attempted to use the upgrade wizard but it appears it requires a project > file and I only have .FRM, .FRX, and Make files, like this one: Those files you are naming "make files" in fact are _the project files_. 16 bit VB (in your case VB 3.0) used the extension ".MAK" for project files. It is rather unlikely that the upgrade wizard accepts project files from a 16 bit version of VB. -- Thorsten Albers gudea at gmx.de