VB.NET app cannot deploy on any client machine! Exception couldn't be handled!!!

From: Bill Nguyen (billn_at_jaco.com)
Date: 09/19/03 

Date: Thu, 18 Sep 2003 17:14:23 -0700

Forgive me for cross-posting, I'm desperated.
-------------
Client machine: Win2K server SP4 with both .NET framework 1.0 & 1.1
installed. VB.NET app developed using an XP Pro with VS.NET 2003 / .NET
framework 1.1
You help is greatly appreciated.
Bill

--------------------------

Common Language Runtime Debugging Services:
Application has generated an exception that could not be handled.

Process id=0x248 (584), Thread id=0xe68 (3688).

Click OK to terminate the application.
Click CANCEL to debug the application.

Relevant Pages

  • VB.NET app cannot deploy on any client machine! Exception couldnt be handled!!!
    ... Forgive me for cross-posting, I'm desperated. ... VB.NET app developed using an XP Pro with VS.NET 2003 / .NET ... framework 1.1 ... Common Language Runtime Debugging Services: ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Framework definition...
    ... "The .NET Framework consists of two main parts: ... applications and Web services, Windows Forms for smart client applications, ... The Common Language Runtime Library is an immense collection of code. ...
    (microsoft.public.dotnet.framework)
  • Re: Upgrading Windows XP
    ... >> If you want to experiment with programming languages in MS .net ... >> framework, then you need pro to fully install all the features. ...
    (uk.comp.homebuilt)
  • Re: Upgrading Windows XP
    ... >>> framework, then you need pro to fully install all the features. ...
    (uk.comp.homebuilt)
  • Re: Network Printing Problem
    ... I also posted the query in the microsoft.public.windowsxp.network_web ... also (I know, I know, cross-posting, but I would not have if I had ... I completely agree that XP Home or Pro is a red herring - ... network running both XP Pro and Home (with an SMC router with a ...
    (comp.periphs.printers)