Ah yes, the VS tools depend on Chiron. Makes sense. ~Jimmy
On Wed, Aug 25, 2010 at 12:15 PM, Dino Viehland <di...@microsoft.com> wrote: > So that when we do a build for the MSI it’ll get built in the same way > that it does for “Silverlight4Release” and “Silverlight4Debug”. That lets > us just kick off 1 msbuild and get the resulting binaries. > > > > I could also look at making us do a separate build for that if necessary > but it seems like building it w/ the desktop binaries is fine. > > > > *From:* users-boun...@lists.ironpython.com [mailto: > users-boun...@lists.ironpython.com] *On Behalf Of *Jimmy Schementi > *Sent:* Wednesday, August 25, 2010 8:57 AM > *To:* Discussion of IronPython > *Subject:* Re: [IronPython] IronPython 2.6 CodePlex Source Update > > > > How come a Debug/Release configuration was added to Chiron.csproj? > ~Jimmy > > On Wed, Aug 25, 2010 at 11:48 AM, <merl...@microsoft.com> wrote: > > This is an automated email letting you know that sources > have recently been pushed out. You can download these newer > sources directly from > http://ironpython.codeplex.com/SourceControl/changeset/view/76456. > > MODIFIED SOURCES > $/IronPython/IronPython_Main/Hosts/Silverlight/Chiron/Chiron.csproj > $/IronPython/IronPython_Main/Msi/IronStudio/IronStudio.msm.wproj > > > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > > > > _______________________________________________ > Users mailing list > Users@lists.ironpython.com > http://lists.ironpython.com/listinfo.cgi/users-ironpython.com > >
_______________________________________________ Users mailing list Users@lists.ironpython.com http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
