Gareth,

Some quick things to check.
1) Ensure that the file is set to have a type of "Content"
2) If your config file is in a separate project to the executable make
sure that the deployment dropdown has "Deploy to ..." rather than "Same
as consuming device". For some reason "Same as consuming device" content
files don't get copied 
3) If you are using source control make sure you have the file checked
out as otherwise it will work once, but successive deploys will not copy
the file as it is marked read only (Note, that this isnt your problem,
as it would work once... )

Cheers

Greg

-----Original Message-----
From: Gareth Mc Leigh [mailto:[EMAIL PROTECTED] 
Sent: Wednesday, 25 May 2005 20:48
To: [email protected]
Subject: log4net and .net Compact Framework

Hi,
I want to use log4net when developing for mobile devices (as there is no
Console.out).

I can get the .netcf example to run and it creates the apporpriate log
text files.

However, I don't seem to be able to create create logs on simple
programs that I write. For some reason the config file is not copied
across in deployment.

.NETCF EXAMPLE:

Copying files from 'C:\Mobile
Development\Logger\log4net-1.2.0-beta8\bin\netcf\1.0\release\' to
'\Program Files\ConsoleAppCS'
Copying log4net.dll
Copying content files to '\Program Files\ConsoleAppCS'
Copying ConsoleApp.exe.config

MyExample:
Copying files from 'C:\Mobile
Development\Logger\log4net-1.2.0-beta8\bin\netcf\1.0\debug\' to
'\Program Files\check'
Copying log4net.dll

I have tried various simple logs and even a carbon copy of the .netcf
example but the .config file is never copied across.
I have also looked at the differences between the project properties and
there does not seem to be any.
I use "log4net.Config.DOMConfigurator.Configure();" in my examples to
locate the config file, but I think this is correct.


Any help would be great,
Gareth.


NOTICE
This e-mail and any attachments are private and confidential and may contain 
privileged information. If you are not an authorised recipient, the copying or 
distribution of this e-mail and any attachments is prohibited and you must not 
read, print or act in reliance on this e-mail or attachments.
This notice should not be removed.

Reply via email to