Member Avatar for caily

I run on a MAC.

I currently am trying to add a login capability for multiple users to a website. The programmer who will be hosting/developing the web service using Microsoft .NET has left the integration and setup of the web service technology into Dreamweaver to me (as the web designer).

Dreamweaver documentation to install and configure a proxy generator states: "If you are developing web service pages for use with ASP.NET, you must install the ASP.NET SDK, which is available from Microsoft."

All of my searches ultimately lead me to:

Note: Currently, web services development with Dreamweaver is limited to the Windows environment.
System Requirements
Supported Operating Systems: Windows 2000; Windows Server 2003; Windows XP

Does anyone know where to download MAC compatible software?

  • 3 Contributors
  • 2 Replies
  • 196 Views
  • 1 Month Discussion Span
  • Latest Post Latest Post by AICkieran

Dani AI

Generated

Practical options for a Mac-based Dreamweaver designer who needs to integrate an ASP.NET login service (given that the programmer will develop and host the service, as described):

  • Have the programmer produce the client-side artifacts. The simplest route is to ask the .NET developer to run the proxy/generator on a Windows machine and hand over the generated JavaScript (or a tiny wrapper endpoint). The designer then places that script in the site and includes it with a normal <script src="..."></script> tag so the generated functions can be called from the page.

  • Use a lightweight REST/JSON endpoint instead of the full SOAP proxy. A small POST-based login endpoint is language-agnostic and removes the need for Dreamweaver’s Windows tooling. Returning compact JSON makes frontend integration trivial and avoids SOAP/XML parsing in the browser.

  • If local generation on the Mac is required, run Windows in a VM or on a remote Windows host to produce the proxy (an approach similar to the Virtual PC suggestion from ).

Example client pattern for a REST-style login (illustrative):

fetch('/auth/login', {
  method: 'POST',
  headers: { 'Content-Type': 'application/json' },
  body: JSON.stringify({ username: uname, password: pwd })
})
.then(r => r.json())
.then(res => {
  if (res.success) window.location = '/members';
  else showError(res.message);
});

Quick checklist to pass to the programmer: provide the WSDL or login endpoint URL; include one or two example requests and responses; indicate expected cookies/session headers; enable CORS if the service is on a different domain; always use HTTPS for credentials. Tying back to ’s point: relying on the developer to supply the proxy or a simple JSON endpoint is usually the fastest, cleanest solution for a Mac-based designer.

Member Avatar for bkendall

I do not believe that there is a mac version of the ASP.NET SDK. I would be interested if anyone comes across a work around for it.

Member Avatar for AICkieran

This is why i prefer php to asp*, its not proprietary shite.
You could always use virtual pc,

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.