Skip to main content

Nilas Jensen's Library tagged software_engineering →  View Popular

13 Nov 07

15 Seconds : Using Managed Components from Unmanaged Code

  • Standard COM implementation relies on the Windows registry for looking up the information related to COM components, like CLSID, Interface IDs, the path of the component's housing (DLL/exe), the component threading model, etc. .NET framework does not depend on the registry and uses metadata for this information. Therefore, we have to generate the COM-compatible registry entries for our managed server so that the COM runtime could instantiate our server.
    Like tlbimp.exe, there is a tool named regasm.exe. This tool reads the metadata information within an assembly and adds the corresponding COM-compatible registry entries. Classes in the assembly are not COM creatable until they are actually registered in the Windows registry.

Painless Software Schedules - Joel on Software

  • So, you have to make a schedule. This is something almost no programmer wants to do. In my experience, the vast majority just try to get away with not making a schedule at all. Of the few that make a schedule, most are only doing it because their boss made them do it, halfheartedly, and nobody actually believes the schedule except for upper management, which simultaneously believes that "no software project is ever on time" and in the existence of UFOs.


    So why doesn't anybody make a schedule? Two key reasons. One, it's a real pain. Two, nobody believes that it's worth anything. Why go to all the trouble working on a schedule if it's not going to be right? There is a perception that schedules are consistently wrong, and only get worse as time goes on, so why suffer for naught?

12 Apr 07

Calling a .NET Component from a COM Component

  • This code starts by defining an interface named iTemperature. Because the interface is defined with the Public keyword, it will be exported to the type library you'll create from this assembly. You can think of an interface definition as the skeleton for all or part of a class definition. The interface definition can contain members (properties, methods—either functions or subs—and events), just like a class. But unlike a class, an interface definition contains no code for any of these members. A class can implement one interface (as in this example) or more than one interface.

ClassInterfaceAttribute Class (System.Runtime.InteropServices)

  • Although class interfaces eliminate the task of explicitly defining interfaces for each class, their use in production applications is strongly discouraged.

Qualifying .NET Types for Interoperation

  • COM clients can still use the type if it is activated by some other means
  • For instance, parameterized constructors, static methods, and constant fields are not exposed to COM clients.
  • 1 more annotations...
01 Nov 06

Refactoring Home

  • information about refactoring, a disciplined technique for restructuring an existing body of code. There is a list of sources of information about refactoring, including various books that have been written. There is a catalog of common refactorings - yyensen on 2006-11-01
  • disciplined technique for restructuring an existing
    body of code
  • information about refactoring.
    There is a list of sources of information
    about refactoring, including various books that have been written. There
    is a catalog of common
    refactorings
17 Aug 06

Workspaces: Announcements




  • Workspace announcements


    Visual Studio 2005 Beta 2 workspaces Source Control Plug-in released (6/15/05)

    GotDotNet workspaces source control plug-in will now work with Visual Studio 2005 Beta 2. Kindly select the Visual Studio .NET Plug-in from the source control interface selection page and download the 2.0 msi from the WSSCCI Introduction page presented.

1 - 20 of 28 Next ›
Showing 20▼ items per page

Selected Tags

Related Tags

Sponsored Links

Ads by Google

Diigo is about better ways to research, share and collaborate on information. Learn more »

Join Diigo