http://jimmy.schementi.com/silverlight/Chiron.zip This contains Chiron.exe, the Silverlight development web server for Dynamic Languages, with a fix for the IPv4/6 issues. Let me know if anyone has issues on Firefox on either Windows or Mac. This fix will appear on Codeplex in a week. I haven't fixed the "file:///" bug on the Mac yet since it doesn't repro on Windows ... so it probably (?) is a Mono bug. I'll see if I can work around it, but in the meantime you can just do "Chiron /m /d:app" to generate the AppManifest.xaml to disk ... then you can edit it and remove the "file://"s (leave one "/" in the front though!). More information about the issue To understand the bug a little more, Chiron currently tries to listen on IPv6 first, and if that fails it then tries to listen on IPv4. While that’s a fine solution for Vista/XP/Mac, as well as browsers that are tied to their operating system’s network settings (IE, Safari), it’s a problem for browsers that support both in some configurable manner (Firefox). The new behavior is to listen on both IPv6 and IPv4 when it can, but not fail if IPv6 fails. This will work on both IPv6/v4 operating systems (so Vista/XP/Mac will both work), as well as v4/v6 configurable browsers (Firefox), no matter what their settings. In the future Along other Chiron news, I’m also planning on removing the “only works on localhost” constraint. I don’t think it’ll be difficult, but I just need to find hacking time. =) I find it useful because I’d like to do development on one machine and browser to it with another machine, especially if I’m testing different browsers. Would others find it useful as well?
- Silverlight (30)
- Microsoft (20)
- ruby (19)
- Life (16)
- Python (14)
- Dynamic Languages (13)
- rails (12)
- IronRuby (11)
- talks (8)
- Internship (6)
- Lang.NET (5)
- Open Source (5)
- Testing (5)
- assistment (5)
- IronPython (4)
- RailsConf (4)
- Seattle (4)
- Windows (4)
- wpi (4)
- MacOSX (3)
- ASP.NET (2)
- C# (2)
- DLR (2)
- DevConnections (2)
- MSDN (2)
- REPL (2)
- Silverline (2)
- .NET 4.0 (1)
- ASP (1)
- Apple (1)
- Chiron (1)
- CodePlex (1)
- Cucumber (1)
- Dbus (1)
- Firefox (1)
- Flickr (1)
- Hack (1)
- Head First OOAD (1)
- IIS (1)
- Internet Explorer (1)
- JSON (1)
- JScript (1)
- Java (1)
- Linux (1)
- MIX08 (1)
- MacDrive (1)
- Performance (1)
- Pidgin (1)
- Release (1)
- SQLServer (1)
- Sinatra (1)
- Twitter (1)
- Visual Studio (1)
- VisualBasic (1)
- WPF (1)
- Walk Through (1)
- WebCam (1)
- Windows 7 (1)
- bob ross (1)
- christmas (1)
- css (1)
- game (1)
- git (1)
- graduation (1)
- html (1)
- new york (1)
- nichum (1)
- rafferty (1)
- rational edge (1)
- review (1)
- smpl (1)
- tutorial (1)
- webdesign (1)
- wii (1)
- worcester (1)
5 comments:
Do you test Silverlight and Chiron on the Mac?
Not as a checkin gate (we don't have any Macs in our checkin/build labs) but have a Macbook as my main work machine and I'm doing making SL apps on it all the time; which is why I'm a little confused as to "why" this doesn't work for you, and I definitely *had* it working for me, Gotta look into it.
Why what doesn't work for me?
Do the guys who are responsible for the Safari plugin and the Mac installer test on a Mac?
>Why what doesn't work for me?
The urlPrefix adding file:/// uris; I use that all the time on the mac, and I've only recently seen that behavior. That's what I was referring to when I said "it" =)
> Do the guys who are responsible
> for the Safari plugin and the Mac
> installer test on a Mac?
Short answer: oh yeah.
Long answer: Part of the "Silverlight check-in process" requires a full-stack build of Windows, Mac, along with a running a ship-stopper-checking test suite, before checkin. Also, builds are created daily, for Windows and Mac, and the full test suite is run daily against them. On top of that, there are a bunch of QA folks who run browser tests in Internet Explorer, Firefox, and Safari.
Maybe the urlprefix problem is due to a recent Mono or OSX change? (More likely Mono and probably not worth testing on previous versions to find out).
Cool about the testing. I was pretty sure there was *some* testing on the Mac going on. :-)
Post a Comment