w 1.1 or 2.0 will behave. It's probably worth experimenting
>with though.
>
>Geoff
>
>> -Original Message-
>> From: Discussion of advanced .NET topics. [mailto:ADVANCED-
>> [EMAIL PROTECTED] On Behalf Of Eddie Lascu
>> Sent: 0
ve. It's probably worth experimenting
>with though.
>
>Geoff
>
>> -Original Message-
>> From: Discussion of advanced .NET topics. [mailto:ADVANCED-
>> [EMAIL PROTECTED] On Behalf Of Eddie Lascu
>> Sent: 02 January 2007 12:42
>&g
ehave. It's probably worth experimenting
>with though.
>
>Geoff
>
>> -Original Message-
>> From: Discussion of advanced .NET topics. [mailto:ADVANCED-
>> [EMAIL PROTECTED] On Behalf Of Eddie Lascu
>> Sent: 02 January 2007 12:42
anuary 2007 12:42
> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM
> Subject: Re: [ADVANCED-DOTNET] Configuration file name as a start up
> parameter
>
> Why don't you rename your cMyConfigFile.config file as a first step of
> your
> application. The reason why you would need a d
bject: [ADVANCED-DOTNET] Configuration file name as a start up
parameter
Hi,
I have an application where I need to provide the name of the configuration
file as a start up parameter (for example myapp.exe -cMyConfigFile). The
application is started as a windows service.
The application uses other assem
Hi,
I have an application where I need to provide the name of the configuration
file as a start up parameter (for example myapp.exe -cMyConfigFile). The
application is started as a windows service.
The application uses other assemblies that use the "standard"
System.Configuration.ConfigurationMan
