Flex Components is not really the right place for a Flex 3 beta discussion. but having said that the first place I would look is the CrossDomain xml file (or whatever it is called) that is required for Flash to talk to servers other than local. We had a similar issue with a Flex 2 app at work talking to a .NET service.
In addition ASP.Net 2 adds several enhancements to the webservice core libraries that make it much more robust, but from your example it does not appear to be an issue. Would probably help if you had included the exact error message you receive when making the request. Something else to consider is using a REST service instead of a SOAP service for simplicity (and REST is just better anyways ;) Downloading Flex 3 beta now, but I urge you to hit up FlexCoders or one of the other groups, as this group is specifically about creating components for the Flex framework. Hope I helped somehow, -Marc From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of essuark Sent: Tuesday, June 26, 2007 7:48 PM To: [email protected] Subject: [flexcomponents] Flex 3 and asp.net 2.0 webservices I am DYING here. I am trying to get Flex to talk to a webservice with no luck. It is the BETA to Flex 3. I am not sure where the problem is but here is what I have working.... Flex 3 project talks to a asp.net 1.1 webservice .NET Windowed applications talks to as.net 2.0 webservice So I dont thinks it is Flex 3 and I ensured the service works because I had the C# app talk to it. It is a simple webservice called ping and returns a string of 'ping'. Has anyone made this work? thanks Ralph
