If you select a server in the New Flex Project wizard then you will need a local server.
My server(s) are not local so I create a New Flex Project without specifying a server and then create RemoteObjects in ActionScript targeting my server. WebORB just makes it easy to connect with a back end server using AMF (RemoteObjects). If you don't want to do that and are happy with XML responses from the ASP.NET services then just use HTTPService calls. Another option is SOAP calls if they already have it available. --- In [email protected], Blair Cox <blair....@...> wrote: > > I only thought I required the Windows version because when you start a new > project and select ASP.net as the server, it requires the dev server or IIS > to be local. I would like to stay away from third-party add-ins for > communicating with the ASP server. I have to follow the rules of the > client¹s IT department. Minimal boat rocking here. > > How about WSDL? > > -- > Blair > > > > > > From: valdhor <valdhorli...@...> > Reply-To: <[email protected]> > Date: Fri, 09 Jan 2009 15:43:55 -0000 > To: <[email protected]> > Subject: [flexcoders] Re: Installation on multiple machines (was: Flex > Builder 3 on Mac and Win at same time?) > > > > > You can use the Mac version of Flex Builder to build a SWF that > connects to ASP.NET using WebORB. > > Why do you need the Windows version of Flex Builder? >
