search

OpenRIAServices / OpenRiaServices

The Open RIA Services project continues what was previously known as WCF RIA Services.
https://openriaservices.gitbook.io/openriaservices/
Apache License 2.0
54 stars 48 forks source link

can't mix signed assemblies on the client with unsigned on the server #62

Closed Daniel-Svensson closed 6 years ago

Daniel-Svensson commented 6 years ago

While troubleshooting another issue, I found that having unsigned assemblies on the server and signed assemblies on the client prevents the CreateOpenRiaClientFilesTask from executing correctly.

While I don't believe this is an issue now, I seem to recall discussion around not signing the server assemblies in the future, when/if that happens I'm thinking this would need to be addressed?

Attachments

OpenRiaServices.Client.CodeGen.4.4.0.3.nupkg

This work item was migrated from CodePlex

CodePlex work item ID: '62' Vote count: '1'

Daniel-Svensson commented 6 years ago

[danneesset@2015-02-15] Right before the final 4.4.0.0 release we camo up with a solution that should make the code generation wotk with both signed and unsigened versions of the server assemblies so if this does not work it might indicate a problem with that specific nuget package.

What version of open ria services are you using? can you paste the content of your packages.config?

Daniel-Svensson commented 6 years ago

[danneesset@2015-03-01] I have managed to make some improvements to this which should ship with the next minor update.

With the new solution the normal (unsigned) codegen should work for all scenarios except where the server project uses the T4 template based codegen (when it reference a signed version of the Tools.dll).

The code gen works for me, but I would appreciate if you could test it it. The nupkg is just a zip file so you should be able to open it and replace the contents of your build directory with the new version.

Daniel-Svensson commented 6 years ago

[danneesset@2015-03-01] Fixed in changeset 50d0fa98a3878a88c25f0ef4feb63881822c8ea7

Daniel-Svensson commented 6 years ago

[groovejumper@2015-03-01] Awesome! That did it, thanks danneesset!

I've got the signed assemblies in my client projects (due to 3rd party control requirements), and the unsigned assemblies in the server project, and with the fix you just uploaded it now works great!

PS: While I do want to future-proof, the main reason I was interested in doing this now, is that I'm still having an issue with the tooling/domain service wizard not displaying any context classes when using the signed assemblies on the server. This is no longer an issue with your fix, as I have no need for signed assemblies on the server.