.NET does nothing on target machine

[Peter Morris]

I do a simple unzip style deployment onto a target machine. This target
machine previously had a working version of my app on it but 30 seconds
after unzipping the new DLLs etc to this folder nothing happens when the
WinForm EXE is double-clicked.

Without getting the .NET 2 SDK downloaded onto this computer is there a way
I can find out what is going on?


Cheers


Pete

 

[Ignacio Machin ( .NET/ C# MVP )]

I do a simple unzip style deployment onto a target machine.  This target
machine previously had a working version of my app on it but 30 seconds
after unzipping the new DLLs etc to this folder nothing happens when the
WinForm EXE is double-clicked.

Without getting the .NET 2 SDK downloaded onto this computer is there a way
I can find out what is going on?

Cheers

Pete

what framework are you targetting?
is it the same than your old app?
it's weird that nothing happens, at least an error message should be
displayed

 

[Peter Morris]

what framework are you targetting?

2.0

is it the same than your old app?

Yes, the same app with modified GUI etc. All DLLs are marked
"CopyLocal=True" too.

it's weird that nothing happens, at least an error message should be
displayed

I agree, and that's why I want to know what is happening Does anyone
have any ideas?



Pete

 

[Chris Dunaway]

Yes, the same app with modified GUI etc. All DLLs are marked
"CopyLocal=True" too.


I agree, and that's why I want to know what is happening Does anyone
have any ideas?

Pete

If you can connect to the target machine using the debugger from your
development machine, you can try to debug the app.

If not, you can fall back on the old fashioned way by adding logging
statements to your code.

Also, check the Event logs on the target machine and see if anything
is logged in the event logs.

Chris

 

[Ignacio Machin ( .NET/ C# MVP )]

Yes, the same app with modified GUI etc.  All DLLs are marked
"CopyLocal=True" too.


I agree, and that's why I want to know what is happening  Does anyone
have any ideas?

Pete

Are you logging the errors?
TAke a look into AppDomain.UnhandledException and
Thread.ThreadException

without seeing the code that is run before displaying the first window
is difficult to know where the problem is