Tolga Koseoglu - All Comments

re: Silverlight 2.0 and WCF

Dipal Bhavsar — Wed, 11 Nov 2009 10:17:18 GMT

Hello embody of group,

I have been facing one problem while consuming web services from WCF in my silverlight application.

The error title and description are following...

Error Title : ComminicationException was unhandled by user code

Error Description:

An error occurred while trying to make a request to URI 'localhost/.../EmpService'. This could be due to attempting to access a service in a cross-domain way without a proper cross-domain policy in place, or a policy that is unsuitable for SOAP services. You may need to contact the owner of the service to publish a cross-domain policy file and to ensure it allows SOAP-related HTTP headers to be sent. This error may also be caused by using internal types in the web service proxy without using the InternalsVisibleToAttribute attribute. Please see the inner exception for more details.

What does it mean by?

What is the proper solution for it.

I have been refer the following link as I am totally new in SilverLight.

www.dotnetcurry.com/ShowArticle.aspx

Please suggest me the proper solution.

Thanks.

re: Web UserControls (.ascx) and validations...

kinjal — Sat, 27 Jun 2009 07:13:09 GMT

Thanks for the solution..Its really help ful to me......

re: Getting Powershell to work in your asp.net application

Stefano Parini — Thu, 29 Jan 2009 11:14:20 GMT

I noticed that the error occurs using write-host

is it possible?

re: C# version of Silverlight Page Turn

deviations — Tue, 07 Oct 2008 14:20:30 GMT

You have here another nice implementation:

blogs.msdn.com/.../silverlight-2-beta-2-page-turn.aspx

re: Saved passwords after deploying web applications

Moss — Thu, 02 Oct 2008 20:04:08 GMT

This is pretty useless, like most of your recent posts.

re: C# version of Silverlight Page Turn

silverUser — Wed, 03 Sep 2008 16:31:24 GMT

hi tolga

i can't see sample, beacuse it need a specific version

of silverlight.

?!?!?!

can you post source code ?

thanks in advance

asp operation aborted hotfix

asp operation aborted hotfix — Wed, 09 Jul 2008 23:50:52 GMT

Pingback from asp operation aborted hotfix

re: Complete hide textbox without loosing functionality

Jason Clark — Wed, 02 Jul 2008 13:18:42 GMT

Actually, instead of Visible="False" (which doesn't render the control in the DOM), you could just do style="display:none;" which hides the control on the page, but still renders it on the DOM, and allows you to do anything with it you desire.

It also reduces the amount of code you have to write to do the exact same thing.

re: Complete hide textbox without loosing functionality

Mark Hildreth — Mon, 30 Jun 2008 20:16:45 GMT

Alternatively, you can just add the attribute Visible="false". That has has the added benfit that if would prevent someone from just viewing the page source and discovering the textbox value.

re: Complete hide textbox without loosing functionality

markvt — Mon, 30 Jun 2008 18:30:48 GMT

It's not hidden it's still on the page and someone could select it when clicking init.

Why not use a session variable?