I' am using Mono 2.8
-Vinay
--
View this message in context:
http://mono.1490590.n4.nabble.com/Unable-to-work-with-Configuration-files-tp3014524p3022188.html
Sent from the Mono - Dev mailing list archive at Nabble.com.
___
Mono-devel-list mailing
Could you please attach the xbuild logs for this?
Run it with /v:diag
-Ankit
On Mon, Nov 1, 2010 at 7:26 PM, vinay_rk vinay.kash...@ironmountain.com wrote:
I' am using Mono 2.8
-Vinay
--
View this message in context:
Could it be a bug in xbuild then? Can you try building a clean
checkout with msbuild to see if there is a different behavior? I
haven't run xbuild very much, is it possible to enable some
diagnostics output like for msbuild? To see where exactly they are
being copied.
/Oskar
2010/10/28 vinay_rk
It really seems like a bug with XBuild because when these projects with
MSBuild, I don't see this happening. I now have to see what settings in a
csproj results in this buggy behavior by XBuild. Has anyone had a situation
like this ? with system dll's found copied to the local path after running
So it makes it more mysterious that the stack trace goes through
WindowsIdentity.Impersonate(). All I' am calling in my code is
ConfigurationManager.GetSection(NameOfCUstomSection). The rest is supposed
to be happenening within the framework (In this case the mono framework).
The same code works
On 27.10.2010 14:51, vinay_rk wrote:
So it makes it more mysterious that the stack trace goes through
WindowsIdentity.Impersonate(). All I' am calling in my code is
ConfigurationManager.GetSection(NameOfCUstomSection). The rest is supposed
to be happenening within the framework (In this case
I still don't know how the System.Configuration.dll is being copied into the
output directory. Copy local has not been enabled on any of the
references. After some inspection I found that System.dll,
System.Security.dll and mscorlib.dll are also being copied to the output
directory. And I also
Hi,
When I run my app (that is built using XBuild) in Mono from the command
prompt (using command Mono exe name ) , I always get the below error
whenever the app tries to access the config file. Basically the App is
trying to open some custom config sections.
Error:
FATAL[1]
On Tue, 2010-10-26 at 14:23 -0700, vinay_rk wrote:
Hi,
When I run my app (that is built using XBuild) in Mono from the command
prompt (using command Mono exe name ) , I always get the below error
whenever the app tries to access the config file. Basically the App is
trying to open some
What I' am doing in my AppConfig is define custom sections like this :
configuration
configSections
section name=CustomSectionName
type=FullQualifiedNameOfCustomSectionHandler/
-
-
The custom handler derives from System.Configuration.ConfigurationSection.
There
On Tue, 2010-10-26 at 15:03 -0700, vinay_rk wrote:
What I' am doing in my AppConfig is define custom sections like this :
configuration
configSections
section name=CustomSectionName
type=FullQualifiedNameOfCustomSectionHandler/
-
-
The custom handler
11 matches
Mail list logo