A .Net assembly uses a manifest to specify the contents of the assembly, be they code and/or resources. They also do not require registering with the Windows machine. A COM object publishes its contents via classid's or progid's to the Windows Registry. COM objects use Reference Counting to manage their memory, and will deterministically clean their memory resources when the reference count reaches zero. .Net assemblies are garbage collected, and their memory reclamation is non-deterministic (meaning, don't make any assumptions on when resources will be cleaned up.) COM objects can have different threading models. .Net objects can only have "Single Threaded Apartment" threading model (I think... you might want to look that up before you use it on your homework assignment).
COM can be accessed in .NET by using a reference Interop Assembly
.com=comershal .net=network
COM mean Component Object Model
.Net Framework bug
com- commercial org- organisation net- network
.NET is an abbreviation for "network," while .COM is an abbreviation for "commercial." Anyone can register a .NET or .COM, and there's no real difference between the two domain extensions.
Don't need to register a .NET assembly in the Windows registry like you have to with COM components. Also, DLL hell is gone. Programmer can install assemblies into GAC (Global Assembly Cache) or a central repository for assemblies otherwise in application local directories.
force is a push or pull. net force is the overall force on an object.
Net is short for network & com or comm is short for communication.
Org is non profits only. net is 2d to com and most only use it if com domain not available, info. if other 2 not avail, etc..
In domain names .com = commercial .net = network
Ideally, a URL ending in "com" indicates a commercial website whereas a URL ending in "net" meant that this site belonged to an organization involved in networking such as ISPs. In practice, people often chose a URL ending in .net when they couldn't get the one they wanted ending in .com.