WAMP server, localhost is not working

Solution(s) for this, found in the official wampserver.com forums:

SOLUTION #1:

This problem is caused by Windows (7) in combination with any software that also uses port 80 (like Skype or IIS (which is installed on most developer machines)). A video solution can be found here (34.500+ views, damn, this seems to be a big thing ! EDIT: The video now has ~60.000 views ;) )

To make it short: open command line tool, type "netstat -aon" and look for any lines that end of ":80". Note thatPID on the right side. This is the process id of the software which currently usesport 80. Press AltGr + Ctrl + Del to get into the Taskmanager. Switch to the tab where you can see all services currently running, ordered by PID. Search for that PID you just notices and stop that thing (right click). To prevent this in future, you should config the software's port settings (skype can do that).

SOLUTION #2:

left click the wamp icon in the taskbar, go to apache > httpd.conf and edit this file: change "listen to port .... 80" to 8080. Restart. Done !

SOLUTION #3:

Port 80 blocked by "Microsoft Web Deployment Service", simply deinstall this, more info here

By the way, it's not Microsoft's fault, it's a stupid usage of ports by most WAMP stacks.

IMPORTANT: you have to use localhost or 127.0.0.1 now with port 8080, this means 127.0.0.1:8080 or localhost:8080.

You can use any license you wish with .NET - the framework and platform does not lock you into any specific license.

As for your specific questions:

I'm partial to a Apache/BSD style license; but can I use that with .NET?

Yes, this is perfectly acceptable to use for .NET applications, and a good option, along with the MIT license.

Can I use GPL and still let people use it in commercial applications?

GPL does put fairly strong restrictions on usage, which tends to limit the commercial uptake (since it forces users to redistribute their application based on your library as GPL). LGPL is an option that doesn't prohibit commerical usage nearly as much, though.

Or should I be using something like the Microsoft Permissive License?

This is much more commonplace with .NET libraries, and will be much more familiar to many .NET developers. If you are happy with the terms of this license, its a very good option (at least, in terms of not limiting usage by license alone).