Registration-Free COM... how to use it?

[GoogleCodeExporter]

Hello MH. I am trying to build my project using registration-free COM, but
although I can run the app directly from the bin/Release directory without
the component registered (having set CSEXWBDLMANLib to isolated), if I
install the software, copy it to a pen drive, then uninstall it and make
sure the component is unregistered, I can not run the program from the pen
drive, getting:

Retrieving the COM class factory for component with CLSID
{A1FE23EF-03EF-4759-B021-668443C37A24} failed due to the following error:
80040154.

I have done some digging around with this issue before, and the best I can
come up with is that it appears that the application manifest which is
required for reg-free COM to work isn't being included in my installer. As
I mentioned, if I run from the bin/Release directory it works fine.
Similarly, if I copy FeedBeast.exe.manifest (FeedBeast.exe being my
program) from bin/Release to the application directory on my pen drive, it
works!

So this cannot be a terribly complicated issue. I just want to know how can
I get this manifest file to be included with the installer? It is being
generated automatically by my project, but the setup project is not
including it!

Any thoughts would be helpful, thanks.

Original issue reported on code.google.com by murray.l...@gmail.com on 18 Jan 2008 at 12:29

[GoogleCodeExporter]

Can't you include the manifest file in the setup manually. Most setup programs, 
including VS, have an option to include additional files in the install 
directory. 
You can even automate the process by using setup scripts which are supported by 
many 
setup programs.

MH

Original comment by mehr...@gmail.com on 18 Jan 2008 at 1:27

[GoogleCodeExporter]

I will try this; I was just thinking maybe I was doing something wrong and that 
it
should be including it by default.

Original comment by murray.l...@gmail.com on 18 Jan 2008 at 4:25

[GoogleCodeExporter]

It seems to work when I include the file manually. It seems rather bizarre that 
this
step must be taken. Why would VS generate the appropriate manifest to allow the 
built
application to be run without registration, but then not include this manifest 
in the
setup project's installation?

Original comment by murray.l...@gmail.com on 20 Jan 2008 at 4:09

[GoogleCodeExporter]

I agree, it does seem strange. However, I am glad that it worked.

MH

Original comment by mehr...@gmail.com on 20 Jan 2008 at 9:23

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Hi...

Actually I have some issues regarding this topic ("Registeration-free 
ComUtilities
COM interop") too... and I'd be more than happy if somebody would help me on 
this.

First... when I followed general instructions for "RegFreeDemo" app... 
everything
went fine (I tested on another PC with no COM registration from an USB stick - 
all
files in a same folder). 

But then... when I did the same for my project ("MyApp" instead of 
"RegFreeDemo")...
this wouldn't work (I recreated also "MyApp.exe.manifest" file changing its 
content
for compliance too). Am I missing something?

Regards, Cristi.

Original comment by xcrys...@gmail.com on 22 Sep 2008 at 9:00

[GoogleCodeExporter]

Ok, I found something on this...
It seems I should not have code in "FrmMain.OnLoad" that calls "Navigate()" 
methods.
Otherwise will raise "InvalidCastException"

Original comment by xcrys...@gmail.com on 22 Sep 2008 at 10:58