NugetCracker 0.10

Screenshot on MacOSX

Reengineered the BumpVersion command:

Now it bumps all dependent versions numbers and only after that, it builds all needed projects so that a build error can be fixed and the build be restarted without have inconsistent version numbers.

NugetCracker building/bumping itself on Linux, Version 0.6.1

laptop:~/Projects/active/NugetCracker$ ./nugetcracker 
NugetCracker 0.6
See https://github.com/monoman/NugetCracker


Using /home/rafael/Projects/active/NugetCracker/MetaProject.NugetCracker
Scanning '.' > '/home/rafael/Projects/active/NugetCracker'
.
Scanned 144 directories
Found 2 components
Sorting...
Finding dependents...


Ready > l
    Listing all components...
    [0001] Commons.Prevalence.1.0 - Minimal prevalence support for .NET [C# Nuget Project]
    [0002] NugetCracker.0.6 - A builder for versioned nugets within a web of dependencies [C# Project]


Ready > help
    Available Commands:
        BumpVersion     Bumps up a version for a component
        Help, ?         Show this list of commands or an specific command help
        List            List components, optionally filtered by regular expression
        Quit, Exit      Stops interactive mode
        Rebuild         Rebuilds current version for a component


Ready > r Commons
    Rebuilding component Commons.Prevalence.1.0
        XBuild Engine Version 2.11.0.0
        Mono, Version 2.11.0.0
        Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2011.
        Build started 9/11/2011 2:13:20 PM.
        __________________________________________________
        Project "/home/rafael/Projects/active/NugetCracker/Commons.Prevalence/Commons.Prevalence.csproj" (default target(s)):
        Done building project "/home/rafael/Projects/active/NugetCracker/Commons.Prevalence/Commons.Prevalence.csproj".
        Build succeeded.
        Time Elapsed 00:00:00.8898590




Ready > r Nug   
    Rebuilding component NugetCracker.0.6
        XBuild Engine Version 2.11.0.0
        Mono, Version 2.11.0.0
        Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2011.
        Build started 9/11/2011 2:13:46 PM.
        __________________________________________________
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        Project "/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj" (default target(s)):
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        /usr/lib/mono/4.0/Microsoft.Common.targets:  warning : Found a conflict between : 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' and 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Using 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' reference.
        Done building project "/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj".
        Build succeeded.
        Warnings:
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj (default targets) ->
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj (default targets) ->
        /usr/lib/mono/4.0/Microsoft.Common.targets (ResolveAssemblyReferences target) ->
        Time Elapsed 00:00:04.7531090


Ready > help bumpversion
    Usage:


    BumpVersion [options] pattern


Bumps up the [AssemblyVersion]/Package Version of the component and rebuilds/repackages. 
The [AssemblyFileVersion] attribute also is kept in sync with the [AssemblyVersion].
If component generates a Nuget it is not automatically published unless the --cascade 
or --publish options were specified.


Options
-part:major|minor|build|revision|none
Increments the major, minor, build, revision version number. 
If option is ommitted the default is to increment build number.
-dontcascade
Update all dependent components to use the new build/package, and them their dependent 
components and so on. If some components generate a Nuget, the Nuget is published to 
a temporary output 'source' and the dependent components have their package references 
updated, if all goes successfully packages are them published to the default or specified
source.
-publish
Specifies that package should be published if successful.
-to:
Specifies source other than the default to publish nugets to. 


Ready > b nug
    Bumping component 'NugetCracker' version from 0.6 to 0.6.1
    ==== cascading
    Setting new version to 0.6.1
    Building NugetCracker.0.6.1
        XBuild Engine Version 2.11.0.0
        Mono, Version 2.11.0.0
        Copyright (C) Marek Sieradzki 2005-2008, Novell 2008-2011.
        Build started 9/11/2011 2:15:27 PM.
        __________________________________________________
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        Project "/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj" (default target(s)):
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        /usr/lib/mono/4.0/Microsoft.Common.targets:  warning : Found a conflict between : 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' and 'System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Using 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' reference.
        Done building project "/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj".
        Build succeeded.
        Warnings:
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj:  warning : Cannot import project '/usr/lib/mono/4.0/Microsoft.CSharp.targets' again. It was already imported by '/home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj'. Ignoring.
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj (default targets) ->
        /home/rafael/Projects/active/NugetCracker/NugetCracker/NugetCracker.csproj (default targets) ->
        /usr/lib/mono/4.0/Microsoft.Common.targets (ResolveAssemblyReferences target) ->
        Time Elapsed 00:00:04.2109010


Ready > q

Pinta needs help, and I decided to lend a hand...

Pinta is a nice bitmap editing tool, simple and yet powerful, for Linux/MacOSX/Windows

http://www.pinta-project.com/

Jonathan Pobst it's creator and maintainer is focusing his energy on some other ventures and left it untouched for some time know.

Cameron White forked and started to make it tick again, and now Robert Nordan and other people in the project discussion list http://groups.google.com/group/pinta?hl=en, including me , are starting to organize a full project team around it, at github (my fork https://github.com/monoman/Pinta).

I approach this with a more systemic view to have something like the MonoMagic App Wall (chose another name because a store would emphasize a commercial offering), with apps that may be easily installable/usable on any of the miriad platforms where Mono/.NET is available, Pinta could just be the forerunner.

Imagine an iPad/Android version of Pinta, with your drawings/photos synced to your personal cloud storage, so that you can take your editing session back at your Linux notebook later...

Wild ideas...

NugetCracker 0.5 - Runs on Mono 2.11 on Ubuntu

Kind of self-explanatory...

monoman:~/Projects/NugetCracker$ mono NugetCracker/bin/Debug/NugetCracker.exe -c list
NugetCracker 0.4
See https://github.com/monoman/NugetCracker


Using /home/rafael/Projects/active/NugetCracker/MetaProject.NugetCracker
Scanning '.' > '/home/rafael/Projects/active/NugetCracker'
.
Scanned 128 directories
Found 2 components
Sorting...
    Listing all components...
    [0001] Commons.Prevalence.1.0 - Minimal prevalence support for .NET [C# Nuget Project]
    [0002] NugetCracker.0.4 - A builder for versioned nugets within a web of dependencies [C# Project]
Done!
monoman:~/Projects/NugetCracker$ mono NugetCracker/bin/Debug/NugetCracker.exe -c bumpversion -part:minor nu
NugetCracker 0.4
See https://github.com/monoman/NugetCracker


Using /home/rafael/Projects/active/NugetCracker/MetaProject.NugetCracker
Scanning '.' > '/home/rafael/Projects/active/NugetCracker'
.
Scanned 128 directories
Found 2 components
Sorting...
    Bumping component 'NugetCracker' version from 0.4 to 0.5
    Setting new version to 0.5
    Building NugetCracker.0.5
Done!
monoman:~/Projects/NugetCracker$ mono NugetCracker/bin/Debug/NugetCracker.exe -c list
NugetCracker 0.5
See https://github.com/monoman/NugetCracker


Using /home/rafael/Projects/active/NugetCracker/MetaProject.NugetCracker
Scanning '.' > '/home/rafael/Projects/active/NugetCracker'
.
Scanned 128 directories
Found 2 components
Sorting...
    Listing all components...
    [0001] Commons.Prevalence.1.0 - Minimal prevalence support for .NET [C# Nuget Project]
    [0002] NugetCracker.0.5 - A builder for versioned nugets within a web of dependencies [C# Project]
Done!

NugetCracker 0.3

Committed to Github version 0.3 of NugetCracker now with Help command, and some real parsing of project files:

Sample run:

NugetCracker 0.3
See https://github.com/monoman/NugetCracker

Using C:\Projects\xxx\MetaProject.NugetCracker
Scanning '.' > 'C:\Projects\xxx'
..........................
Scanned 6454 directories
Found 36 components
Sorting...
Ready > help
Available Commands:
    BumpVersion  Bumps up a version for a component
    Help         Show this list of commands or an specific command help
    List         List components, optionally filtered by regular expression
    Quit, Exit   Stops interactive mode
Ready >

MoonVorbis - monogatari

MoonVorbis - monogatari

Learning a bit more for doing the WebM on Moonlight project.

Thanks to the commenters that pointed me to this other project.

Update: It is Atsushi Enomoto, from Mono's team who is behind that blog and project. Nice to know...

Managed Commons including WebM subproject is at Github

Sorry, forgot to update here that the Managed Commons project now resides at Github: http://github.com/monoman/Managed-Commons

It includes the WebM subproject, that will allow reading/writing WebM files/streams generally and decode/play such streams in Moonlight.

Little time to work on it, so the progress is very slow, but if you want to contribute, please do: Fork it at Github and send those fantastic Pull Requests.

Also please post issues there to help guide/prioritize development, I'm trying to first be able to read the Matroska files, them I'll start the decoder and pump some video data, and last plug it into Moonlight. Writing streams/files has low priority at this point, unless someone really want to develop a video producing app, or a slideshow-to-video converter and want to contribute code and testing to that end.

We've upgraded to a Enterprise Licensed Monotouch

First thing to try (while waiting Apple bureaucracy to process our requests):

Build our prototype to the iPhone target... result: the binary of the program grows from 5MB to more than 7MB.

But I still think it is fairly sized for what it is carrying inside...

Developing for IPhone with MonoTouch

I'm developing my first app for the iPhone using Mono, MonoTouch and MonoDevelop in a Mac Mini. Never used seriously a Mac before, and last time I've developed something professionally for an Apple platform was for the Apple II, back in the 1970s (yes, I'm that old...).

Anyway, it is awesome to be able to leverage my skills with Mono and C#, instead of having to resort to Objective-C, to get the job done.

So far, I'm tackling the still steep learning curve over Cocoa, Interface Builder, and the limitations imposed over Mono by the AOT compiling the iPhone platform mandates.

My app has just a Login View, so far, that already interacts and validates against a hard-coded password, and Monodevelop generates an executable with some 4.7 Megabytes to be deployed to the iPhone Simulator.

When you think that all the Mono native runtime and huge parts of the basic class library already in native binary format is in there, I think it is a reasonable size, that won't grow much until I add loads and loads of functionality to the application.

I've been using the evaluation version of Monotouch so far, but I think it is proving itself worth the price, and my boss already said the investment on buying one or two (if we buy a second mac) enterprise licenses has a green.

Now I'm going to move more code from our J2ME version of the app to C#, while also trying to build an usable interface on top of it along the Apple guidelines.

Java support in Google's App Engine and Mono and Sneer

I've been reading and watching the videos from Google's Campfire One, about the new features they've added to App Engine, specially the Java support, and got thinking of some possibilities when throwing Mono in the picture:

1. We can see if they have interest in having Mono support in the App Engine, meaning basically to be able to host ASP.NET apps in there. That entails customizing the core libs/APIs using Mono as the VM and the libraries source, and also developing a plugin for Visual Studio (and maybe Monodevelop/Sharpdevelop) to give ASP.NET devs (WebForms and MVC) the same integrated experience they've provided for Java devs using Eclipse
2. We can help Keerthi's proposal to GSOC for implementing a clone of Azzure take off, and integrate it into Monodevelop, and perhaps Visual Studio. The advantage here being that we would have an open-sourced cloud implementation, that more people can host, even as an in-house solution.
3. We can retarget the Java in App Engine ideas from Computing in the Cloud, to Computing in the Crowd (Sovereign Computing),  it even keeps itself in the Java realm for the Sneer implementation of SC.
4. Sneer.NET could offer something akin to Azzure
5. We can drop all but the main concepts and have some Mono-based Cloud Implementation.

Well possibly some other permutations are also viable.

I've just thought to get the ball rolling on discussing those dreamable projects.

Boojay came to daylight

Nice screencast from my friend Rodrigo, the creator of boo and boojay.

Highly recommended. The most interesting part is that the pipelined design of the boo compiler allows this, to have it targeting different virtual machines and class libraries.

Niiiice...

New project DinDin

Starting a new open source (BSD license) project at google code: DinDin, which is a Brazilian Portuguese slang for money, as it is a distributed multi-platform home finance system based on Mono (WinForms+ASP.NET+Ajax) and maybe Moonlight.

Yes, I know, DinDin is also a childish slang for Dinner in English.

C# father Hejlsberg, talks about the language and cites Mono and Moonlight

I've read an Anders Hejlsberg's interview about C# history and future. It is scant on future details for C# 4.0, but nevertheless interesting.

A good thing in it, too, is that he cites favorably projects Mono and Moonlight on the middle pages.

:)

Commons.GetOptions the sucessor to Mono.GetOptions

I'll start Commons.GetOptions outside of Mono, and just keep Mono.GetOptions 1.0 stable (only security fixes) inside Mono svn. That would help with stability requirements for Mono colliding with the desire for innovation/improvements on GetOptions.

I'll post details as I progress with it. But some of the ideas I already have are:

1. to make it I18n-friendly (either gettext and resources, by defining/using localization providers and matching tools)
2. drop the multiple constructor overloads for the attributes, in favor of the supported syntax for field initialization by name
3. refactoring into a layered design, that should allow for imperative definition of option sets, besides the declarative form currently supported
4. subcommands support
5. easier runtime addition of options
6. a tool to compile a DSL (Domain Specific Language) to binary optionsets classes and/or generate (cia codedom) partial classes sources in any language that have correct codedom support installed.
7. a GTK# GUI tool (also wrapped as a MD plugin) to write the above DSL (some call it a graphical DSL)
8. A WinForms component/editor to define/generate/use the DSL
9. Full Monodoc/VSNET Documentation
10. Sample code also in Boo, VB.NET and Java(IKVM)

Nevertheless suggestions are welcome.

MS is getting some sense...

See the Novell/Microsoft cooperation/patent-protection agreements news, from Mono's perspective, of course:

http://tirania.org/blog/archive/2006/Nov-02.html

C#-scripting of Firefox, looks like something interesting

Vladimir Vukićević's post (Missing Pieces) opens up a nice prospect, of being able to script client-side with C#, and perhaps, Boo, and other CLR languages.

I think Mono fits the bill nicely on how to integrate with Firefox in Linux and elsewhere it is available, the same way it will be possible to do with the CLR in Windows Vista.

In truth, Mono's embedding API is a proven solution that, AFAIK, predates any MS disclosure of such a thing for .NET.

We just need to understand that this IE7-born integration, that is being "opened" to Firefox, isn't just some basic embedding API, but surely comes with a HUGE Object-Model attached of what is available in the browser to be scripted, and also some Security-Model which the central piece may be a list of running-time limitations and general assumptions.

Lots of fun, I foresee

ONDotnet.com: Miguel de Icaza Explains How to "Get" Mono

ONDotnet.com: Miguel de Icaza Explains How to "Get" Mono

And I couldn't resist answer some comments. I'm so easily tricked...