RE: Another typical problem

[Greg Keogh]

Chaps,

 

I just got home after another day of suffering in a different office.
Brendan, I do like to use svcutil to generate proxies for non-Silverlight
projects. I wanted to do the same for SL projects but never found out what
"trick" the build process was using to generate the code behind the "Add
Service Reference". Thanks for pointing out that slsvcutil
  exists,
and I'll give it a bash on the weekend and hopefully it will replace project
references and prevent such suffering as I had this morning.

 

I'm familiar with cross-domain errors and have had them before when I
accidentally had the service and the client running in different ways (in
IIS or the lightweight sever). I guess in my anger this morning I forgot to
check in fiddler what was happening, but I didn't change any networking code
and didn't expect to find problems there.

 

Chris, "Maybe your Silverlight project is set as the startup project, hence
the issue." - I have done this before by accident and it produces a stinkin'
mess of misleading errors. I'm not sure if I did it this morning in my
confusion.

 

By randomly restoring files I eventually managed to get the projects working
again, but I don't know how because I changed so many things so rapidly.

 

Oh well, at least I'm going again for some reason or other.

 

Greg 

 

___
ozsilverlight mailing list
ozsilverlight@ozsilverlight.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

In praise of slsvcutil.exe

[Greg Keogh]

Folks,

 

Thanks to a hint by Brendan in the Silverlight forum I was led to find this
utility (on my machine):

 

"%ProgramFiles(x86)%\Microsoft SDKs\Silverlight\v4.0\Tools\slsvcutil
 .exe"

 

Thank heavens for this, as it means I can now generate the service reference
code for a Silverlight project the same way I have been using svcutil for
normal projects. I haven't used the "Add Service Reference" in normal
projects for years because the code generated by svcutil is easier to
control and far less cluttered. I highly recommend that people gen the code
this way instead of using "add reference".

 

I was wondering what the equivalent was for SL projects and what the build
process what doing internally. Ages ago I used some monitoring tools and
various tricks to find what was happening internally but was defeated and
gave up. I'm not sure if slsvcutil existed then, but it does now. I also
fell for the bug described here
  and had to use the
workaround to get slsvcutil working.

 

I hope this tool helps others avoid the shocking problems I had this morning
with a "corrupt" service reference.

 

Greg

___
ozsilverlight mailing list
ozsilverlight@ozsilverlight.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight

Re: In praise of slsvcutil.exe

[Miguel Madero]

Hi Greg,

As an alternative to 'Add Service Reference' and even 'slsvcutil/svcutil'
you could use AutoServiceProxy, just by sharing DataContracts and
ServiceContracts you don't really need the proxy. Have a look at the
project in bitbucket.

https://bitbucket.org/mamadero/sltoolsdemo



Miguel A. Madero Reyes
www.miguelmadero.com (blog)
m...@miguelmadero.com


On Thu, Mar 29, 2012 at 6:02 PM, Greg Keogh  wrote:

> Folks,
>
> ** **
>
> Thanks to a hint by Brendan in the Silverlight forum I was led to find
> this utility (on my machine):
>
> ** **
>
> "%ProgramFiles(x86)%\Microsoft 
> SDKs\Silverlight\v4.0\Tools\slsvcutil
> .exe"
>
> ** **
>
> Thank heavens for this, as it means I can now generate the service
> reference code for a Silverlight project the same way I have been using
> svcutil for normal projects. I haven’t used the “Add Service Reference” in
> normal projects for years because the code generated by svcutil is easier
> to control and far less cluttered. I highly recommend that people gen the
> code this way instead of using “add reference”.
>
> ** **
>
> I was wondering what the equivalent was for SL projects and what the build
> process what doing internally. Ages ago I used some monitoring tools and
> various tricks to find what was happening internally but was defeated and
> gave up. I’m not sure if slsvcutil existed then, but it does now. I also
> fell for the bug described 
> hereand
>  had to use the workaround to get slsvcutil working.
> 
>
> ** **
>
> I hope this tool helps others avoid the shocking problems I had this
> morning with a “corrupt” service reference.
>
> ** **
>
> Greg
>
> ___
> ozsilverlight mailing list
> ozsilverlight@ozsilverlight.com
> http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight
>
>
___
ozsilverlight mailing list
ozsilverlight@ozsilverlight.com
http://prdlxvm0001.codify.net/mailman/listinfo/ozsilverlight