The Platform Adaption Layer allows SSCLI (Rotor) to run on Unix. I worked on FreeBSD. IIRC, that SSCLI distribution is actually kinda old and isn't the source that made up VS 2008 (though the changes to the BCL were minimal between 2005 and 2008)
freedb/cddb finger printing is based on the length and order of the tracks. If you were to burn k tracks of silence with the right length and in the correct order you can get freedb or cddb to say "yup, you've got the right cd!"
The OP got it right here and you are in the wrong. If you look at the assemblies that are in %WINDIR%\Microsoft.NET\Framework\v2.0.50727 (which is the RTM version of the 2.0 Framework) you'll find 28 files.
For example, this list includes System.Windows.Forms.dll (WinForms) which is the GUI component of the.NET Framework. You aren't comparing apples to apples here. You might have better luck comparing just mscorlib.dll and System.dll to the POSIX standard, but I still think it wouldn't be fair (There are collections in both mscorlib.dll and System.dll and I don't think that's something that POSIX defines, but I could be wrong here).
The Platform Adaption Layer allows SSCLI (Rotor) to run on Unix. I worked on FreeBSD. IIRC, that SSCLI distribution is actually kinda old and isn't the source that made up VS 2008 (though the changes to the BCL were minimal between 2005 and 2008)
freedb/cddb finger printing is based on the length and order of the tracks. If you were to burn k tracks of silence with the right length and in the correct order you can get freedb or cddb to say "yup, you've got the right cd!"
Except that CDBaby also charges the buyer shipping on top of whatever the artist sets the CD Price at.
The OP got it right here and you are in the wrong. If you look at the assemblies that are in %WINDIR%\Microsoft.NET\Framework\v2.0.50727 (which is the RTM version of the 2.0 Framework) you'll find 28 files.
/B System*.dll
.NET Framework. You aren't comparing apples to apples here. You might have better luck comparing just mscorlib.dll and System.dll to the POSIX standard, but I still think it wouldn't be fair (There are collections in both mscorlib.dll and System.dll and I don't think that's something that POSIX defines, but I could be wrong here).
C:\Windows\Microsoft.NET\Framework\v2.0.50727>dir
System.configuration.dll
System.Configuration.Install.dll
System.Data.dll
System.Data.OracleClient.dll
System.Data.SqlXml.dll
System.Deployment.dll
System.Design.dll
System.DirectoryServices.dll
System.DirectoryServices.Protocols.dll
System.dll
System.Drawing.Design.dll
System.Drawing.dll
System.EnterpriseServices.dll
System.EnterpriseServices.Thunk.dll
System.EnterpriseServices.Wrapper.dll
System.Management.dll
System.Messaging.dll
System.Runtime.Remoting.dll
System.Runtime.Serialization.Formatters.Soap.dll
System.Security.dll
System.ServiceProcess.dll
System.Transactions.dll
System.Web.dll
System.Web.Mobile.dll
System.Web.RegularExpressions.dll
System.Web.Services.dll
System.Windows.Forms.dll
System.XML.dll
For example, this list includes System.Windows.Forms.dll (WinForms) which is the GUI component of the
FWIW, The Windows SDK and .NET SDK's (both of which are free to download) contain compilers.
At Microsoft, Program Managers are not "Managers" in the traditional sense. Instead these people spec out the different features a product will have.
In Microspeak they are individual contributors and not managment, they don't have reports.
Having a strong team of program managers is a good thing for a developer. You get to spend more time focusing on the techncial implementation.
Best. Games. Ever.
But who will watch those watchers? And who will watch them?
I dunno. Coast Guard?