Murat's Corner https://docs.microsoft.com/archive/blogs/murat/feed.xml Wed, 17 Apr 2019 03:23:28 GMT en-US hourly 1 Converting 32Bit COM+ Solution to 64Bit (VS2010) https://docs.microsoft.com/archive/blogs/murat/converting-32bit-com-solution-to-64bit-vs2010 Thu, 06 Jan 2011 13:54:24 GMT https://blogs.msdn.microsoft.com/murat/2011/01/06/converting-32bit-com-solution-to-64bit-vs2010/ Besides gazillions of things that can go wrong when converting a COM+ library written in C++ to 64Bit in Visual Studio 2010, the linker may start giving some weird "unresolved external symbol" errors for the autogenerated Proxy/Stub code.

The reason for that is, when you change the build target to Win64 for the solution, the MIDL thinks it's still generating code for the x86 platform. (yeah it's not a bug, it's a feature :))

But the workaround is easy:

Go to "Properties" screen of your COM+ application and change the "Target Environment" setting accordingly.

Edit: Just noticed this issue has been discussed here as well.

]]> Back online https://docs.microsoft.com/archive/blogs/murat/back-online Wed, 22 Dec 2010 13:02:03 GMT https://blogs.msdn.microsoft.com/murat/2010/12/22/back-online/ It's been a long time since I have last logged on to this blog site and have completely forgotten about it until today when I decided to clean my junk mail folder and saw lots of mails coming from readers marked as junk for some reason. So apologies to everyone to whom I havent replied back yet I'll try to go through feedbacks, questions and comments starting from tomorrow and update the blog.

Thanks to everyone who took the trouble of sending comments

]]> Exposing Com Events - C# https://docs.microsoft.com/archive/blogs/murat/exposing-com-events-c Thu, 20 Nov 2008 05:00:00 GMT https://blogs.msdn.microsoft.com/murat/2008/11/20/exposing-com-events-c/ With C#'s declerative programming ability it's relatively easy to expose the types to COM environment. But there are a few thing you must pay attention if you want to raise events from your managed COM component. I'll not go into the details of COM programming with C# but just focus on events for now.

Thanks to ComSourceInterfaces attribute; by using this attribute you can easily point to an interface which has the event declerations for your COM type. But before using that attribute you must have an interface to declare your type's events. (Keep in mind events are "dispatched", which means your interface that will contain the event declerations should implement IDispatch)

Here is a sample interface:

[ComVisible(true)] //Exposed

[InterfaceType(ComInterfaceType.InterfaceIsIDispatch)] //Our managed interface will be IDispatch

public interface IMathEvents {

    void OnOperationCompleted(string message);

}

And of course we need a class that will implement that interface and expose our event to COM. Here it is:

[ClassInterface(ClassInterfaceType.None)]

[ComSourceInterfaces(typeof(IMathEvents))]  //Our event source is IMathEvents interface

public class Math : ServicedComponent , IMath  /*IMath interface just declares a method named Add */

  {

  public int Add(int x, int y) {

    if (null != this.OnOperationCompleted)

    this.OnOperationCompleted("Operation completed");

    return x + y;

}

[ComVisible(false)]

public delegate void OperationCompletedDel(string message); //No need to expose this delegate

public event OperationCompletedDel OnOperationCompleted;

}

We need the ClassInterface attribute and we need to set it to None. If we dont do that we'll end up with a class and two different interfaces one of which has the method and the other one having the event. And for example if you need to access that class from VB you'll end up with two interfaces which may be confusing such as;

Private WithEvents ? obj as IMath <--- Cannot access events ??

Private WithEvents ? obj as IMathEvents <-- Cannot access the Add method ??

But obviously we need to be able to access both the event and members ;) thanks to ClassInterface attribute. So we can:

Private WithEvents obj as Math

 

 

]]> EnvDTE - Adding a reference to a project https://docs.microsoft.com/archive/blogs/murat/envdte-adding-a-reference-to-a-project Wed, 30 Jul 2008 10:35:00 GMT https://blogs.msdn.microsoft.com/murat/2008/07/30/envdte-adding-a-reference-to-a-project/ It was confusing to see a property named "Object" on EndDTE.Project class (which returns an object of type System.Object), especially when the tooltip didnt provide any useful information. (It's actual type is a ComObject) Anyway, actually it returns an object of type VSLangProj.VSProject (assuming you have a reference to VSLangProj). I was just trying to add a reference to my project within the VS Package I was working on and that class gives me the functionality I was looking for. Long story short, in order to add a reference (GAC) programmatically to your project here's what needs to be done:

private void AddReference(EnvDTE.Project proj) {

     VSLangProj.VSProject vsProject = (VSLangProj.VSProject)proj.Object;

     vsProject.References.Add("MyLibrary");

}

]]> Drag IT https://docs.microsoft.com/archive/blogs/murat/drag-it Mon, 15 Oct 2007 09:32:00 GMT https://blogs.msdn.microsoft.com/murat/2007/10/15/drag-it/ "I really would like to be able to move (drag) that custom control which I have just implemeneted on another custom control (say Panel )" said to myself this weekend... and started to implement MouseMove events... but it should not be that hard and actually it was not. If you just mess with Win32 a little bit, here is a quick solution for that. Here it is:

The idea is: just get the windows message (the message when you need to begin dragging your control) and tell Windows that the mouse is down on the caption (title) of the form (jut like you do when dragging the windows)

const int HTCAPTION = 0x2;

const int WM_NCLBUTTONDOWN = 0xA1;

[DllImportAttribute("user32.dll")]

public static extern int SendMessage(IntPtr hWnd, int Msg, int wParam, int lParam);

[DllImportAttribute("user32.dll")]

public static extern bool ReleaseCapture();

 

private void Control_MouseDown(object sender, MouseEventArgs e) {

    ReleaseCapture();

    SendMessage(this.Handle, WM_NCLBUTTONDOWN, HTCAPTION, 0);

}

]]> Office 2003 https://docs.microsoft.com/archive/blogs/murat/office-2003 Wed, 19 Sep 2007 08:56:00 GMT https://blogs.msdn.microsoft.com/murat/2007/09/19/office-2003/ Office 2003 - SP3 is available for download from (published 17/09/07)

https://www.microsoft.com/downloads/details.aspx?FamilyId=E25B7049-3E13-433B-B9D2-5E3C1132F206&displaylang=en

 And the details are here: https://support.microsoft.com/?kbid=923618

 

 

]]> Non Serialized Properties https://docs.microsoft.com/archive/blogs/murat/non-serialized-properties Mon, 17 Sep 2007 13:02:00 GMT https://blogs.msdn.microsoft.com/murat/2007/09/17/non-serialized-properties/ A fellow has asked me the easiest way of NOT serializing a property when using XML serialization...

You can not use the NonSerializable attribute for properties because this attribute is only valid for public fields, but there is another attribute in the System.Xml.Serialization namespace which is XmlIgnore.

This attribute will tell the xml serializer to ignore the property when serializing / deserializing. Such as:

 

[XmlIgnore()]

public string PropertyName {

    get { //code here }

    set { //code here }

}

]]> Office Web Components https://docs.microsoft.com/archive/blogs/murat/office-web-components Wed, 29 Aug 2007 13:38:00 GMT https://blogs.msdn.microsoft.com/murat/2007/08/29/office-web-components/ Was talking about charting components / libraries with a friend today. Just remembered that I have implemented one (a long time ago) with C#, which was nothing much but just a wrapper for OWC.

Well, it was OWC 2003  - I think I'm getting old :-) -

Here is the URL:

https://www.gotdotnet.com/Community/UserSamples/Details.aspx?SampleGuid=6dff5ce3-1c2f-42c8-90a5-cf0290b0cffc

 PS: Requires OWC 2003

]]> SMO https://docs.microsoft.com/archive/blogs/murat/smo Wed, 22 Aug 2007 18:08:00 GMT https://blogs.msdn.microsoft.com/murat/2007/08/22/smo/ SMO if a very powerful library, but if you do not have the correct version installed on your machine (like me) it may make you spend your valuable time looking for non-existing errors. The assembly Microsoft.SqlServer.BatchParser is machine (CPU) specific, which means if you have .NET Framework 64Bit (like I do) installed and trying to run your code with x86 version, it will fail :) Just make sure you have the correct version installed on your system...

]]> Delegate parameters https://docs.microsoft.com/archive/blogs/murat/delegate-parameters Tue, 21 Aug 2007 17:13:00 GMT https://blogs.msdn.microsoft.com/murat/2007/08/21/delegate-parameters/ Let's say you have two delegates at hand:

delegate void DummyDelegateWithInt(int x);

and

delegate void DummyDelegateWithObject(object x);

Everything seems OK right? But how about the performance issues? that question just crossed my mind. int is a value type where object is a reference type. I just implemented a very simple application that makes method calls through these delegates and passes the parameter 0 (int::zero). Of course these method calls are made more than once, 1,000,000,000 times... here is the result:

Method calls made through the first delegate takes 6.3 - 6.4 seconds (1,000,000,000 times), and the second one takes 32 - 33 seconds in average. Of course you may have a much faster CPU than I have, but it will not change the fact will it?

]]>