Namespaces / Importing / References

Ankur_Verma · August 30th, 2006, 01:02 PM

Quote:

quote:With .NET---nothing is included (except private assemblies, and none of these would be included with the standard .NET framework--they would have to be downloaded or sent to me).

Taking AnkurLib.dll again. If you refer to it with âCopy Localâ property True, it will be copied to app directory of your application, which will make it a private assembly.

If you install AnkurLib.dll in GAC and refer to it with âCopy Localâ False it will not get copied to the app directory of you application, but will be loaded from the GAC, that makes it a shared assembly.

In either case you will have to have it sent to you or download it.

Quote:

quote:Things are referenced "just in time"?

Things are âloadedâ just in time. References to assemblies get added to the
application at design time. But implementation of classes like âConsultancyâ get
loaded just in time.

Regards
Ankur

Ankur_Verma · August 30th, 2006, 01:03 PM

Quote:

quote:Lastly, with old C++, when you "#include" you always included the header (.h) file in your exe -- it depended upon dynamic or static binding?---If that is true--I how would I know which was the case. In my classes, I only ever typed #include (using classes such as Cstring or iostream or whatever).

CString being an MFC class resided in one of the MFC DLLs which get referenced in
your MFC projects by default. You can state in the projects settings, however, whether you want to bind dynamically or statically. Neither of the cases usually have any bearing on #include statement as it only adds class declaration info to the application and not the implementation. Implementation comes from the DLLs.

Regards
Ankur