A .netish wish!
-
I wish there was one installer package containing all .net frameworks (from 1 to latest) for all windows Oss(32 bit x86, 64 and ia64) redistributable and free that automatically installs updates needed for the computer it runs on(Updates for available versions and installing new ones). In an advanced panel maybe it let's user selects which versions to install. Now I need a dreaming smiley here.
"In the end it's a little boy expressing himself." Yanni
... and it should download in 3.2 seconds. :-D
-
I wish there was one installer package containing all .net frameworks (from 1 to latest) for all windows Oss(32 bit x86, 64 and ia64) redistributable and free that automatically installs updates needed for the computer it runs on(Updates for available versions and installing new ones). In an advanced panel maybe it let's user selects which versions to install. Now I need a dreaming smiley here.
"In the end it's a little boy expressing himself." Yanni
But given that most .NET 1.0 apps should run with just 3.5 installed, why would you need that ?
Christian Graus Driven to the arms of OSX by Vista.
-
But given that most .NET 1.0 apps should run with just 3.5 installed, why would you need that ?
Christian Graus Driven to the arms of OSX by Vista.
I had a customer in another city. I sent him my .net software and link to Microsoft .net framework download page and asked him to download and install appropriate framework. A day later and just when I thought he is using the software successfully, he ranged that he has downloaded and installed a lot of versions and application doesn't run. I asked him to give me some information about his OS and machine and searched and sent him download links. Also when creating a software that's going to be released on CD it saves time if there was such a package available. Creating an installer would take far less time. Dealing with multiple versions and service packs takes time and is difficault for the end user. There are bootstrapper versions, SDKs, redistributables and service packs. These things make many clients confused.
"In the end it's a little boy expressing himself." Yanni
-
I had a customer in another city. I sent him my .net software and link to Microsoft .net framework download page and asked him to download and install appropriate framework. A day later and just when I thought he is using the software successfully, he ranged that he has downloaded and installed a lot of versions and application doesn't run. I asked him to give me some information about his OS and machine and searched and sent him download links. Also when creating a software that's going to be released on CD it saves time if there was such a package available. Creating an installer would take far less time. Dealing with multiple versions and service packs takes time and is difficault for the end user. There are bootstrapper versions, SDKs, redistributables and service packs. These things make many clients confused.
"In the end it's a little boy expressing himself." Yanni
-
... and it should download in 3.2 seconds. :-D
PIEBALDconsult wrote:
it should download in 3.2 seconds
No kidding. It should be 3.2 seconds for both the download AND install :)
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
It doesn't really matter that much because what Christian was saying is that if say you wrote an application targeting .NET 2.0 then all you'd have to ensure is that at least 2.0 is installed on your machine.
Unless something you're using becomes obsolete and is removed from the later versions?
-
It doesn't really matter that much because what Christian was saying is that if say you wrote an application targeting .NET 2.0 then all you'd have to ensure is that at least 2.0 is installed on your machine.
Ed.Poore wrote:
It doesn't really matter that much because what Christian was saying is that if say you wrote an application targeting .NET 2.0 then all you'd have to ensure is that at least 2.0 is installed on your machine.
Aha! I understand it. I know if we now start downloading .netfx 3.5 we have all old versions, but that looks like to be obvious only to programmers. If an installer sends user to .net download page, or a programmer asks user to download appropriate framework (Say I tell him 3.5) there are still users that don't understand it and search and find multiple versions. I wish there was one package being called say .netFrameWork that had latest version plus all previous and a permanent download link and was appropriate for all machines so users even don't think about it. Aside from that someone might really doesn't like to install 3.5 to get version 2.(size or installation time) So separate versions might help an installer to work more quickly on some machines.
"In the end it's a little boy expressing himself." Yanni
modified on Monday, December 8, 2008 3:40 PM
-
Unless something you're using becomes obsolete and is removed from the later versions?
-
Ed.Poore wrote:
It doesn't really matter that much because what Christian was saying is that if say you wrote an application targeting .NET 2.0 then all you'd have to ensure is that at least 2.0 is installed on your machine.
Aha! I understand it. I know if we now start downloading .netfx 3.5 we have all old versions, but that looks like to be obvious only to programmers. If an installer sends user to .net download page, or a programmer asks user to download appropriate framework (Say I tell him 3.5) there are still users that don't understand it and search and find multiple versions. I wish there was one package being called say .netFrameWork that had latest version plus all previous and a permanent download link and was appropriate for all machines so users even don't think about it. Aside from that someone might really doesn't like to install 3.5 to get version 2.(size or installation time) So separate versions might help an installer to work more quickly on some machines.
"In the end it's a little boy expressing himself." Yanni
modified on Monday, December 8, 2008 3:40 PM
Just tell them to install >{your required version}. There isn't a huge amount of different between the different frameworks (I think now that Microsoft have released the client version of 3.5 it has also dropped back down to <30MB). Also bearing in mind that all the recent version (2.0 -> 3.5) use the same core anyway, 3.5 is just a set of extensions sitting on top of .NET 2.0. The easiest way to accomplish this would be to bootstrap it, in which case if a version of the framework which you require isn't installed then it'll go off and either download it, or install it from a CD. ClickOnce deployment does this already, other systems such as MSI, WiX, NSIS can all provide identical features.
-
But given that most .NET 1.0 apps should run with just 3.5 installed, why would you need that ?
Christian Graus Driven to the arms of OSX by Vista.
Christian Graus wrote:
most .NET 1.0 apps should run with just 3.5 installed
By the way, I thought .net3.5 setup is ok for apps needing 2 and above. I didn't know it supports framework 1.0 as well. My lack of knowledge here. :-O
"In the end it's a little boy expressing himself." Yanni
-
Just tell them to install >{your required version}. There isn't a huge amount of different between the different frameworks (I think now that Microsoft have released the client version of 3.5 it has also dropped back down to <30MB). Also bearing in mind that all the recent version (2.0 -> 3.5) use the same core anyway, 3.5 is just a set of extensions sitting on top of .NET 2.0. The easiest way to accomplish this would be to bootstrap it, in which case if a version of the framework which you require isn't installed then it'll go off and either download it, or install it from a CD. ClickOnce deployment does this already, other systems such as MSI, WiX, NSIS can all provide identical features.
Ed.Poore wrote:
There isn't a huge amount of different between the different frameworks
True.
Ed.Poore wrote:
tell them to install >{your required version}
Might not work. The problem is that for a customer whose native language is not English, it's not easy to figure out what's the difference between a bootstap, a redistributable full download, an SDK etc. He will be confused. Giving them direct download link and not saying what it is helped more. :sigh:
Ed.Poore wrote:
The easiest way to accomplish this would be to bootstrap it, in which case if a version of the framework which you require isn't installed then it'll go off and either download it, or install it from a CD.
Thanks. I didn't know a bootstrap version can find and install missing files from CD. I have to look back at that in my NSIS docs. Thank you :) .
"In the end it's a little boy expressing himself." Yanni
-
Just tell them to install >{your required version}. There isn't a huge amount of different between the different frameworks (I think now that Microsoft have released the client version of 3.5 it has also dropped back down to <30MB). Also bearing in mind that all the recent version (2.0 -> 3.5) use the same core anyway, 3.5 is just a set of extensions sitting on top of .NET 2.0. The easiest way to accomplish this would be to bootstrap it, in which case if a version of the framework which you require isn't installed then it'll go off and either download it, or install it from a CD. ClickOnce deployment does this already, other systems such as MSI, WiX, NSIS can all provide identical features.
Ed.Poore wrote:
I think now that Microsoft have released the client version of 3.5 it has also dropped back down to <30MB
That's because the 3.0 and 3.5 packages only have new stuff and don't change anything from prior versions. :rolleyes: IF you don't have 2.0 and 3.0 installed you'll need them as part of 3.5. I'd hope the installer grabs them automatically for you, but never tested.
Today's lesson is brought to you by the word "niggardly". Remember kids, don't attribute to racism what can be explained by Scandinavian language roots. -- Robert Royall
-
PIEBALDconsult wrote:
it should download in 3.2 seconds
No kidding. It should be 3.2 seconds for both the download AND install :)
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
3 minutes is fine, as long as it tells you that is how long it will be. Any shorter and you don't have time to get coffee (or tea).
Silver member by constant and unflinching longevity.
RichardM1 wrote:
3 minutes is fine, as long as it tells you that is how long it will be
I agree. As long as it doesn't do one of those 1 seconds remaining kind of thing that seems to take 30 minutes to finish :rolleyes:
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
RichardM1 wrote:
3 minutes is fine, as long as it tells you that is how long it will be
I agree. As long as it doesn't do one of those 1 seconds remaining kind of thing that seems to take 30 minutes to finish :rolleyes:
"The clue train passed his station without stopping." - John Simmons / outlaw programmer "Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon "Not only do you continue to babble nonsense, you can't even correctly remember the nonsense you babbled just minutes ago." - Rob Graham
-
How come if the last 10% only takes 90% of the time, the last 1% takes 99%?
Silver member by constant and unflinching longevity.
most of what gets downloaded is crap, hence it behaves like crap
-
But given that most .NET 1.0 apps should run with just 3.5 installed, why would you need that ?
Christian Graus Driven to the arms of OSX by Vista.
Hooo, if only that were true! I've encountered libraries from a major manufacturer that *require* .Net 1.1 and won't run if .Net 2.0 is the only framework present. I don't know how they did it (or why come to that) but persuading customers that they must have both frameworks is sometimes a little tricky. And retrofitting 1.1 doesn't always work -- depends what sort of a mess the workstations are in... Just to ease matters, I'm not developing for 3.0 or 3.5 just yet -- waiting for the said manufacturer to catch up.
-
Ed.Poore wrote:
It doesn't really matter that much because what Christian was saying is that if say you wrote an application targeting .NET 2.0 then all you'd have to ensure is that at least 2.0 is installed on your machine.
Aha! I understand it. I know if we now start downloading .netfx 3.5 we have all old versions, but that looks like to be obvious only to programmers. If an installer sends user to .net download page, or a programmer asks user to download appropriate framework (Say I tell him 3.5) there are still users that don't understand it and search and find multiple versions. I wish there was one package being called say .netFrameWork that had latest version plus all previous and a permanent download link and was appropriate for all machines so users even don't think about it. Aside from that someone might really doesn't like to install 3.5 to get version 2.(size or installation time) So separate versions might help an installer to work more quickly on some machines.
"In the end it's a little boy expressing himself." Yanni
modified on Monday, December 8, 2008 3:40 PM
Hi! You can try sending them to http://www.microsoft.com/NET/[^]. Although I can't remember who said it or where I read it, there is a link on that page entitled "Install it now ->" that will download a setup file directly (no redirect to MS downloads or anything) that will always be the latest version of the .NET Framework. Does that help? I know it doesn't cover bootstrappers or CDs, but it's half the solution. Schmuli.
-
I wish there was one installer package containing all .net frameworks (from 1 to latest) for all windows Oss(32 bit x86, 64 and ia64) redistributable and free that automatically installs updates needed for the computer it runs on(Updates for available versions and installing new ones). In an advanced panel maybe it let's user selects which versions to install. Now I need a dreaming smiley here.
"In the end it's a little boy expressing himself." Yanni
Just thank God you don't have to deal with JAVA and all the mess is their version system, compatibility problems, etc. Even for JAVA developers the versions cause pain, specially because the backwards compatibility is not good.
-
... and it should download in 3.2 seconds. :-D
He-Who-Shall-Not-Be-Named can probably sell it to you.
Software Zen:
delete this;