http://www.itwriting.com/phorum/list.php?3 EN Wed, 29 Sep 2010 09:08:46 +0100 Wed, 29 Sep 2010 09:08:46 +0100 HtmlEditor Phorum 5.1.25 60 http://www.itwriting.com/phorum/read.php?3,1825,4637#msg-4637 poonguzhali HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,4637#msg-4637 Wed, 29 Sep 2010 09:08:46 +0100 http://www.itwriting.com/phorum/read.php?3,1825,1995#msg-1995 James Hancock
MS is still stuck in Windows 3.1 days in their minds. Lots of people at MS are finally figuring this out and pushing MS to change the recomendations. (I've talked to them directly, and ClickOnce is phase one of this)]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1995#msg-1995 Sun, 01 May 2005 23:08:55 +0100 http://www.itwriting.com/phorum/read.php?3,1825,1982#msg-1982 Lior Ben Dror
I wouldn't disregard Microsoft's recommendation about installing PIAs in the GAC:

I have a .NET application which is using the Microsoft.mshtml PIA. It frequently experienced exceptions with a message saying that the Microsoft.mshtml assembly or one of its dependencies is missing. Weirdly enough, this happens on some machines, but works fine on others! (actually, it works fine on the majority of machines)

This problem was solved once I installed the mshtml PIA in the GAC.

Hope this helps,

Lior]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1982#msg-1982 Fri, 22 Apr 2005 20:35:30 +0100 http://www.itwriting.com/phorum/read.php?3,1825,1860#msg-1860 James Hancock
DLL Sucks = DLL Hell Sucks

"for ms.net framework related stuff only" = "only stuff from MS that is isntalled by the .net framework installer"]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1860#msg-1860 Wed, 09 Feb 2005 22:26:55 +0000 http://www.itwriting.com/phorum/read.php?3,1825,1832#msg-1832 James Hancock
Why?

Because people have huge hard drives and it doesn't matter any more, and DLL sucks.

Because upgrading a file in the GAC programmatically afterwards with an update utililty is problmatic at best.

Because if you put it in your application directory debugging becomes easy. Something not working? Great copy over the entire directory from another computer that's working and you're done.

Etc. etc. etc.

My personal opinion is that the GAC should be for MS .NET Framework related stuff only.]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1832#msg-1832 Fri, 28 Jan 2005 14:42:47 +0000 http://www.itwriting.com/phorum/read.php?3,1825,1828#msg-1828 Tim
Yes, because the managed assembly is a wrapper for mshtml itself, which is part of IE. MSDN has some code for checking the IE version. You could simply advise users to upgrade, rather than supplying the IE setup yourself.

Tim]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1828#msg-1828 Tue, 25 Jan 2005 14:48:03 +0000 http://www.itwriting.com/phorum/read.php?3,1825,1827#msg-1827 George Soules
Thanks for the advice. It had not occurred to me that there were IE dependencies as well. If we go the simple route of simply copying Microsoft.mshtml.dll to our application folder and ignoring the GAC altogether, do we still need to check that IE 6 is installed?

George

]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1827#msg-1827 Tue, 25 Jan 2005 14:33:22 +0000 http://www.itwriting.com/phorum/read.php?3,1825,1826#msg-1826 Tim
First, your setup should check for IE 6.0 and offer to install it if not present. This will upgrade the unmanaged mshtml components. IE 5.5 is meant to be sufficient, but I feel safer with IE 6.0.

As for mshtml, here are two sensible options. You can stick in the GAC; if you do, you are meant to use the Windows Installer. A VS.NET setup project works fine. You are not meant to use gacutil for deployment. Regasm isn't necessary for Microsoft.mshtml.dll; in fact, I'd have thought it might mess things up.

The other idea is to copy it to the application folder. As you say, you could avoid this if it is already in the GAC. I doubt it would do any harm though.

Not sure what the official position is, but I noticed that Microsoft say the Office XP PIAs should be installed in the GAC; I guess the same might apply to mshtml.

Tim]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1826#msg-1826 Mon, 24 Jan 2005 23:25:34 +0000 http://www.itwriting.com/phorum/read.php?3,1825,1825#msg-1825 George Soules
The simple approach is to simply copy the dll to our application directory. However, if the user already has a copy on their machine, we will be giving them another.

A better approach would be to check the Global Assembly Cache to see if the dll is already installed, and if it is, use the installed version. A risk there is that if the user uninstalls the dll, our app will no longer work.

If we don't find the dll on the user's machine, we could use gacutil and regasm to install it, but where should we copy the 8MB dll file to?

Given that Microsoft.mshtml.dll is a Microsoft product, there ought to be some guidelines for dealing with it, but we have not yet discovered them.

Has anyone had to deal with this and/or know how it should be done?

George

]]> HtmlEditor http://www.itwriting.com/phorum/read.php?3,1825,1825#msg-1825 Mon, 24 Jan 2005 22:19:09 +0000