"James" <j DOT w AT zoom DOT co DOT ukwrote in message
news:en******** ******@TK2MSFTN GP03.phx.gbl...
>
"Mr. Arnold" <MR. Ar****@Arnold.c omwrote in message
news:%2******** ********@TK2MSF TNGP04.phx.gbl. ..
>>
Just because it runs on XP doesn't mean it's going to run on Vista. The
solutions you brought over from XP may have to be re-tooled to work with
Vista's security. Under the hood, Vista is another O/S platform even
though it's a NT based O/S.
Thanks for your post Mr. Arnold. Fully understood that it is a different
OS. But I was hoping that as I am using .Net 2 on both XP and Vista, the
same functions would work. I did embed manifests for UAC compliance into
the app, but the root of the problem is that Assembly.LoadFr om is failing
with FileNotFound. Do you know where to begin looking as to why this may
happen?
I would suspect that a DLL that's there on XP is not there on Vista, and
that's the file not found. You should look at the DLL(s) that are used
during this function and find out what their dependencies or other DLL(s)
used in the process are.
Something you should keep in mind, you build, compile and deploy a solution
for the platform it is intended to run on. You build and compile the
solution on a XP machine to be deployed to XP and you do the same with the
solution if it's Vista -- Vista to Vista.
It's not build solution on XP machine and deploy it to Vista machine, or the
other way around.