vb.net - Override usage of registered COM assembly -


i have old vb6 application i'm moving vb.net, have com assembly referenced application.

i want able run both applications (the old 1 , .net one) side side, problem made couple of changes in signature of com assembly work on .net application (and these changes aren't compatible old app).

if install old application first, registers dll , copies system32, when install new application copies new com assembly application folder (in program files), when execute it, tries load old assembly (registered old application).

is there way make new application use assembly on own folder? , keep old application using old 1 (the 1 registered on system32).

i hope made myself clear.

thanks lot help.

sound me forgot register com server. kill old app. hard requirement in com change guids of co-classes , interfaces when make breaking changes them. ensures different versions can live side-by-side , not stomp on each other's registry entries.

a reg-free com manifest way. although isn't lot of fun put manifest , troubleshoot problems.

a really, really cheap trick put com server dll in same directory client exe. , create empty file .local filename extension. if main exe named mumble.exe file should named mumble.exe.local. that's enough com resolver use local dll, not path that's recorded in registry. documented here.


Comments

Popular posts from this blog

asp.net - repeatedly call AddImageUrl(url) to assemble pdf document -

java - Android recognize cell phone with keyboard or not? -

iphone - How would you achieve a LED Scrolling effect? -