do-windows team mailing list archive

["Krisztian Gyuris" <gyurisc@xxxxxxxxx>]

I see that as totally doable. The binary compatibility comes with .net/mono
as the byte code is the same I guess. If we can make changes in the core
code, so they start using the extension paths for not only actions and
itemsources, but for UI as well I think this is not unreallistic.

I tried to look at autoconfig some time ago, but I never grok it really. I
gave up. I like msbuild better :)

On Thu, Jul 3, 2008 at 10:51 PM, Brian Pedersen <brian.pedersen@xxxxxxxxx>
wrote:

> Cool, we now have source code also :D
>
> I have been experimenting a bit with the binary compatibility between Mono
> and .NET, and it seems to work quite nice.
>
> I have also been trying to build Do on my linux box, but I got lost in
> autoconf and make, I have never used anything but ant, nant and maven for
> building, so I need to bring myself up to speed with those tools.
>
> It could be really nice if we could end up having 90% of the code in
> cross-platform assemblies and only have a thin platform specific layer.
>
> /Brian
>
>
> 2008/7/3 Krisztian Gyuris <gyurisc@xxxxxxxxxxxxxxxxxxxxx>:
>
>> Blueprint changed by Krisztian Gyuris:
>>
>> Whiteboard changed to:
>>
>> I pushed the my solution. It does not compile yet and need to add the
>> Mono.Addins project to the solution.
>>
>> [03.07.2008 brian.pedersen]
>> Initial Visual Studio setup
>> Create project, import source, resolve dependencies - no more than this.
>> We need one person to do this, it doesn't have to be working, but it needs
>> to be pushed to launchpad as soon as it is done in order to avoid the "lone
>> ranger" approach
>>
>> [03.07.2008 Krisztian Gyuris]
>> I started to put together a solution and I have it almost ready for
>> initial checking. I am down to 34 compilation errors this morning :)
>> I will check in what I have this evening.
>>
>> --
>>  Initial Visual Studio setup
>>  https://blueprints.edge.launchpad.net/windo/+spec/vssetup
>>
>
>