Posted By: jmacdonagh | Jun 11th, 2006 @ 8:20 PM
page 3 of 3
Comments: 53 | Views: 16314
footballism
footballism
Another Paradigm Shift!
    I think to some extent, the rebranding really confuses some of developers, you know .NET 2.0 and it's predecessors can run on Windows 2000, but .Net3.0 cannot. and for those who ain't follow the latest update on new technologies, it does take them a period of time  to figure out what .NET 3.0 really is.

Sheva
pacelvi
pacelvi
Phear
After reading the following , I'm really not seeing what people are complaing about in regards to having version conflicts, having to re-code, confusion etc..


http://msdn.microsoft.com/winfx/default.aspx?pull=/library/en-us/dnlong/html/netfx30.asp#netfx30_topic8

On Windows XP and Windows Server 2003, installing .NET Framework 3.0 also adds any .NET Framework 2.0 components that are not already installed. If .NET Framework 2.0 is already installed, the .NET Framework 3.0 installer adds only the files for Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace.

Components shared with .NET Framework 2.0 are installed in the following location:

%windir%\Microsoft.NET\Framework\V2.0.50727

Components that are new to .NET Framework 3.0 are installed in the following location:

%windir%\Microsoft.NET\Framework\V3.0 

All components of the .NET Framework 3.0 reference assemblies are installed in the following location:

%programfiles%\Reference Assemblies\Microsoft\Framework\v3.0

Uninstalling .NET Framework 3.0 will not remove the components shared with .NET Framework 2.0. To remove those components, you must first uninstall .NET Framework 3.0 and then separately uninstall .NET Framework 2.0. (You can uninstall the .NET Framework using the Add or Remove Programs item in the Windows Control Panel.)

pacelvi
pacelvi
Phear
vistawillship wrote:
STop this pointless speculation. What they decide on in Redmond is right, whether you agree or not. To think otherwise is just plain disloyalty.


Hmm how do I put this..

phuk off freak.
Q:  How many programmers does it take to change a lightbulb?

A:  None, its a hardware problem.



Q:  How many MS programmers does it take to change a lightbulb?

A:  None, MS just changes the standard to darkness.



So, what we have here is yet another case of chaning the standard to darkness.

page 3 of 3
Comments: 53 | Views: 16314
Microsoft Communities