Dave,

Check out the event viewer.  I've had to look into the event viewer
many times for my day job while debugging .NET apps and services.
Bring up a Run console and enter "eventvwr" for the quickest access.

I don't have an XP machine at home, so I don't remember what the XP
version of the Event Viewer console looks like, but on Win7, check out
the "Application" event log under the "Windows Logs" folder and check
out the entries around the time the user attempted to start up the
program.  With any luck, you can find out at least a little bit more
information as to what is going on on the users' workstations when
they try to launch your app.

Josh

On Feb 9, 11:05 pm, iDesmet <[email protected]> wrote:
> Hallo all,
>
> I have searched over the Internet and here, and the solutions found
> didn't help with my problem.
> I've created a windows application (WinForms) using various
> components, of course, it works well on my development pc, but whey I
> try to deploy on a client pc it simply stop working when loading
> (Initializing).
>
> It's created using .NET 4.0, which is already installed in the client
> pc (with .NET 2.0 to 3.5). I use InstallAware to create the setup, I
> have created several applications and deployed in several pcs and all
> of them worked without any issue, so this is the first time I'm facing
> such problem.
>
> I also used the built-in feature in InstallAware to search and add
> dependencies which I though it was the problem. In the same solution I
> created the application, there's another project (report viewer) I
> created using almost the same components and works fine on client pc.
>
> I must add that in another develpment computer, the problematic
> application works as expected.
>
> So, my question: Is there a tool (other than Fusion Logger) which I
> can use to search deeper for dependencies in the developed application
> (just in case it is a dependency error)?
>
> Or, Is there another way I can find out why the applications stops
> abruptly when starting?
>
> Thanks in advance!
>
> Regards,
> Dave

Reply via email to