... using Visual Basic .Net Standard. (so Visual Studio 2003)
I have created a wonderful (well, it is really a "Hello World" style
application) -- in any case it is wonderful to me -- application.
I have fooled "Standard" into creating a .dll library since this is
strictly a COM callable application.
In any case, I have created a Deployment project in my Visual Studio 2003.
Among other things, I have attempted to get it to properly register. To
that end, I have included project output, the generated COM interop.*.dll
files that are "mirrors" of the real COM objects, and the *.tlb. All of
them have one of the vsrd*COM set. (The * varies from type to type
vsdrfCOM, vsdrpCOM, vsdraCOM)
Okay, I run the build and it creates a project1.msi. All is well, so I
execute the .msi on my development computer (Windows XP) and lo and behold,
all the COM objects are properly registered ... CLSID entries are created
for all of them, and so on.
However, I try to run the same .msi on a different computer. It has
Windows ME. Well, first it demands that I download the Microsoft .NET
Framework 1.1 Redistributable. Did that and it apparently installed
alright. Then I reexecuted the .msi. And it _seemed_ to go just fine.
However, my main application was NOT registered. Interestingly, the
Interop.*.dll files (vsdraCOM) did register properly. Only my main program
(vsdrpCOM) didn't register. I strongly suspect that the .tlb did not
register (vsdrfCOM) or did not "execute" or whatever. I am new to all this
COM stuff.
Perhaps this is Operating System dependent given that I am crossing to an
ME machine.
I have searched all over the net and newsgroups and can't find any mention
of a similar problem. Any help would be appreciated.
