Does having the ASP.NET web services extension prohibited in IIS negate this vulnerability?
View Complete Post
was giving a though on using ajax enabled wcf services as part of architecture
generally wht im using
is UI-> BL-> data access
is it suggestable to use wcf services layer instead
nd hv UI-> services-> data access
related to asp.net
would like to no pro's and con's of doing this thing.
is it suggestable to do it.
I've been working on my first asp.net application and for the most part it's been pretty smooth. Right now I'm having trouble getting reporting services working under SQL Server 2005. I developed the site with Visual Studio 2010 and didn't think about any of the .Net 4.0 compatibility issues that have arisen. I'm having no problems with the site communicating with SQL Server 2005 for the regular database stuff. The only problem I'm having is with setting up Reporting Services. I have the .Net 4.0 framework installed on the server, however Reporting Services is still using 2.x. I'm not sure if this is a problem with SSRS or with IIS. When i go to localhost/Reports it's reading my web.config for my application and throwing an error: "Parser Error Message: Unrecognized attribute 'targetFramework'." This is referring to a line in my web.config where targetFramework is set to 4.0.
Software that I'm using:
how to get a report in my c#.net page button lick event also steps to call a report from asp.net to reporting services
Thanks in advance
Learn how to use the AtomPub protocol to pump up your blogs. Chris Sells includes a practical demonstration of mapping so you can expose a standard AtomPub service from a Web site and use Windows Live Writer to provide a rich editing experience against the service.
MSDN Magazine August 2010
Office 2010 and SharePoint 2010 include a new set of components called Application Services. These put a rich set of tools in a developer's bag for Office automation. We'll show you how to use Office OpenXML, Word Automation Services and SharePoint to build a simple application that merges separate status reports into a single document.
Manvir Singh, Ankush Bhatia
MSDN Magazine July 2010