I had a go at removing it (see the newly commented code in the utility), but it didn't pan out well. So for now, yes, it needs to be on the path - but I hope not for long. There's a few pieces of code in there trying to figure out if a reference is in the GAC from just a name that is imperfect. Another thing this is needed is to use AppDomains so all the libraries aren't loaded up into the addin's assembly space.
- Brett On 02/07/2011, at 3:12 PM, John Fallows wrote: > Devs, > > In one of the recent releases a lot of work was done on the plugins to > ensure that the environment PATH did not need to be set in order to locate > various utilities such as csc.exe, etc, so I don't have them on my path any > more to avoid unanticipated side effects. > > However, it seems that the VisualStudio ProjectImporter Engine project fails > to build due to an exception in GacUtility when it is unable to locate > gacutil.exe because it is not on the path. > > Is the PATH requirement for gacutil.exe intentional? > > tc, > -john. > -- >> |< Kaazing Corporation >|< > John Fallows | CTO | +1.650.960.8148 > 444 Castro St, Suite 1100 | Mountain View, CA 94041, USA -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter
