G
George
Hi,
I have a little bit off topic question. What is the best (or most used)
solution for writing Outlook forms?
I decided to write small calendar (project) form, with some data stored in
SQL Server (for example project list), and also cache them for offline use
(for example as xml file in users Local Settings folder). I also want to use
it with Exchange server for massive usage and also for standard pst file.
Just now I'm thinking of the best solution how do to it. I want to use .NET
technology if it is possible.
1, Classic form with code behind
I have already used it in previous version of this small project.
Advantages
- as admin on Exchange you can easy to install it to every user (with
script)
- easy to update
Disadvantages
- whole form with code (which can be viewed) is send to another users (when
using scheduling), possible security issues (SQL username and password
stored in code (I can use NT authentication), etc
2, Form with Addin
It sounds good for me, but I see ptoblems with central administration.
I have no experience with programming addins for Outlook, but may be it will
be the best solution. The form is without code (or with simple one) and most
of code is hidden in addin. This solution is like MS Outllook BCM.
Advantages
- form without code
- code is hidden in addin
- outside user cannot see the code (they only see filled form)
Disadvantages
- central instalation from Exchange?
- how to central update addin?
3, ...
May be there are another solutions which is not just in my mind
Can you share your experience and ideas?
Thanks a lot.
George
I have a little bit off topic question. What is the best (or most used)
solution for writing Outlook forms?
I decided to write small calendar (project) form, with some data stored in
SQL Server (for example project list), and also cache them for offline use
(for example as xml file in users Local Settings folder). I also want to use
it with Exchange server for massive usage and also for standard pst file.
Just now I'm thinking of the best solution how do to it. I want to use .NET
technology if it is possible.
1, Classic form with code behind
I have already used it in previous version of this small project.
Advantages
- as admin on Exchange you can easy to install it to every user (with
script)
- easy to update
Disadvantages
- whole form with code (which can be viewed) is send to another users (when
using scheduling), possible security issues (SQL username and password
stored in code (I can use NT authentication), etc
2, Form with Addin
It sounds good for me, but I see ptoblems with central administration.
I have no experience with programming addins for Outlook, but may be it will
be the best solution. The form is without code (or with simple one) and most
of code is hidden in addin. This solution is like MS Outllook BCM.
Advantages
- form without code
- code is hidden in addin
- outside user cannot see the code (they only see filled form)
Disadvantages
- central instalation from Exchange?
- how to central update addin?
3, ...
May be there are another solutions which is not just in my mind
Can you share your experience and ideas?
Thanks a lot.
George