Thanks for the reply and the greeting. I'm sorry I should have been more clear. I have a larger application that will use this dll. It needs to be a Com DLL so that the class can be seen by the users of our application. They will sometimes do direct com calls (in this case it will be rare). It will also be called directly from our application when an event takes place. Our main code is written in C' and in the past I created smart pointers to hit against a non registered C++ dll functions. This C++ dll established a pointer to the class for a registered VB com dll and would call the appropriate member and return the result to the main application for use in further processing. I have it where the class is seen because I have it working in VB. However I just learned C# and would prefer to do it in this language since it will help me in the future. Eventually our application will be rewritten in .Net and I want to learn and do as much as I can before we get to that point.
By the way I know with using Smart pointers I am doing it the long way and I am sure their is a quicker way but with the smart pointers it's easier for me to see and follow the process I hope that better explains why I need to turn a very simple process into a dll that in turn needs to be registered. Thanks Josh On Sep 2, 4:23 am, Cerebrus <[EMAIL PROTECTED]> wrote: > Hi Josh, > > Welcome to the Group ! I hope you find your time here fruitful. > > It appears that you are indeed missing something - conceptual > knowledge! ;-) A DLL is a class library that is not specific to COM. > Dotnet class libraries are also built as .dll's. Therefore, I do not > see any reason for you to Register your DLL for COM interop, unless > there is some information that you haven't told us. > > I think that what you really want to do is to create a Custom Control, > not a COM library. If we can agree on that basic premise then we can > better guide you on how to create that type of control. > > On Sep 2, 5:47 am, joshturner1967 <[EMAIL PROTECTED]> wrote: > > > > > Hello, > > > I am new to this group but it seems like a good place to ask my > > question. I have a very simple program that has a form. On that form > > I have a MonthCalendar Common Control. This code is written in VS > > 2005. The code itself is pretty straight forward. I have two > > functions one that returns the selected date to a text box and one > > that returns the date directly from the MonthCalendar Common > > Control. I did a quick test in windows app mode to make sure it works > > that the way I want and it does. > > > Now that I have it working I want to turn the App into a DLL. In > > order to do that I did the following. I went into the Build tab of the > > project properties and an enabled the "Register for COM interop by > > clicking yes. I also added "using System.Runtime.InteropServices;" to > > my code I created an ok button and when I hit ok it will return the > > text box value back to the calling app > > > My problem is that I think I must be missing something because my > > class shows up but my my members do not.. Do you guys know what I > > could be missing? > > > I am sure it's something silly but I am not seeing it. > > > Thanks > > Josh- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://cm.megasolutions.net/forums/default.aspx -~----------~----~----~----~------~----~------~--~---
