Prev: OleDbCommandBuilder - Data type mismatch in criteria expression
Next: Check .NET Framework exists from managed assembly
From: Michael Nemtsev [MVP] on 27 Nov 2007 15:48 Hello Paul, There is no reason to remove the previous version of .NET FW, because there could be an app which is binded to the specific version of FW. But you can try to remove, and everything may be ok. --- WBR, Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour "The greatest danger for most of us is not that our aim is too high and we miss it, but that it is too low and we reach it" (c) Michelangelo PH> I have several old versions of the .NET Framework on my machine, and PH> I am wondering if I can remove them. I have version 1.1 (and a 1.1 PH> hotfix), 2.0, 3.0 and now, new with Visual Studio 2008, 3.5. PH> PH> How many versions of the framework do I *really* need to carry? Can PH> I dump all but 3.5, or will that break other things? I am not doing PH> any legacy projects based on older versions. PH> PH> Paul PH> ---- PH> Paul Hurley PH> Caliban Computing PH> http://www.Caliban.com/ PH> Spam resistant return email address.
From: PvdG42 on 27 Nov 2007 23:31 "Paul J. Hurley" <hurleyp(a)NoSpam.caliban.com> wrote in message news:bovok3d2ca0i5erkj2ig1570tnfqvarjko(a)4ax.com... >I have several old versions of the .NET Framework on my machine, and I am > wondering if I can remove them. I have version 1.1 (and a 1.1 hotfix), > 2.0, 3.0 and now, new with Visual Studio 2008, 3.5. > > How many versions of the framework do I *really* need to carry? Can I > dump > all but 3.5, or will that break other things? I am not doing any legacy > projects based on older versions. > > Paul > ---- > Paul Hurley > Caliban Computing > http://www.Caliban.com/ > Spam resistant return email address. You may want to consider that VS 2008 is capable of targeting .NET 2.0 (SP1), 3.0 or 3.5, So keeping those makes sense. As for 1.1, whether you really need it will be determined by whether or not you have any ,NET software that requires 1.1 installed.
From: Cowboy (Gregory A. Beamer) on 28 Nov 2007 13:51 You have to keep 2.0, 3.0 and 3.5, as the last two are just additions to 2.0. You can uninstall 1.0 and 1.1 as long as you do not have any products installed that use them. If you leave them on your drive, nothing will happen, except you will have less space on the drive for other things. -- Gregory A. Beamer MVP, MCP: +I, SE, SD, DBA ************************************************* | Think outside the box! | ************************************************* "Paul J. Hurley" <hurleyp(a)NoSpam.caliban.com> wrote in message news:bovok3d2ca0i5erkj2ig1570tnfqvarjko(a)4ax.com... >I have several old versions of the .NET Framework on my machine, and I am > wondering if I can remove them. I have version 1.1 (and a 1.1 hotfix), > 2.0, 3.0 and now, new with Visual Studio 2008, 3.5. > > How many versions of the framework do I *really* need to carry? Can I > dump > all but 3.5, or will that break other things? I am not doing any legacy > projects based on older versions. > > Paul > ---- > Paul Hurley > Caliban Computing > http://www.Caliban.com/ > Spam resistant return email address.
From: Cowboy (Gregory A. Beamer) on 28 Nov 2007 13:52 "PvdG42" <pvdg(a)toadstool.edu> wrote in message news:emohheXMIHA.1184(a)TK2MSFTNGP04.phx.gbl... > > You may want to consider that VS 2008 is capable of targeting .NET 2.0 > (SP1), 3.0 or 3.5, So keeping those makes sense. As for 1.1, whether you > really need it will be determined by whether or not you have any ,NET > software that requires 1.1 installed. That is because 3.0 and 3.5 are just extras added on top of 2.0 and not really new Frameworks. :-) -- Gregory A. Beamer MVP, MCP: +I, SE, SD, DBA ************************************************* | Think outside the box! | *************************************************
From: larrylou on 19 Dec 2007 14:40
"Michael Nemtsev [MVP]" wrote: > Hello Paul, > > There is no reason to remove the previous version of .NET FW, because there > could be an app which is binded to the specific version of FW. > > But you can try to remove, and everything may be ok. > > --- > WBR, > Michael Nemtsev [.NET/C# MVP] :: blog: http://spaces.live.com/laflour > > "The greatest danger for most of us is not that our aim is too high and we > miss it, but that it is too low and we reach it" (c) Michelangelo > > > PH> I have several old versions of the .NET Framework on my machine, and > PH> I am wondering if I can remove them. I have version 1.1 (and a 1.1 > PH> hotfix), 2.0, 3.0 and now, new with Visual Studio 2008, 3.5. > PH> > PH> How many versions of the framework do I *really* need to carry? Can > PH> I dump all but 3.5, or will that break other things? I am not doing > PH> any legacy projects based on older versions. > PH> > PH> Paul > PH> ---- > PH> Paul Hurley > PH> Caliban Computing > PH> http://www.Caliban.com/ > PH> Spam resistant return email address. > > > |