This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Team Build\MSBuild issue
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2007
04:45 AM
Team Build\MSBuild issue
I'm trying to build a project via Team Build (which uses MSBuild) on our build server and i'm getting the following error:
C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.targets(63,3): error MSB4062: The "Macrovision.InstallShield.Tasks.InstallShield" task could not be loaded from the assembly C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.Tasks.dll' or one of its dependencies. The module was expected to contain an assembly manifest. Confirm that the declaration is correct, and that the assembly and all its dependencies are available.
The installation itself is an Admin Studio installation and i've installed it to the D drive (some files have been installed to the C drive to).
I've tried loading the dll in idlasm (which failed) and then Depends which came back with nothing useful.
Does anyone else have any information or experienced this to?
Regards,
Matt
C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.targets(63,3): error MSB4062: The "Macrovision.InstallShield.Tasks.InstallShield" task could not be loaded from the assembly C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files\MSBuild\Macrovision\IS2008\Macrovision.InstallShield.Tasks.dll' or one of its dependencies. The module was expected to contain an assembly manifest. Confirm that the
The installation itself is an Admin Studio installation and i've installed it to the D drive (some files have been installed to the C drive to).
I've tried loading the dll in idlasm (which failed) and then Depends which came back with nothing useful.
Does anyone else have any information or experienced this to?
Regards,
Matt
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 07, 2007
10:21 AM
The dependencies of that file should only include the .NET 2.0 framework and the VC8 redist (as well as a runtime dependency of our IDE or SAB); I'm not certain what the missing assembly manifest amounts to, as I know this works in other scenarios. However I don't see how you could lack either dependency if VSTS is installed.
If you have the Macrovision.InstallShield.Tasks.dll, and/or the targets file, on another machine where you can successfully use MSBuild, you might try copying them in and making sure the path in the .targets file references the build machine's InstallShield install.
If you have the Macrovision.InstallShield.Tasks.dll, and/or the targets file, on another machine where you can successfully use MSBuild, you might try copying them in and making sure the path in the .targets file references the build machine's InstallShield install.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2007
05:00 AM
It is confusing, i've tried in on my dev box to and getting the same error (just using MSBuild here).
The Macrovision product i have is AdminStudio evaluation version. Confused to about what could be missing.... Any ideas how i can debug it further?
Matt
The Macrovision product i have is AdminStudio evaluation version. Confused to about what could be missing.... Any ideas how i can debug it further?
Matt
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 10, 2007
08:08 AM
I don't use AdminStudio anymore but I'm guessing that there is a problem with their install based on prior experience with how they compose InstallShield/AdminStudio at release time. I can't test this though.
Matt-
I sent you an email with suggestions. Please let me know how it turns out.
Thanks,
Chris
Matt-
I sent you an email with suggestions. Please let me know how it turns out.
Thanks,
Chris