11 Dec
2010
11 Dec
'10
12:39 a.m.
On 10 December 2010 20:30, Florin Ciubotaru <florin.ciubotaru(a)xwiki.com>wrote;wrote:
On Fri, Dec 10, 2010 at 10:44 AM, Paul Harris
<harris.pc(a)gmail.com> wrote:
I have patched a few things, including system logging - it now correctly
falls back to writing a file in a spot that it will be allowed to write to,
and if that is still not possible then it'll show a warning to the user
once.
What I'd like to know now is: where does the ClickOnce installer get built?
Where is the configuration for it? And, were could i put some code to
create a system log?
I'm not familiar with C# etc so if you could just point me in the
potentially correct direction or tell me where the related projects/files
are, that would be appreciated.
thanks
Paul
Hi again,
I've been investigating problems with XWord.
One of the big problems on Vista and Windows7 is this line in Log.cs
EventLog.CreateEventSource(eventSource, logName);
This is a know issue. IIRC I didn't have an optimal solution for it, but
the
logger should fall back to writing to a file is it doesn't have the rights
to create a Windows log.
It can't create a system log at this point as that must be done as
Administrator... and normally its the User running XWord/Word at this
point.
This sort of thing is supposed to be done at the
point of installation,
but
I don't have any idea of how to do this yet.
Does anyone know? Can someone please explain how
the XWord installer
works? The "Setup XWord" project appears to be completely empty to my
untrained eye!
Setup XWord was used on an outdated build of XOffice. The advantage of
using
it was that it allowed custom setup actions(extra screens, custom code like
registering log groups, etc). The issue is that is not well integrated with
VSTO and even with proper code/assembly signing the add-in will fail to
start on some custom Windows and Office distributions.
The current installer is ClickOnce based and is bundled in the "XWord"
project, unfortunately it's harder to customize it.
I guess the only quick & healthy solution to this issue is to remove the
system logging.
Florin Ciubotaru