czwartek, 22 listopada 2007

Failed To Create AppDomain

Failed To Create AppDomain

I was playing around with Visual Studio Whidbey last night and had been altering my CAS security policy. I tested what I wanted and forgot all about it.

This morning, I came to play with some of my ASP.NET demo projects and found that when I ran up the local web server I couldn't get any page to display whatsoever (everything was coming back with a "page not found").

I couldn't understand this at all and (having the memory of a goldfish) it took me ages to get back to the point where I worked out when things had last been working and when they'd stopped. I could see in the VS debugger that when the little Visual Web Developer Web Server was coming up it was throwing a "Failed to create AppDomain" exception but I couldn't for the life of me think why that might be given that it'd been working fine up until about half a day ago.

After staring at it for a while I thought a bit about what might go wrong with creating an AppDomain and security suddenly hit me and I remembered that I'd tweaked with my settings last night.

A quick;

caspol -s off

showed me that I could now run up pages in the Web Developer Web Server and a quick

caspol -reset

fixed the problem.

One to bear in mind should you find this page whilst searching for "Failed to create AppDomain".

poniedziałek, 5 listopada 2007

Serwery proxy

Dla użytkowników TPSA
217.98.20.195:8080 (w3cache.tpnet.pl)
217.98.20.20:8080 (w3cache2.tpnet.pl)

Dla użytkowników Dialogu
62.87.244.34:8080 (proxy.dialog.net.pl)

Dla użytkowników TkTelekom
82.160.0.10:8080 (w3cache.tktelekom.pl)
213.199.225.43:8080 (w3cache2.tktelekom.pl)

Dostępne dla wszystkich Polaków
193.219.28.144:8080 (w3cache.icm.edu.pl)
193.219.28.146:8080 (w3cache2.icm.edu.pl)