Friday, June 03, 2011 1:33 PM
Am writing a Dryad application (library) which needs to be pushed to GAC, made available as a component for other applications (pushing to GAC is a requirement).
The Dryad Dlls am referencing in the app (Microsoft.Hpc.Linq.dll and Microsoft.Hpc.Dsc.dll) also have to be signed and pushed to GAC for the library to work.
Please let me know how can I achieve this.
This is a showstopper for us, your suggestions are highly appreciated.
Friday, June 03, 2011 10:59 PM
The RTM build will ship with strongly named assemblies that can be referenced by GACed assemblies. For the beta if you really need this to work you could possibly disable strong name verification. Obviously this is not recommended for production environments but would allow you to make progress on a dev/test environment.
- Proposed As Answer by Ade Miller Friday, June 03, 2011 11:00 PM
Saturday, June 04, 2011 4:38 AM
Thanks for replying, I tried disabling strong name verification of the signed dryad assemblies (I did strong name the dryad dlls), but even after that the build errors remain same. Is there any other fix so that I can continue with further development. This has actually been a ROAD BLOCK for us.
Saturday, June 04, 2011 5:57 PM
The only other workaround I can suggest is the following. Obviously this is only a temporary fix
But it may get you unblocked. I've not tried this so I don't know if it will fix the issue.
This will be resolved for RTM.
- Proposed As Answer by Ade Miller Saturday, June 04, 2011 5:57 PM