Feeds

Official: Microsoft's C# is Cool

Parse this, Sun

  • alert
  • submit to reddit

The essential guide to IT transformation

When Microsoft rolled out its new programming language, C#, in June, a team of spin-paramedics was on hand to point out that no way, never ever was this anything to do with Microsoft's allegedly mythological "Project Cool".

However, we spotted in the documentation for C# an extended attribute created by language spec co-author Scott Wiltamuth that read 'Owner=scottwil Team=VC Feature=Cool'.

By your extended-attribute-tags shall ye know them, we thought, although we couldn't quite rule out the possibility that the witty language authors had inserted the reference as a tease. We even tried to out these fine folk with the naked enducement of a Register label badge, but the buggers wouldn't bite.

But it's all over now. Thanks to eagle-eyed Register reader Larry Smith, we've learned that C# is indeed Cool. Or if it isn't, it's chocca with references to it.

Take for example the C# file samples\quickstart\aspplus\samples\webforms\intro\acme.cs which contains the giveaway comment: "//TodoHack 'needed because COOL doesn't support array initializers yet'."

Then Larry discovered that the original C# compiler was called coolc (duh...) subsequently renamed as csc.exec. Elsewhere, sample C# code has the HTML tag <script language='COOL' runat='server'>, and Larry notes a couple of references to the string "C\temp\fact\factorial.cool"

Burrowing deeper into the libraries we find "CoolCodeStream" in VisualStudio.dll and "DataSetCSharp". "DataSetCool" and "Microsoft.VisualStudio.Data.CodGen.DataCacheCool.xsl".

Make files also have references to "compiling cool samples" - which Larry reckons isn't quite the smoking pistole, but nonetheless, we reckon, are too coincidental to be ignored. Had enough? Wait a minute - we haven't mentioned the preprocessor declarations such as COOL_EXE_FLAGS (hmm...)

It kinda reminds us of the beta trial of Windows NT 3.1 (nee OS/2 version 3.0) when Microsoft denied that WinNT had anything to do with its hated IBM counterpart... and that it was sheer coincidence that NT spewed a ton of identical OS/2 error messages (down to the number) as OS/2 did, in identical circumstances.

It's dirty work, but somebody has to point out Microsoft's unceasing innovation. And so it falls to us... ®

Related Story

Microsoft describes its Java killer

The essential guide to IT transformation

More from The Register

next story
BBC: We're going to slip CODING into kids' TV
Pureed-carrot-in-ice cream C++ surprise
China: You, Microsoft. Office-Windows 'compatibility'. You have 20 days to explain
Told to cough up more details as antitrust probe goes deeper
Linux turns 23 and Linus Torvalds celebrates as only he can
No, not with swearing, but by controlling the release cycle
Scratched PC-dispatch patch patched, hatched in batch rematch
Windows security update fixed after triggering blue screens (and screams) of death
This is how I set about making a fortune with my own startup
Would you leave your well-paid job to chase your dream?
prev story

Whitepapers

Endpoint data privacy in the cloud is easier than you think
Innovations in encryption and storage resolve issues of data privacy and key requirements for companies to look for in a solution.
Implementing global e-invoicing with guaranteed legal certainty
Explaining the role local tax compliance plays in successful supply chain management and e-business and how leading global brands are addressing this.
Advanced data protection for your virtualized environments
Find a natural fit for optimizing protection for the often resource-constrained data protection process found in virtual environments.
Boost IT visibility and business value
How building a great service catalog relieves pressure points and demonstrates the value of IT service management.
Next gen security for virtualised datacentres
Legacy security solutions are inefficient due to the architectural differences between physical and virtual environments.