Typed vs Strongly Typed in C#
.net, c#
Solution
Your nomenclature is incorrect. it is not `strongly typed vs just typed`
It's `strong vs. weak typing`
Once you talk about it in those terms, then there is a big distinction to be made.
You can read about it all over teh Googles.
http://en.wikipedia.org/wiki/Strong_and_weak_typing#Definitions_of_.22strong.22_or_.22weak.22
Edit:
There is no such thing as just a Typed language. You have Dynamic vs Static and Weak vs Strong typing which are addressing two different types of issues. Another reference article
What is the difference between a strongly typed language and a statically typed language?
Problem
In C#, is there any reason to say strongly typed vs just typed? When someone says typed class, I think of some type other than object. Nearly everything except object is typed in C#. Once you define a class that is not object, that class is a type. It doesn't get anymore typed from there. By the way, this isn't a question about type safety (valid memory access and object assignment compatibility).