Install program wants ANOTHER .NET Framework!

[terrypin]

Oh no! last night I decided to bite the bullet and install the vast Microsoft .NET Framework 2.0 which is unfortunately needed for Chris's simple (FREE) VOB2MPG program. Took me ages, but by the early hours I had it working and went to bed.

This morning I decided as an act of faith to pay up 20 UKP (36 USD) for SVCD2DVD. I'd read good reviews and I knew it used .NET Framework, so I judged that would capitalise a bit more on the effort I'd just made. So I duly registered and downloaded. But on starting the install I get this message:

"This setup requires the .NET Framework version 1.1.4322. Please install the .NET Framework and run this setup again."

Must I really install another, OLDER version of this beast? Why would the free program use a newer version? I've no idea how much HD space version Framwork 2.0 has taken, but it was one heck of a lot, plus hundreds of new registry entries. So naturally I'm reluctant to proceed. But having paid up... I've never ever before dived staright in without a trial; obviously picked the wrong choice to break that habit.

--
Terry, West Sussex, UK

[ChrissyBoy]

The reasons are as follows.... SVCD2DVD was first written when the .Net framework was at release 1.1. There are too many lines of code and a high level of complexity that a port to .Net 2.0 is not realistic at this time. All new software applications that I write (e.g. VOB2MPG) are written for v2.0 of the .Net framework.

So in short you need:

.Net 2.0 for VOB2MPG
.Net 1.1 SP1 for SVCD2DVD

If you have concerns and want me to refund your registration - just let me know.

[Bjs]

You will need to uninstall all net framework version's first .

Install version 1.1.4322 then install svcd2dvd reboot pc
Install version 2 , then install vob2mpg

It's a pain when developer's dont bother to update their product's source to take into account of later release's of the net package , it cause's plenty of headache's for newbies and alike ...

I prefer to avoid any developer which use's netframe work , as it open's more hole's in the os ... there are plenty of other way's to convert a vob to mpeg without net framework .

[mats.hogberg]

Seriously, the .net framework is (and will be even more) the platform on which Windows applications (of any form) are built. It will be an integral part of the OS, and I don't doubt parts of the OS (or the OS bundle MS calls OS)itself will be built on the .net platform.
But Chrissy - If you have 1.1 code running and compiling fine on 1.1 - Isn't it just a matter of recompiling it against 2.0? I thought the newer versions are backwards compatible? At least, that's how we do it (web applications) and haven't found any drawbacks (yet?).

/Mats

/Mats

[ChrissyBoy]

Mats: I have compiled it against 2.0 - no problem there, but there are many threading issues with callbacks & delegates which means it just won't run properly without rewriting some major parts. I believe my efforts are best spent on developing a new tool from the ground up.

Your other point is spot on.

All my tools use .Net: if someone doesn't want to install .Net then don't use my tools. All .Net requirements are clearly pointed out on the website.

[MaxBlack]

@Terry (the OP)

I am not a programmer and don't understand this .NET stuff but apparently you do need to have both 1.1 and 2.0 on your PC at the same time, i.e. that "upgrading" to .NET 2.0 does not (as you might expect) mean that 1.1 goes away in favor of 2.0.

In any case I have done this, have both installed, and the various programs that require one version or t'other all work, thankfully...

[terrypin]

OK, thanks Chris, appreciate the prompt response.

Went ahead and installed 1.1, which was very much faster than 2.0. SVCD2DVD now installed and working, although I have yet to put it properly through its paces.

Hopefully, in the months ahead, a few other desirable programs will make use of this 2.0 monster, and justify its existence.

Couple of minor points while they're fresh in my mind:
- I like your demo movies, thanks, they'll be helpful. But in Firefox the controls (Forward, Exit, etc) didn't work. (OK in IE6.)

- On my first test, found that pasting a path/filename into the source and destination boxes doesn't work, either with r-click or ctrl+v.

--
Terry, West Sussex, UK

[mats.hogberg]

I hear you Crissy - when it comes to desktop apps, you're the expert! My experience is mostly in the web development area.

/Mats

[ChrissyBoy]

Couple of minor points while they're fresh in my mind:
- I like your demo movies, thanks, they'll be helpful. But in Firefox the controls (Forward, Exit, etc) didn't work. (OK in IE6.)

Thanks for the headsup - i will take a look.

- On my first test, found that pasting a path/filename into the source and destination boxes doesn't work, either with r-click or ctrl+v.

I take it this is in VOB2MPG? If so this is by design: to avoid typos

[terrypin]

You will need to uninstall all net framework version's first .

Install version 1.1.4322 then install svcd2dvd reboot pc
Install version 2 , then install vob2mpg

It's a pain when developer's dont bother to update their product's source to take into account of later release's of the net package , it cause's plenty of headache's for newbies and alike ...

I prefer to avoid any developer which use's netframe work , as it open's more hole's in the os ... there are plenty of other way's to convert a vob to mpeg without net framework .

I seem to have succeeded the other way around. Having uninstalled 1.1 I installed 2.0, then VOB2MPG, then 1.1, then SVCD2DVD.

Could you expand on your last point about alternatives please. What is your preference?

I tried one other method, simply renaming all VOB files as MPG. I can't be 100% sure that was the cause, but on importing those and working on them in Movie Maker 2.0, I had frequent crashes. I have yet to repeat the work with the VOB2MPG output.

--
Terry, West Sussex, UK

[ChrissyBoy]

I hear you Crissy - when it comes to desktop apps, you're the expert! My experience is mostly in the web development area.

/Mats

Alot has changed in the GUI threading department: Some nice new stuff like the BackgroundWorker class (which does what took me reams of code in 1.1 in about 5 lines!) but some of the more delicate stuff to do with updating controls created in one thread from another no longer works the way i did it in 1.1. As there is a lot of this: log files, progress, log windows etc.... there is a lot to rewrite. Instead i think I'll focus on something new.

[terrypin]

Thanks MaxBlack. Happily I seem to have both working too. I'll just have to try to forget all that complex stuff lurkin around!

One key point I meant to add earlier is that I have XP Home SP1, not SP2. I'm a bit nervous, as at the download page
http://www.microsoft.com/downloads/details.aspx?familyid=0856EACB-4362-4B0D-8EDD-AAB15...n#Requirements
it says
Supported Operating Systems: Windows 2000 Service Pack 3; Windows 98; Windows 98 Second Edition; Windows ME; Windows Server 2003; Windows XP Service Pack 2

--
Terry, West Sussex, UK

[terrypin]

I take it this is in VOB2MPG? If so this is by design: to avoid typos

Yes, VOB2MPG - sorry to change topics mid-post. Please re-consider then, as my copies of path/filenames are guaranteed typo-free! They're made with Send To|Clipboard As Name
Far quicker than browsing through deeply-nested folders from the top down.

(Meanwhile, I'd suggest greying out Paste.)

--
Terry, West Sussex, UK

[MaxBlack]

I'm a bit nervous, as at the download page it says
Supported Operating Systems: ...Windows XP Service Pack 2

I was "born nervous" and can feel your pain. However, I think this statement is more a reflection of MS' desire to get everyone onto SP2 than a true "won't work unless".

But then, some days I have more guts than brains!