tag:blogger.com,1999:blog-5419182.post4772978386714751892..comments2008-09-12T15:24:25.843-07:00Jimmy Schementihttps://profiles.google.com/116380716127564408544noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-5419182.post-35016454822820011612008-09-12T15:24:00.000-07:002008-09-12T15:24:00.000-07:00Some name suggestions: <BR/>SDLK; (Using just K for SDK)<BR/>DynaK; (Read dyna - K (K-e-y))<BR/>SilK; (Not bad!)<BR/>SilverDK;<BR/>DynamicLight; (Mmm...)<BR/>DylaK;<BR/>Sidyla; (Mm..)<BR/>...<BR/>Just some came to my mind! :)Kaveh Shahbazianhttp://www.blogger.com/profile/05485737252432475634noreply@blogger.comtag:blogger.com,1999:blog-5419182.post-74133100287023439752008-09-02T17:12:00.000-07:002008-09-02T17:12:00.000-07:00@paul Awesome! Actually, Chiron is a exe that runs on the desktop CLR, so no work is needed to get that working =) If everything else builds, then your patch should be good to go. I'll check it out and let you know.Jimmy Schementihttp://www.blogger.com/profile/05370777584064015818noreply@blogger.comtag:blogger.com,1999:blog-5419182.post-10931762428655354292008-09-02T17:10:00.000-07:002008-09-02T17:10:00.000-07:00I uploaded a patch to CodePlex that builds for the client framework in VS 2008. Haven't tested it, but everything (except chiron) builds correctly.<BR/><A HREF="http://www.codeplex.com/Project/Download/FileDownload.aspx?ProjectName=sdlsdk&DownloadId=42891" REL="nofollow">Download Patch</A>paulhttp://www.blogger.com/profile/06570093931665451972noreply@blogger.comtag:blogger.com,1999:blog-5419182.post-66452065333530669022008-09-01T16:44:00.000-07:002008-09-01T16:44:00.000-07:00@apl: Unfortunately there's no similar package for the desktop. The root problem is all our source-control, continuous integration, and daily build machines are part of either VS or CLR's internal systems, so giving people access to that is next to impossible. Also, we don't have someone who can test the builds work together (like a test-pass, which consists of manual tests as well). In the future the languages will all depend on a single version of the DLR, so this won't be a problem anymore, but until then it does suck. Expect that in the fall.<BR/><BR/>However, it should be just a matter of changing the project file references to point to desktop assemblies. I know Ivan (http://flanders.co.nz/) has done this before.Jimmy Schementihttp://www.blogger.com/profile/05370777584064015818noreply@blogger.comtag:blogger.com,1999:blog-5419182.post-9920919837185061362008-08-31T10:50:00.000-07:002008-08-31T10:50:00.000-07:00In France we say <BR/><BR/>"""<BR/>la parole est d'argent<BR/>le silence est d'or<BR/>"""<BR/><BR/>so i propose<BR/><BR/>SilverWhisper Kit<BR/><BR/>then you can start the google battle for SWK ranking :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5419182.post-10645492800421294722008-08-31T03:57:00.000-07:002008-08-31T03:57:00.000-07:00Great news. Just a quick question, do you know anything about similar package (latest binaries of the DLR, IronRuby, IronPython and Managed JScript), but for the desktop CLR?aplhttp://www.blogger.com/profile/14783143626906780756noreply@blogger.com