Installing issues...please help

[genc ymeri]

Hi,
I have a application which runs fine in any PC which has installed .Net1.1
framework and VS2003 but do run in any PC which has installed only .Net
framework 1.1.

The error I get is this. Any idea please ?

PS:

---------------------------
WFDesigner.exe - Common Language Runtime Debugging Services
---------------------------

Application has generated an exception that could not be handled.
Process id=0x8ec (2284), Thread id=0x480 (1152).
Click OK to terminate the application.
Click CANCEL to debug the application.

 

[Guest]

Give fuslogvw.exe a whirl and make sure that all of the assemblies you application needs can be accessed correctly

Also, make sure you have unhandled exception logic so you can hopefully display a meaningful message, write to the Event Log etc

http://msdn.microsoft.com/library/d...ystemAppDomainClassUnhandledExceptionTopic.as

an

http://msdn.microsoft.com/library/d...sformsapplicationclassthreadexceptiontopic.as

HT

RS

 

[genc ymeri]

Should I copy my reference dll files in the client PC also ? for instance, I
have as a reference the "system.data.dll" located at
c:\winnt\microsoft.net\framework\v1.1.4322\system.data.dll

while in the client PC the same file is located somewhere else. Same for
other references. Do you think that may be an issue ? If yes, how this
should be get resolved ?

Give fuslogvw.exe a whirl and make sure that all of the assemblies you

application needs can be accessed correctly.

Also, make sure you have unhandled exception logic so you can hopefully

display a meaningful message, write to the Event Log etc.

 

[genc ymeri]

btw what is fuslogvw.exe ?

Thanks a lot.

Give fuslogvw.exe a whirl and make sure that all of the assemblies you

application needs can be accessed correctly.

Also, make sure you have unhandled exception logic so you can hopefully

display a meaningful message, write to the Event Log etc.

 

[Guest]

This is from MSDN regarding fuslogvw.exe or the Assembly Binding Log Viewer

"The Assembly Binding Log Viewer displays details for failed assembly binds. This information helps you diagnose why the .NET Framework cannot locate an assembly at run time. These failures are usually the result of an assembly deployed to the wrong location or a mismatch in version numbers or cultures."