The Microsoft .NET Framework is the core “runtime” and libraries for all Microsoft .NET applications. On Windows x64, the Microsoft .NET Framework v1.1 will run as a 32-bit application – not as a 64-bit application. In the next release of .NET, the installer will install a native x64 version of the .NET framework, along with a 32-bit version (yes, TWO identical .NET Frameworks – one x64 and one 32-bit). To understand why Microsoft is doing this, let me explain how .NET applications really “work”.
When a developer is finished writing his application, he uses a .NET enabled compiler to compile his code into a .NET assembly (usually into a .exe or a .dll file). A .NET Assembly does not contain any architectural “machine” code, it contains “MSIL” – Microsoft Intermediate Language. When you run a .NET assembly, the .NET “CLR” – Common Language Runtime reads the MSIL and converts it into code that your architecture can understand.
With this in mind, why doesn’t .NET 1.1 run assemblies as an 64-bit process on Windows x64? The quickest answer would be, .NET 1.1 simply does not have any type of x64 support. So why not make a patch, or release an update to .NET 1.1 to make it support running 64-bit assemblies?
The answer is compatibility. In .NET, a developer can still use COM controls and make Win32 calls in their assemblies. A 64-bit application can’t host 32-Bit COM controls, and if you ran an assembly in 64-bit mode – it would have a problem if it made a 32-bit specific call.
View: Extended64
When a developer is finished writing his application, he uses a .NET enabled compiler to compile his code into a .NET assembly (usually into a .exe or a .dll file). A .NET Assembly does not contain any architectural “machine” code, it contains “MSIL” – Microsoft Intermediate Language. When you run a .NET assembly, the .NET “CLR” – Common Language Runtime reads the MSIL and converts it into code that your architecture can understand.
With this in mind, why doesn’t .NET 1.1 run assemblies as an 64-bit process on Windows x64? The quickest answer would be, .NET 1.1 simply does not have any type of x64 support. So why not make a patch, or release an update to .NET 1.1 to make it support running 64-bit assemblies?
The answer is compatibility. In .NET, a developer can still use COM controls and make Win32 calls in their assemblies. A 64-bit application can’t host 32-Bit COM controls, and if you ran an assembly in 64-bit mode – it would have a problem if it made a 32-bit specific call.
View: Extended64
Making home networking easier is a key focus in Longhorn; among the aspects made simpler are setup, discovery of network resources, access and use of networked resources, diagnostics, roaming, etc. Considerable effort is going into making file sharing simple.
Our principal focus in Longhorn is to "make WIFI a great experience", both for users and for managers. We are investing a lot on a great diagnostic service, so that users can quickly understand and correct issues with wireless services. We are also investing a lot on a configuration and management. Finally, the extensibility of the stack paves the way for future innovation.
We are focusing on several major aspects: simplifying the interaction with the various configuration and setup UI aspects to make them much simpler to navigate; providing a more unified way of looking at different types of networks and managing them, making discovery and use of networked resources quick and simple, allow users as they move from work to home and public spots to easily roam without onerous intervention on changing settings, and making sure that end users can quickly discover problems, fix them and keep on using their network connections.
There is going to be a Network Explorer in Longhorn that will show the PCs and devices on your network. Users will be able to organize the PCs and users in different sorting order and will show PCs in the different workgroups and domains.
Personally I'm more of the opinion: Grr, the curse of COM controls hitting us again.
Yeah, like it's super nice to not have 64 bit support in .NET apps, or were you just sarcastic?
Last edited by 47883 on 23 Mar 2005 - 23:41
.NET 2.0 isn't released in a final form, but .NET 1.1 is already?
"just use the new framework"
.NET 2.0 is currently beta quality code and not aimed for use in production environments.
Microsoft basically say "use at your own risk". Windows x64 may go RTM before .NET 2.0 do.
There's your problem.
Commenting has either been disabled on this article or you are not logged in. Click here to login or register, its free!
Note: Anonymous commenting is disabled in order to keep the quality of responses to a high standard.