Sos all my passwords in textedit app which will not open update#

People have been asking me to update the tutorial for VS.NET. However, the tutorial shows each step to take to build a very simple DCOM server and client. The tutorial isn't meant to reveal the underlying theory and gory detail of DCOM itself, just like the Scribble tutorial wasn't exactly meant to tour every nook and cranny of MFC. You may recall my step-by-step DCOM tutorial for VC6, which I posted at Not to toot my own horn.well, OK.to toot my own horn It's supposed to be hard, otherwise anybody could do it! New clients should use the IViewObject2 interface in this case and old clients would continue to use the IViewObject interface like nothing happened even if a server with the new IViewObject2 interface is distributed. Have a look in OLE/COM viewer and you will see interfaces such as IViewObject and IViewObject2. In that case you usually create a new version of the interface appending a number to the interface name and assign a new GUID for it in order not to break the contract between the server and its clients. Sometimes an original interface require modification.

A guideline would be to consider splitting an interface if it contains more than 20 functions.

The correct solution would be to create new interface(s) for the new functionality and also not to make the interfaces too complicated and large. The symptoms will vary depending on the interface changes. If this is the case, changing existing interfaces would break the 'contract' between the server and its client(s) and the client(s) will not function properly. These improvements could be new functionality through COM interfaces.

Sos all my passwords in textedit app which will not open software#

Most software that are 'kept alive' will usually need some kind of improvement. Otherwise you will end up having a situation where you have clients that are incompatible with their servers among your end users and they won't be very happy about that. You haven't provided enough information about your situation but I assume that the interfaces you are using are under construction and has not been completely specified yet and therefore, I hope, are distributed to a very small, controllable environment. On the other hand, one of the corner stones of COM is never to change a distributed interface. If you don't use the correct virtual table you will 'jump' to the wrong address when calling an interface function. The reason is that if there is an interface change the virtual table for the interface will change as well.

The short answer for this is simply 'No, you have to rebuild'. Msumit wrote:Is there any way to sort this out