.NET 2.0 for x264 daily builds.

[Sharktooth]

Im thinking to distribute the included MeGUI and AVC2AVI GUI as .NET 2.0 binaries.
That will require you to download the .NET 2.0 framework from Windows Update or MS Dowload Center (or any other mirror hosting it) but will enable support for full visual styles (including buttons, listbox etc.).
What do you think?

EDIT: I forgot to say you can have both .NET 2.0 and .NET 1.1 without any compatibility problems.

[DarkZell666]

Might as well start upgrading, 'coz anyway once .NET 2.0 framework is installed old 1.1 applications will still run (long live backwards compatilibity, even if we're talking about M$ here, hehe), so I doubt upgrading to 2.0 would be a bad move ;)

just go for it =)

[dimzon]

A small offtop - I really don't understand why does you distribute stripped to x264 only MeGUI version? Just to save approx 100kb per download? Maybe You will create MeGUI-x264 vs MeGUI poll?

[Sharktooth]

@dimzon: I do it coz i want to distribute a full working package and including full MeGUI means i should include all the other stuff.
I already have intentions to change the name of the x264-full to x264-std and create a new full package with full MeGUI including OpenSource stuff like faac, dgindex, avisynth etc. but it will be BIG.

[Revgen]

I could care less what version you use, just as long as MeGUI works fine.

[Sharktooth]

It works. I already use .NET 2.0 compiled binaries and there are no drawbacks.

[acidsex]

I, for one, am looking forward to the visual styles. :) I say go for it.

[buzzqw]

i have already installed net 1.1 and 2... but why using .net 2 if ALL option is fuctional under .net 1?

Better performance/layout/more possibility for this front-end... ?

thanks

BHH

[Sharktooth]

.NET 2.0 has definatly more functionality than 1.1 and will be compatible with Vista.

[buzzqw]

gotcha !

go for .net 2 !

BHH

[Sharktooth]

It depends on MeGUI development though.

[FFWD]

and create a new full package with full MeGUI including OpenSource stuff like faac, dgindex, avisynth etc. but it will be BIG.Sweet! Everybody has broadband nowadays..

[DeathTheSheep]

Everybody has broadband nowadays.
Actually, I only have 3mbps dsl ;)
I see no reason not to upgrade to .NET 2.0: The 2.0 package is easily downloadable, has no compatibility problems (actually helps it, i.e. Vista), and actually boosts functionality a teensy bit.

edit: In the rapidly evolving and developing codec world, sicking with the old stuff is kinda pointless anyway. People who download x264 in the first place are embracing modernity--they could have settled for the more well-known XviD--so it only makes sense for .NET to be kicked up a notch, just like x264 keeps doing.

[Sharktooth]

The new build is still based on .NET 1.1. However seems im going to compile the next revisions with .NET 2.0...

[Sirber]

@dimzon: I do it coz i want to distribute a full working package and including full MeGUI means i should include all the other stuff.
I already have intentions to change the name of the x264-full to x264-std and create a new full package with full MeGUI including OpenSource stuff like faac, dgindex, avisynth etc. but it will be BIG.That would be cool. I'm sure most user don't like to have to find all the needed stuff :)

[Sharktooth]

67 vs 10...
2006 versions of x264 daily builds will have MeGUI for .NET 2.0 :)

[Sharktooth]

get ready for the jump. next x264 full package will require .net 2.0.

[Sirber]

Get RealAnime then! No need of .NET ;)

[Romario]

I vote for Net 2.0, it's logical step forward.

[Doom9]

At this point the poll can be closed.. the switch has already been made, the current source code can only be built against .NET 2.0 and there will be more 2.0 only features by my next CSV commit, making it quite an exhausting exercise in code rewriting to ever go back.. and we haven't even started with generics and the likes.