M
Mark B
Hi,
I have an issue with VSTO deployment. Instead of using ClickOnce deployment,
I create the installer from the traditional windows installer. I had issues
to add the setup project under the same Solution because the configuration
of my registry always got changed from "app.manifest|vstolocal" to
"app.manifest". Therefore I did some research on Google and someone said it
was a known VS2008 bug. They suggested creating a setup project outside the
existing VSTO solution and then add files and assemblies one by one.
That solution works and it correctly installed the VSTO addin. However, as
soon as I opened up Outlook, I got an exception saying that "the
app.manifest may not be valid or the file could not be opened."
Does anyone know what might be wrong?
Thanks in advance
Kyle Huang
I have an issue with VSTO deployment. Instead of using ClickOnce deployment,
I create the installer from the traditional windows installer. I had issues
to add the setup project under the same Solution because the configuration
of my registry always got changed from "app.manifest|vstolocal" to
"app.manifest". Therefore I did some research on Google and someone said it
was a known VS2008 bug. They suggested creating a setup project outside the
existing VSTO solution and then add files and assemblies one by one.
That solution works and it correctly installed the VSTO addin. However, as
soon as I opened up Outlook, I got an exception saying that "the
app.manifest may not be valid or the file could not be opened."
Does anyone know what might be wrong?
Thanks in advance
Kyle Huang