vb.net winform apps fail on WindowsNT

  • Thread starter Thread starter Elliot M. Rodriguez
  • Start date Start date
E

Elliot M. Rodriguez

I've been struggling with this for a bit now and I hope someone can offer
some help.

Any winform app I assemble that I run on WinNT SP6a with 1.1 framework
installed completely crashes. Whether its by simply running a built EXE or
creating a VS installation project, the result is the same. A modal dialog
box that reads simply:

"Application generated an exception that could not be handled".

And my app would crash. The same installer works fine under WinXP and 2000.

I was able to run the EXE from the command line and output the error stream
to a file, so I could at least get an idea of what the error was, and it
simply read:

"Fatal stack overflow error".

I assume this occurs in Initialze Component, since the form doesnt ever load
or even instanced (error handling I implement here is never reached).

Can anyone offer anothe rdirection? I am at the end of my rope on this
one... Thank you
 
* "Elliot M. Rodriguez said:
I've been struggling with this for a bit now and I hope someone can offer
some help.

Any winform app I assemble that I run on WinNT SP6a with 1.1 framework
installed completely crashes. Whether its by simply running a built EXE or
creating a VS installation project, the result is the same. A modal dialog
box that reads simply:

"Application generated an exception that could not be handled".

And my app would crash. The same installer works fine under WinXP and 2000.

I was able to run the EXE from the command line and output the error stream
to a file, so I could at least get an idea of what the error was, and it
simply read:

"Fatal stack overflow error".

I assume this occurs in Initialze Component, since the form doesnt ever load
or even instanced (error handling I implement here is never reached).

Does this even occur with a "single-form-project"?
 
Herfried:

Thanks for your reply.

Yes, even with a single form, one-button, MessageBox.Show("Hello World")
type app, it fails with the error described.

I tried to install full debugging support also (so at least I could fire the
CLR debugger), and I was greeted with the same error in various stages of
the install.
 
Just to follow up, another developer put togehter another single form one
button "Hello World" app pointed at the 1.0 runtime and that also failed
with the same error result.
 
Back
Top