I know we tend to stay away from Tech Support Hell (tm Dell) here and
focus more on process/tools, however I wanted to ask a question to
those possibly more experienced with AppDomains than I am. I pretty
much have a solution to the problem, however I just want to make sure
I'm not missing anything.
The problem is this, I have an Updater scenario where I need to have
the Updater update itself. This is the perfect scenario for
AppDomain.ShadowCopyFiles, however I cannot find a way to have a .NET
executable start with the ShadowCopyFiles turned on by default. Does
anyone here know of a way?
My current solution is to have a launcher.exe that will likely never
change spin up a new AppDomain with ShadowCopyFiles turned on, then
execute my updater.exe within that AppDomain. This allows the updater
to be updatable while minimizing any unchangable code. I still feels
like a kludge to me though. What do you guys and gals think?
I know we tend to stay away from Tech Support Hell (tm Dell) here and focus more on process/tools, however I wanted to ask a question to those possibly more...
There isn't another way unless you are into CLR hosting, and I assure you that this is not the way to go. You can even have the updater.exe update the...
Ayende Rahien
Ayende@...
Jan 9, 2008 9:59 pm
Thanks! However wouldn't the launcher.exe be locked? -Jon ... assure you ... and ... pretty ... sure ... have ... a .NET ... Does ... never ... then ... ...
Launcher.exe does the following: 1/ copy itself to temp dir 2/ execute the copy in the temp dir with command args 3/ return in the temp dir, launcher does: 1/...
Ayende Rahien
Ayende@...
Jan 9, 2008 10:08 pm
Ahh, okay we had thought of doing something similar... Great idea! Sadly we can't use ClickOnce because of the deployment group here having to be in control of...
Considering the main .exe in use needs to be shut down to be replaced in any case, what's the point in an upgrade scenario for shadow copy? If clickonce...
Sebastien, Thanks for the response. Our specific problem is requiring us to write our own updater in order to serve our users while compensating for a issue...
I'd write an updater to download the updating msi / msp and rely on the windows updater for the rest. If you want to make it right, supports the restart...
That's excellent. We're going to talk about it right now. Thanks! ... the ... supports the ... for ... work ... [mailto:altdotnet@yahoogroups.com] On ... ...
Jon, Have you looked at the Updater Application Block from the P&P folks? I haven't used it, I'm only aware of it, but it sounds like it addresses your...
Oops, typo... update_bootstrap.exe would take 3 arguments. ... From: altdotnet@yahoogroups.com on behalf of Chad Myers Sent: Wed 1/9/2008 4:09 PM To:...
Chad, Thanks for the suggestions! Right now the Updater is going to be packaged as an MSM within an MSI/MSP for the updates and my coworker has that portion...
To throw a little fuel on this fire I ran into this old code from Mike Woodring to munge with the CurrentAppDomain while running. It's 1.1 stuff, but I'd love...
BAD Mojo that, Bad Mojo. Don't do this, ever. You are going to run into so many risks of ruining things. As a simple example, consider this: /bin/ myApp.exe ...