.Net 3.0 Not Fully Installed

[peter_ashworth]

Using InstallAware Studio 6, I am having problems installing the full .Net 3.0 installation. When I build a new application and then install it on to a clean machine the .Net 3.0 installation appears to be successful and my application appears to work. However when I use certain functions to display Windows Presentation items or perform their printing the application crashes with an error to do with the "system.windows.markup.xamlparse" object. If I install the .Net 3.0 redistributable from the Microsoft website then everything works correctly.

After a lengthy investigation I have found that some .Net 3.0 dlls are not being installed by the InstallAware version of .Net 3.0 installation. One of these is "WindowsCodecs.dll".

I am using InstallAware Studio 6 build gwinnett_sp3.111106

The following "Application Runtimes" are set to install:

Microsoft .Net Framework 2.0
Microsoft .Net Framework 3.0
Microsoft Windows Installer 3.1
Microsoft XML Parser 6.0

Is this a known issue and has it been resolved? Any ideas.

[jimo]

I don't know if this has been resolved in the latest build or not but I would start by downloading Version 6.13 (Build cambridge_sp3.1407 from the InstallAware website, be sure to regenerate your license on the myinstallaware.com website.

[MichaelNesmith]

IA installs the same packages from the .NET 3 installer that Microsoft provides, so hard to see why there would be a difference.

Let us know when you find out more.

[peter_ashworth]

I downloaded the latest version of InstallAware today (Version 6.14 Build cambridge_sp4.011107), and the problem is still there.

I really need this to be fixed. As I have said, my application works correctly if we install the redistributable from the Microsoft Website, but this looks very untity in an install.

Help!!!!

[MichaelNesmith]

Please substantiate your report by indicating what is not being installed compared to the original Microsoft package. IA runs the original Microsoft package anyways, as I have already said.

[peter_ashworth]

Michael,
Thanks for the reply. I have carried out some more investigations. The WindowsCodecs.dll (version 6.0.5840.16388) is definitely not installed using IA. I am not sure which part of the .Net Framework 3.0 install (dotnetfx3.exe) installs this DLL but as soon as I install this dotnetfx3.exe, the WindowsCodecs.dll is installed and therefore my application works. I have performed this test on a number of computers.

There may be some more DLLs that are not being installed, but I have not noticed, and I do not have any monitoring software.

C:\\WINDOWS\\system32\\WindowsCodecs.dll

Peter

[peter_ashworth]

I think I have found a clue. In the Install Aware script "setupnet30" there are references to installing parts of the .Net 3.0 framework. Missing from here is a reference to install the Windows Imaging Component. This component is found in the .Net 3.0 redistributable from Microsoft (if extracted it can be found in the following location: \\wcu\\WIC\\WIC_X86_ENU.exe).

After extracting this exe I found the WindowsCodec.dll among others. Can this be added to the .Net Application Runtime in Install Aware or is it available else where?

I am continuing my investigation.

[MichaelNesmith]

Hi Peter,

I was looking into this for you, but I think you beat me to it.

You can simply update your setupnet30 script to add this component. Just follow the same examples as in the rest of the script.

Is this bit a standard part of the framework that needs to be included with all .NET3 installs, you think?

[peter_ashworth]

I think that it is important to include this part of the .Net distribution. I have taken a look at the code and tried to copy it to add the extra exe. However I keep on getting an error which suggests that it cannot find the .exe.

Would it be possible for someone at InstallAware to modify the standard script to add this in. I am sure it will be of benefit to a lot of people as it enables the new .Net 3.0 way of converting image types.

Thanks

Peter

[MichaelNesmith]

Sure, we'll post an updated script.

[peter_ashworth]

This now appears to be working with the new version of InstallAware. Thanks.