Hi Gurus,

I need to know the following issue that come across during AddIn development
and deployment.

1. How can a AddIn communicate with ASP file using XML protocol. I want to
send and receive XML from a ASP file

2. I need to append a Tab at runtime in any Appointment Inspector.
    This will eliminate the chances of conflicts if one tab of another
vendor is already exist.
    My question is, Can I Append MyTab at the end of Appointment Inspector

3. What are the issues and concerns while accessing the Windows Registry
from AddIn or Form. Like Access rights or other problems

4. Do I need any additional tools for AddIn development since I am
developing a simple AddIn that interacts with ASP or database.

5. I am developing AddIn and Forms that simply interacts with ASP or
database. What should I use CDO or Outlook Object Model

6. What are the deployment issues and concerns of a AddIn and Forms. Like
DLLs, Registry setting or etc

Thanks in Advance and sorry for posting in multiple groups

... A Junior AddIn Developer.

I'll take a stab at some of them.

Using the Microsoft XML Parser (now XML Core Services). 3.0 is the version
that ships with Office XP, so you can add msxml3.dll to your project.

Not really. That's not the way Outlook forms work. Adding a new page and its
controls programmatically will cause the item to one-off, i.e. the form
definition embeds in the item and code on the form no longer runs.

Depends on the part of the registry. You should be able to set and get
values for your addin with no problem.

Basic tools are Visual Basic, Office Developer, or Visual C++. I'd recommend
Outlook Spy for drilliing into Outlook and MAPI  properties and Redemption
for working around the security prompts, both from http://www.dimastr.com.

Depends on what you need to do. CDO can do some things that the Outlook
model can't.

Same as any program you need to install on a Windows client. You'll need to
create a setup program.