>As long as the type signatures match sure. If you're not signing your assemblies it should just all work period. If you are signing you will need to recompile everything and ensure assembly references resolve properly.Thanks Rick!
We don't sign our assemblies, but we do use a third-party DLL from DevExpress that is signed (well, it uses a Strong Name, public key or whatever ... I *think* that's the same thing, right?).
The two DLLs and the EXE that are on the workstations (the ones that would be 2.0) do not use the DevExpress DLL. Everything is instantiated via Interfaces (which is what one of those DLLs contains). However there is a reference to the DevExpress DLL in the EXE project, even though it's not actually used. Will that cause a problem when a DLL on the server is brought down to the workstation, and that DLL references a different version of the DevExpress DLL? (We have to recompile the DevExpress DLL ... we have the source code ... it's very old, compiled to the 1.0 Framework).
I had a previous question posted here, Message #
1301411, with a related question about that DevExpress recompile ... could you take a quick look at the question if you get a chance? No one here has replied yet, so I also posted the question on MSDN (
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=3010608&SiteID=1&mode=1) ...
Thanks!
~~Bonnie
>
>+++ Rick ---
>
>>Hi gang,
>>
>>Our applications all use Reflection to instantiate the majority of the application. We install only one EXE and two DLLs on a workstation and the rest of the DLLs are loaded from a server location using Reflection.
>>
>>We are going to be updating all our apps to VS2008, and will be compiling them to the 3.5 version of the Framework (we currently are using VS2005 and the 2.0 Framework). I am hoping to be able to do this incrementally. We have a scheduled Beta release of one application coming up in a few weeks and we have not, as yet, converted to VS2008.
>>
>>So, here's the question:
>>
>>Can we distribute the EXE and two DLLs that have still been compiled to 2.0 and be able to instantiate the newer DLLs (via Reflection) once they have later been compiled to 3.5 without problems?
>>
>>TIA,
>>~~Bonnie
