471,328 Members | 1,841 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,328 software developers and data experts.

.NET does nothing on target machine

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
Jun 27 '08 #1
4 1007
On May 29, 7:08*am, "Peter Morris" <mrpmorris at gmail dot comwrote:
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
Jun 27 '08 #2
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
Jun 27 '08 #3
On May 29, 9:55 am, "Peter Morris" <mrpmorris at gmail dot comwrote:
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
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
Jun 27 '08 #4
On May 29, 10:55*am, "Peter Morris" <mrpmorris at gmail dot com>
wrote:
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
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
Jun 27 '08 #5

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

43 posts views Thread by Minti | last post: by
22 posts views Thread by Ryan M | last post: by
1 post views Thread by =?ISO-8859-1?Q?Lasse_V=E5gs=E6ther_Karlsen?= | last post: by
4 posts views Thread by Aussie Rules | last post: by
1 post views Thread by sva0008 | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.