Original Post
I’ve spent hours searching the Net for a solution to this problem!
Basically, I need to reference non-local assemblies via the “asmpath:” option which can be used in the Type Library Exporter (TlbExp) tool. However, doing this will cause the tool NOT to look up the Global Assembly Cache (GAC) which, of course, is usually referenced in the vast majority of C# programs.
I’ve located the GAC directory on my machine but it has some spaces;
C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile
and surrounding the directory with quotes doesn’t seem to make TlbExp happy!
I know I could simply copy the assemblies that I’ve written to a specific directory to resolve this issue but, the idea of having multiple copies of assemblies running around on my system doesn’t seem right and, the idea of replacing these copies with new versions seems kinda reminds me of the “DLL Hell” that, supposedly, C# was trying to address!
Furthermore, I’d rather not overload the GAC with my own assemblies so I want them, at least for the time being, to remain private.
I’ll admit, I’m not much of a Command Line Interface guru so, how the heck can this be done? Thanks!
Basically, I need to reference non-local assemblies via the “asmpath:” option which can be used in the Type Library Exporter (TlbExp) tool. However, doing this will cause the tool NOT to look up the Global Assembly Cache (GAC) which, of course, is usually referenced in the vast majority of C# programs.
I’ve located the GAC directory on my machine but it has some spaces;
C:\Program Files\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\Profile
and surrounding the directory with quotes doesn’t seem to make TlbExp happy!
I know I could simply copy the assemblies that I’ve written to a specific directory to resolve this issue but, the idea of having multiple copies of assemblies running around on my system doesn’t seem right and, the idea of replacing these copies with new versions seems kinda reminds me of the “DLL Hell” that, supposedly, C# was trying to address!
Furthermore, I’d rather not overload the GAC with my own assemblies so I want them, at least for the time being, to remain private.
I’ll admit, I’m not much of a Command Line Interface guru so, how the heck can this be done? Thanks!