Yes sure,webservice runs under asp.net framwork and if you want to protect your application, then you should apply the workaround.
Note: if you are using WCF services (not web services), that would depends on where you host the service.If you host it under asp.net , then you still need the workaround.However, if you host it using windows service or any hosting service other than the
asp.net, then you will not need the workaround.
sgraddy
0 Points
1 Post
Web Services Workaround
Sep 21, 2010 12:04 PM|LINK
Does the recommended error page workaround also work for an asp.net web service?
anas
All-Star
73649 Points
7914 Posts
Moderator
Re: Web Services Workaround
Sep 21, 2010 12:10 PM|LINK
Yes sure,webservice runs under asp.net framwork and if you want to protect your application, then you should apply the workaround.
Note: if you are using WCF services (not web services), that would depends on where you host the service.If you host it under asp.net , then you still need the workaround.However, if you host it using windows service or any hosting service other than the asp.net, then you will not need the workaround.
dkarantonis
Member
135 Points
214 Posts
Re: Web Services Workaround
Sep 22, 2010 03:06 PM|LINK
How does the workaround is implemented an a web or wcf service?
Should someone create an Error.aspx page? Since the service is page-less.
thanks
dkarantonis
Member
135 Points
214 Posts
Re: Web Services Workaround
Sep 22, 2010 04:49 PM|LINK
Ok, i've implemented it.
lendog75
Member
16 Points
5 Posts
Re: Web Services Workaround
Sep 22, 2010 05:08 PM|LINK
Did You make an Error.aspx page as mentioned above? Since a web svc has nointerface it seems akward to me, looking for input...
-Lenny
dkarantonis
Member
135 Points
214 Posts
Re: Web Services Workaround
Sep 22, 2010 05:36 PM|LINK
Yes i've created an Error.aspx file and modified the web.config.
I didn't create it on the web service but on the site that hosts the wcf service.
Hope this helps.