Can anyone fill us in on the design intent behind the gac_msil directory where NPanday keeps Windows assemblies? It doesn't appear to be recognized by Windows as a "real" Global Assembly Cache like C:\WINDOWS\assembly. Is it simply
used as a repository by NPanday by convention?
When I build a .NET project with NPanday it will install the resulting binary in both the maven repository and in gac_msil (~\.m2\repository and ~\.m2\uac\gac_msil) but with different naming conventions. Why both, why not just the maven repository
or just gac_msil?
If a Visual Studio project references a dll (e.g. NLog) I can simply create a directory structure in gac_msil, following the naming convention of other stuff there, copy the nlog.dll in there and then NPanday will find it with a depencency section like this
in the pom:
But that's obviously a back door hack to getting something installed in gac_msil. Isn't there some maven command I should be running to do that? I worked through the wiki article on packaging binaries, but deploy:deploy-file only puts binaries
in the maven repository. The biggest problem with the current 1.0.0 installer, by the way, is that it does not build gac_msil on the target machine.
Last question, can I set up a remote gac_msil repository, as I might set up remote maven repositories? What do I put in settings.xml or npanday-settings.xml to point NPanday at a remote gac_msil? And would it then download artifacts to the local
gac_msil per usual maven behavior?
Thanks very much for your help,