Calling assembly : (Unknown).

[Phil Wilson]

"Sam Carleton" <scar...@NO.SPAM.linux-info.net> wrote in message
news:slrnaqoicm.5...@glob620.miltonstreet.com...
> I am having a bear of a problem. I am trying to create a WebSetup
> for my test Web Service (TempConvert1). The basic WebSetup works
> just fine, until I add a Installer Class. I have tried an Installer
> Class which does not override any of the base class and I have tried
> overriding Install. Both give the EXACT same result, they fail.
>
> This is the output from FUSLOGVW.exe:
>
> *** Assembly Binder Log Entry (10/15/2002 @ 12:41:54 PM) ***
>
> The operation failed.
> Bind result: hr = 0x80070002. The system cannot find the file specified.
>
> Assembly manager loaded from: C:\WINNT\Microsoft.NET\Framework\v1.0.3705\
> fusion.dll
> Running under executable C:\WINNT\System32\MsiExec.exe
> --- A detailed error log follows.
>
> === Pre-bind state information ===
> LOG: Where-ref bind. Location = C:\WINNT\System32\Server
> LOG: Appbase = C:\WINNT\System32\
> LOG: Initial PrivatePath = NULL
> LOG: Dynamic Base = NULL
> LOG: Cache Base = NULL
> LOG: AppName = NULL
> Calling assembly : (Unknown).
> ===
>
> LOG: Processing DEVPATH.
> LOG: Policy not being applied to reference at this time (private, custom,
> partial, or location-based assembly bind).
> LOG: Attempting download of new URL file:///C:/WINNT/System32/Server.
> LOG: All probing URLs attempted and failed.
>
>
> This log file means NOTHING to me. I am assuming that the line
> "Calling assembly : (Unknown)." is the key line, but for all I know
> that is normal. Can someone, anyone give me some insight?
>
> Sam Carleton
>

[Phil Wilson]

Let me try again. Seems to be an empty reply there, because replying to the group replies to your
nospam email, argg.

Calling assembly unknown is normal - it means that the calling process is not an assembly, which is
correct, it's msiexec. This just means that the installer service can't find your assembly to
instantiate its install class and call the various methods. Is your assembly the key file in the
component? I believe that's a requirement.