![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | Differences between "Framework" and "Library" What are some of the important differentiating characteristics between frameworks and a libraries? Is it mostly that a library is simply a bunch of code that one can call into; whereas a framework can additionally call into my code (perhaps, for example, via delegates)? What else differentiates frameworks from libraries? Thanks. |
My System Specs![]() |
| | #2 (permalink) |
| | Re: Differences between "Framework" and "Library" A framework is a collection of libraries and represents the context of what the libraries were created to be used for implementation. "Jordan S." <A@xxxxxx> wrote in message news:O6pNULEPJHA.4780@xxxxxx Quote: > What are some of the important differentiating characteristics between > frameworks and a libraries? > > Is it mostly that a library is simply a bunch of code that one can call > into; whereas a framework can additionally call into my code (perhaps, for > example, via delegates)? What else differentiates frameworks from > libraries? > > Thanks. > > |
My System Specs![]() |
| | #3 (permalink) |
| | Re: Differences between "Framework" and "Library" Hello Jordan, A library constists of code, be it in the form of standalone functions (primarily in native code implementation), classes (System.IO.StreamReader for one) or both which exists for use in other applications, such as yours. A framework is a set of libraries and Microsoft .NET Framework is just an example: it contains the 'root' mscorlib.dll (which defines the CLR and by default is included in all .NET-related projects) and additional library sets such as Windows Forms, Web Forms, Linq et cetera. A framework is installed but your application does not necessary use all of the libraries included. You can also create a framework by writing and separating code in appropriate libraries, all of which form a whole 'one.' Think of libraries and frameworks for coding as instruments and kits for music production, although I am sure there is a better comparison. ![]() -- Stanimir Stoyanov http://stoyanoff.info "Jordan S." <A@xxxxxx> wrote in message news:O6pNULEPJHA.4780@xxxxxx Quote: > What are some of the important differentiating characteristics between > frameworks and a libraries? > > Is it mostly that a library is simply a bunch of code that one can call > into; whereas a framework can additionally call into my code (perhaps, for > example, via delegates)? What else differentiates frameworks from > libraries? > > Thanks. > > |
My System Specs![]() |
| | #4 (permalink) |
| | Re: Differences between "Framework" and "Library" Jordan S. wrote: Quote: > What are some of the important differentiating characteristics between > frameworks and a libraries? > > Is it mostly that a library is simply a bunch of code that one can call > into; whereas a framework can additionally call into my code (perhaps, for > example, via delegates)? What else differentiates frameworks from libraries? used interchangeable. Two characteristics that will make a library likely to be called a framework are: * it comes with guidance regarding how it should be used * it calls your code instead of your code calling it Arne |
My System Specs![]() |
| | #5 (permalink) |
| | Re: Differences between "Framework" and "Library" You can also define your own library (the framework allows you to do this) with so-called "extension methods". IntelliSense is the Framework, and it works with the library. But I'm really bad with CSci lingo so don't take my word for it. RL Jordan S. wrote: Quote: > What are some of the important differentiating characteristics between > frameworks and a libraries? > > Is it mostly that a library is simply a bunch of code that one can call > into; whereas a framework can additionally call into my code (perhaps, for > example, via delegates)? What else differentiates frameworks from libraries? > > Thanks. |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Unwanted Multiple contacts in "To","CC","BCC" of email send catago | Vista mail | |||
| Vista not wotking with "My Computer" or "Control Panel", "Screen Saver" | Vista General | |||
| How can I add the icons "Delete", "Cut", "Copy" and "Paste" in Vis | Vista file management | |||
| WM5 Sync with Vista "Windows Calender", "Contacts", and "Mail" | Vista General | |||
| interesting "issue" or "bug" with psobjects when calling DOTNET framework stuff | PowerShell | |||