The Microsoft .NET Framework version 1.1 includes ASP.NET Mobile Controls that enable developers to easily create mobile Web applications. Developers can write and maintain a single application that targets multiple devices. The Windows 2000 Authorization Manager Runtime is a Windows 2000 Server version of the Windows Server 2003 Authorization Manager role-based access control API. This download contains a setup that will correctly install the DirectX 9.0b documentation for use with the .NET Framework 1.1 and Visual Studio .NET 2003.
.NET Framework 1.1: Device Update 3.0; More Windows Downloads
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
It kind of annoys me that they don’t use libtool style version numbering. I believe v1.1 of .NET does in fact break backwards compatability with 1.0 in a few places, and their “solution” to this is to allow them both to be installed at once.<p>
Because they broke some interfaces as opposed to simply adding them, version 2 would have made more logical sense, not to mention being more useful.
Yes, they broke compatibility in many places, yet they documented the changes really well:
http://www.gotdotnet.com/team/changeinfo/
Please note that there are many (actually most) changes that did not involve changing public APIs, but may result in different app behaviour. So if you tried to recompile your app against the new CLR, in some cases it wouldn’t work even if it compiled fine.
The general rule for .NET is: you should run your application in environment it was designed and compiled against. If you want to run it in another environment, you can do it, but you should thoroughly test it and provide appropriate DLL mappings by hand. CLR provides very convenient ways for achieving this.
AFAIK .NET version 2 is a really big change, it’s supposed to include generics and new C# language features.
Do you see this as a bright alternative? windows zealots
Dextor:
I assume that by now you understand v1.1 is not api compatible with v1.0, right? You probably figured that out after reading the first right?
Is there a problem then? How does this have anything to do with Windows? At the very least you could have said Microsoft zealots. Either way, there is nothing zealot like about the previous posting.
Why don’t you complain about something non-trivial? I know, I know, that might force you to actually read and think, but hey, did you come here to vegatate?