Is it a new version of DLL hell?
-
Hi! I have such problem: - i make 3-tiered application, in which data access layer work on standalone computer (Server). - I have some clients which use this server. On server I have Framework 1.0 only! But clients can have differ configurations: - only framework 1.0 - only framework 1.1 - both frameworks in case when client has only 1.1 version server sometimes throw strange exceptions. On Remoting of OleDbType I have exception that server can not create instance of object on his side.
'FastReporting.exe': Loaded 'c:\windows\assembly\gac\system.data\1.0.5000.0__b77a5c561934e089\system.data.dll', No symbols loaded. Strong Thread Exception: Exception: File or assembly name System.Data, or one of its dependencies, was not found.Does anybody know how to configure client or server to remove such problem? Good Luck Alex Kucherenko -
Hi! I have such problem: - i make 3-tiered application, in which data access layer work on standalone computer (Server). - I have some clients which use this server. On server I have Framework 1.0 only! But clients can have differ configurations: - only framework 1.0 - only framework 1.1 - both frameworks in case when client has only 1.1 version server sometimes throw strange exceptions. On Remoting of OleDbType I have exception that server can not create instance of object on his side.
'FastReporting.exe': Loaded 'c:\windows\assembly\gac\system.data\1.0.5000.0__b77a5c561934e089\system.data.dll', No symbols loaded. Strong Thread Exception: Exception: File or assembly name System.Data, or one of its dependencies, was not found.Does anybody know how to configure client or server to remove such problem? Good Luck Alex KucherenkoAdd a FastReporting.exe.config file with this content: Try some variations. Why cant you just upgrade the server? Both runtimes should automatically be used for different assemblies.
-
Add a FastReporting.exe.config file with this content: Try some variations. Why cant you just upgrade the server? Both runtimes should automatically be used for different assemblies.
Upgrade server is still the only one solution for this problem... I want to find more then one solution (if it exists :( ). Thanks for help. Good Luck Alex Kucherenko
-
Upgrade server is still the only one solution for this problem... I want to find more then one solution (if it exists :( ). Thanks for help. Good Luck Alex Kucherenko
OK first some easy stuff: There is a few good articles in April 2003 MSDN on sidebyside execution. What is happening in your case (afai can figure it out): 1. Server defines an interface 2. Client implements interface 3. Client send inteface to the server 4. Server loads implemetation class. KABOOM!!! How can this be? Simple, the client has made a reference to the culprit assembly (OleDB in your case, that is new in 1.1). This is however not desirable. Like I said, installing 1.1 on the server, should automatically resolve these issues. Not doing this, leaves with 3 options: 1. Prevent the client from using "new" libaries. This not however desirable either, although I think the 1.1 compiler can compile for 1.0 compatibilty (this would be nice). 2. Use Remoting. This will be painfull, but will allow you to do more. 3. Compile any source at a single point, e.g. the server. So I guess its back to the drawing boards for you ;P Hope it helps :)