Renamed AutomaticUpdater...now app can't find it

Hello-

I've been renaming AutomaticUpdater.dll for awhile now for use with plugins for an app without problems

Yesterday, I upgraded to 2.6.13 and now, for some reason after renaming AutomaticUpdater.dll my app says it can't find the .dll when it's run.

Here's what I'm doing:

1) Rename AutomaticUpdater.dll and remake the reference in my app2) Rebuild3) When I try to run, I get an exception that AutomaticUpdater can't be found. Oddly, if I rename it in the Program Folder back to AutomaticUpdater.dll from, say, AutomaticUpdater7.9.dll, my app runs fine.

This doesn't seem to be a 2.6.13 issue either. I have 2.6.11.2 running with a different name in another instance, yet when I try to use 2.6.11.2 with the new builds of my app I get the same error.

I am totally stumped. Is there some setting I may have ticked in VS 2010 to create this problem?

, edited

I'm not sure what the problem is. The fix, however, is easy. First remove all references to the AutomaticUpdater in your VS project. Then add a reference to the AutomaticUpdater.dll file in the wyBuild folder (see: AutomaticUpdater tutorial for Windows Forms or AutomaticUpdater tutorial for WPF apps)

That doesn't work.

I can change the name of the dll to whatever I want before I create the reference and it will still work, but only if the dll in my program's executable folder is called 'AutomaticUpdater.dll'

Why are you renaming the AutomaticUpdater? The solution to this problem is to copy the AutomaticUpdater from the wyBuild directory to some other custom folder. Then rename them there. Finally, add references to these newly rename AutomaticUpdaters to your project.

Why are you renaming the AutomaticUpdater?

I was following the advice here: https://wyday.com/forum/t/519/multiple-plugin-update-quandry-with-new-au-dll/#post-2632

A 3rd option is to just rename the AutomaticUpdater.dll for each of your plugins. I.e. AU1.dll and AU2.dll.

What I have to do is release many versions of my plugin with each update, and then the host app will run the version that matches it's version. So I need multiple versions of AutomaticUpdater as well.

OK, I solved this by loading the dlls into an AppDomain and then using a ResolveEventHandler to select the correct one.

Reply
Discard post