I'm using the microsoft "Walkthrough: Creating a Custom Web Service"
white paper to test out this scenario and I have come across a snag.
When I try and run disco.exe to create the .disco and .wsdl files I
get the error:

Could not load the file or assembly 'SharepointCustomLibrary, Version
1.0.0.0, Culture=neutral, PublicKeyToken=986c3ed4d8aaa298 or one of
its dependencies. the system cannot find the file specified.

I run disco.exe locally and the site is hosted on the sharepoint
server. The server displays the Microsoft .net framework 1.1
configuration admin tool but not the 2.0 config tool. When I try to
add my assembly to the GAC through the 1.1 admin tool it says it can't
because it does not have a strong name (even though it really does).
I can add it however if I just drop it into the %windows%\assembly
directory.

Does anyone know what the problem might be here?

Thanks.

Re: custom web service for sharepoint HELP! by Laurent

Laurent
Fri May 11 02:48:16 CDT 2007

Hi,

Use "Visual Studio 2005 Command Prompt" to run gacutil or other command to
be sure using the good version.

--

Laurent Cotton
www.bewise.fr


"goHawkeyes" <linda@boystown.org> wrote in message
news:1178823426.855956.302030@p77g2000hsh.googlegroups.com...
> I'm using the microsoft "Walkthrough: Creating a Custom Web Service"
> white paper to test out this scenario and I have come across a snag.
> When I try and run disco.exe to create the .disco and .wsdl files I
> get the error:
>
> Could not load the file or assembly 'SharepointCustomLibrary, Version
> 1.0.0.0, Culture=neutral, PublicKeyToken=986c3ed4d8aaa298 or one of
> its dependencies. the system cannot find the file specified.
>
> I run disco.exe locally and the site is hosted on the sharepoint
> server. The server displays the Microsoft .net framework 1.1
> configuration admin tool but not the 2.0 config tool. When I try to
> add my assembly to the GAC through the 1.1 admin tool it says it can't
> because it does not have a strong name (even though it really does).
> I can add it however if I just drop it into the %windows%\assembly
> directory.
>
> Does anyone know what the problem might be here?
>
> Thanks.
>