[Mono-devel-list] Potential GAC implementation ideas.

[Todd Berman]

> Anyway, if my understanding is correct, the underlying library can just
> concern itself with paths, right? Ie, we can have a simple interface
> like:
> 
> 	char *gnugac_get_path_to_assembly (char *asm);
> 	char *gnugac_get_path_to_assembly_full (
> 		char *asm, char *pubkeytok, char *culture);
> 	xid   gnugac_begin_assembly_add (
> 		char *asm, char *pubkeytok, char *culture,
> 		char **dest_path);
> 	void  gnugac_done_adding_assembly (xid transaction);
> 	....
> 
> Then we could write a simple managed interface to it that did all the
> heavy lifting (copying / moving files, pubkey calculation, etc) in
> managed code. Seems to me like this would be a good balance.

I must say, I really do like that idea, and it would be similar to how ms
does it (except our gacutil would call into the managed interface, not the
native library). The unmanaged interface would most likely have to be a bit
more complex than that, but its basically the right idea. The only part
about it I don't like would be my inability to write said native library :P
(well, not inability, reluctance).

> Another question: how does the Mono GAC interact with the Windows GAC,
> if people are using the mono runtime on Windows?

Hmm, hadn't really thought about this, but I assume that the mono would use
the mono gac and .net would use the .net gac, however, I have not done any
thinking about it either.

--Todd