Hello Nikolay,

So, the problem with installation or with executing you file?
Have u check if any records are written to the EventLog?

To nail problem down I'd recommend to use loggin, just understand where the
problem is

---
WBR,
Michael  Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour 

"The greatest danger for most of us is not that our aim is too high and we
miss it, but that it is too low and we reach it" (c) Michelangelo

NP> I'd love to handle an error, if it was possible, But I can't do
NP> that. one of problems it's my application is ClickOnce.
NP>
NP> "Peter Hurford" wrote:
NP>

The fact that you're deploying your application as ClickOnce does not
prevent you from handling an error. It may prevent your app from writing to
the Event Log, but it doesn't prevent it from writing to a text file or
popping up a Message Box.

The fact that your app is ClickOnce may provide a clue as to the nature of
the error. ClickOnce apps run under restricted priveleges, so it may be
attempting to access some resource it lacks permission to use. But handling
the error is essential to finding out for sure what the problem is.