Cannot run VBC.EXE from command prompt

12 Jan 2006 5:55 AM

Mark Keogh

Hi,

Just wondering if anyone had come across the following situation.

I currently have VS2003 installed on my machine and it's been working perfectly since day one.

Whilst waiting for our VS2005 to turn up I installed the .Net v2 framework SDK on my machine. After
doing this, my VS2003 VBC.EXE just will not run from the DOS prompt at all. When you call it it just
sits there doing nothing.

I've uninstalled the VS2005 SDK, removed and reinstalled VS2003, installed the v1 SDK etc., etc.,
etc., and nothing has fixed the issue. Dependency Walker doesn't show any missing files and I'll
completely stumped. I'd really rather not have to format my drive just to get the bloody thing back ;-)

Anyway, all suggestions would be welcome

TIA

12 Jan 2006 11:51 AM

Carlos J. Quintero [VB MVP]

Can you use File Monitor and Reg Monitor from www.sysinternals.com to
monitor disk/registry activity?

--

Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio 2005, Visual Studio .NET,
VB6, VB5 and VBA
You can code, design and document much faster in VB.NET, C#, C++ or VJ#
Free resources for add-in developers:
http://www.mztools.com

Show quoteHide quote

"Mark Keogh" <m@ark.com> escribió en el mensaje
news:%23NmgKzzFGHA.620@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> Just wondering if anyone had come across the following situation.
>
> I currently have VS2003 installed on my machine and it's been working
> perfectly since day one.
>
> Whilst waiting for our VS2005 to turn up I installed the .Net v2 framework
> SDK on my machine. After doing this, my VS2003 VBC.EXE just will not run
> from the DOS prompt at all. When you call it it just sits there doing
> nothing.
>
> I've uninstalled the VS2005 SDK, removed and reinstalled VS2003, installed
> the v1 SDK etc., etc., etc., and nothing has fixed the issue. Dependency
> Walker doesn't show any missing files and I'll completely stumped. I'd
> really rather not have to format my drive just to get the bloody thing
> back ;-)
>
> Anyway, all suggestions would be welcome
>
> TIA

12 Jan 2006 10:34 PM

Mark Keogh

Carlos J. Quintero [VB MVP] wrote:

> Can you use File Monitor and Reg Monitor from www.sysinternals.com to
> monitor disk/registry activity?

Thanks for that. For some bizarre reason it turns out that my v1.1 framework vbc.exe doesn't like
having a .config file anymore?

This is the files content.

<configuration>
     <startup>
         <supportedRuntime version="v1.1.4322"/>
         <requiredRuntime version="v1.1.4322"/>
     </startup>
</configuration>

As soon as I rename or delete the thing everything seems springs back to life!

12 Jan 2006 12:57 PM

Herfried K. Wagner [MVP]

Show quote Hide quote

"Mark Keogh" <m@ark.com> schrieb:
> I currently have VS2003 installed on my machine and it's been working
> perfectly since day one.
>
> Whilst waiting for our VS2005 to turn up I installed the .Net v2 framework
> SDK on my machine. After doing this, my VS2003 VBC.EXE just will not run
> from the DOS prompt at all. When you call it it just sits there doing
> nothing.
>
> I've uninstalled the VS2005 SDK, removed and reinstalled VS2003, installed
> the v1 SDK etc., etc., etc., and nothing has fixed the issue. Dependency
> Walker doesn't show any missing files and I'll completely stumped. I'd
> really rather not have to format my drive just to get the bloody thing
> back ;-

If you have system security software or virus scanners installed, disable
them and try again.

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://classicvb.org/petition/>