Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / .NET Framework / Interop / June 2005

Tip: Looking for answers? Try searching our database.

COM without registration

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
ME - 19 Jun 2005 06:57 GMT
Reading a previous post I was able to find a high level overview of COM
without registration:
http://www.simple-talk.com/2005/03/09/com-server-registration/  However, I
was wondering if anyone one knows of other references that could explain
this further.  Specifically I need help creating the manifest files.  I am
not sure I understand the syntax.  A beginners tutorial on this subject
would be great!

Thanks,

Matt
Phil Wilson - 19 Jun 2005 17:41 GMT
There's another article here with more detail:

https://blogs.msdn.com/stevewhitepsfd/articles/category/9237.aspx

The syntax is in MSDN, start here:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sbscs/setup/man
ifest_files_reference.asp


Signature

Phil Wilson
[Microsoft MVP-Windows Installer]

> Reading a previous post I was able to find a high level overview of COM
> without registration:
[quoted text clipped - 7 lines]
>
> Matt
ME - 20 Jun 2005 01:49 GMT
Thank you for that info.  It was extremley helpful.  I have a couple of
questions regarding this type of registration.  I feel you will need to know
what it is I am trying to accomplish first though...

I am writing a GUI interface to a mainframe app that runs in a terminal
window (Reflection for HP - http://www.wrq.com/).  Reflection supports VBA
(in my case it will use the same VBA version installed with Office 2003)
macros.  I want to develop the user interface using .NET as I am more
familure with this languange and it offers more scalabilty for my needs.
The app will send keystrokes back to the Reflection Client via the
Reflection's own Session Object (interface).  (The .NET app refrences a
Reflection Interop Object).  A VBA macro will be used to launch the .NET app
via COM interop (http://www.codeproject.com/dotnet/nettocom.asp ) and pass
the .NET app the running Session object (this makes it easy to get the
current session).  The entire process takes this path:

User Launches a saved Reflection Settings Script > The Script executes the
VBA Macro > The Macro creates the COM .NET object and calls a Method that
starts the .NET App passing along the Session object.

This works great on my development PC where all the COM objects are
registered and ready to go (I selected the "Register for COM interop" option
as necessary).  The trouble though is in Deployment.  I can not for the life
of me get the Setup Project to register .NET COM object correctly so that
the VBA app can create the object. even though I have selected vsdrpCOM as
the Register property (Perhaps I am not doing something right?).

This solution of registering the object without having to make changes to
the registery is a viable solution (I think).  If my under standing is
correct the first manifest file I need is the application manifest.
(application.exe.manifest).  I am assuming this SHOULD be an EXE, not a DLL.
So the question arises, which app in this chain of apps I working with
should get the application manifest file (Reflection?  VBA?  .NET app?)

Thanks,

Matt

> There's another article here with more detail:
>
[quoted text clipped - 15 lines]
>>
>> Matt
Phil Wilson - 20 Jun 2005 16:48 GMT
The registration-free COM works for clients, so start with the exe. VS 2005
Beta 2 almost looks like it supports manifest generation with the manifest
tool, but I haven't found a way to make it put the COM classes in a manifest
instead of an rgs file (for ATL).

To register a COM .NET assembly, mark it for registration (I add the
individual assembly and set it to vsdraCOM). When you do that VS runs regasm
to create a reg file and it imports that reg file into the project. This is
not the same as when you run regasm because the /regfile option does not
register a type library. If you use tlbexp on your assembly and add the
resulting type library to your setup project (I think it will be Register
property vsrdfCOM by default) the install will register the type library -
that might be why it doesn't work.
Signature

Phil Wilson
[Microsoft MVP-Windows Installer]
Definitive Guide to Windows Installer
http://apress.com/book/bookDisplay.html?bID=280

> Thank you for that info.  It was extremley helpful.  I have a couple of
> questions regarding this type of registration.  I feel you will need to
[quoted text clipped - 55 lines]
>>>
>>> Matt
senthilprabu - 21 Jun 2005 07:45 GMT
Hi ,
    I m senthil prabu,currently working in WMI provider creation
project.i created WMI provider dll using .net ATL project. i can
register this dll in .net installed system,but i want to register d dll
in .net not installed system(.net frame work only installed).plz help
me to slove this issue.

Thanks & Regards,
Senthil Prabu R

> Reading a previous post I was able to find a high level overview of COM
> without registration:
[quoted text clipped - 7 lines]
>
> Matt

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.