Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
Strongly named version of "iManage.WorkSite.Web.Proxies.dll"
wwest
I need a strong named version of the "iManage.WorkSite.Web.Proxies.dll" file that somes with the SDK (under the C:\Program Files\Interwoven\WorkSite\Web\Samples\servicesclient\bin\Release folder) in order to put it in the GAC - can this be had?
Thanks,
-Wilson West
Find more posts tagged with
Comments
dabird
Hi Wilson,
By design we do not sign this assembly, as we do not want it to be placed in the GAC. This is based on Microsoft guidelines found in
Working with Assemblies and the Global Assembly Cache
.
If you want to reuse the assembly in your project, you should copy it to the /bin directory of your project.
Regards,
dabird
wwest
dabird,
Unfortunately, that will not work for us. Our other Assemblies are strongly named and reference the proxy assembly, so they will not compile unless it is also strongly named.
When looking at the Services Client sample application/project supplied with the product, it can't be re-compiled because the project references "..\..\iwcs\Proxies\Proxies.csproj" which is not included - at least not with my installation. Is there a way I can receive this project so that I can at least re-compile the example project supplied? Creating a proxy assembly using the wsdl.exe utility (from MS) doesn't appear to be enough - it doesn't contain info about the connection object, etc.
Thanks,
-Wilson
dabird
Hi Wilson,
Our source code disclosure agreement unfortunately does not cover this project. I realize that it's a sample, but our legal department would not be happy, to say the very least, if I released it without the proper legal documentation in place.
Having said that, I can provide a possible workaround for you. You can use
Reflector
to look at our code and copy it. You can then create a new assembly of your own with our source code pasted into it. After that just sign your new assembly and reference it in lieu of Proxies.
Regards,
dabird
wwest
dabird,
In thinking I wouldn't be able to get it, that's exactly what I did. Thanks for your help.
regards,
-wilson