Can't run a C# Program Without VS2005

[chris_doran]

Firstly, let me come clean and say I don't really know what I'm doing.

Classic tale: I'm using some code developed by a third party who is now
uncontactable. Further, he did it in C# and .NET which are a total
mystery to me. My bit of the project is done in C and links to his bit
which is a DLL. As VS2005 for C doesn't seem to know about
App.config.exes , he provided a .exe.config file saying "this will work
with everything -- just rename it in the same directory as your .exe".

All is well on a "developmen t" system that has VS2005 installed, but
our customers' machines don't. There, everything fails with a message:

Exception: The configuration section for Logging cannot be found in the
configuration source.
at
Microsoft.Pract ices.Enterprise Library.Logging .LogWriterStruc tureHolderCusto mFactory.Create Object(IBuilder Context
context, String name, IConfigurationS ource configurationSo urce,
ConfigurationRe flectionCache reflectionCache )
at ... <snip long traceback chain>

but the .exe.config _does_ have a section called
"loggingConfigu ration".

The "Exception ..." message seems to be coming from one of the
functions _fastClientServ ice.lookupQueue Reference,
_fastClientServ ice.createQueue , or _fastClientServ ice.Connect which I
can't find any documentation for. Are they Microsoft's or something
written by the contractor?

Possibly significantly, this is the same message I get when the
..exe.config file is deleted, so perhaps something is looking in the
wrong place. Are there any environment variables or equivalent that
have to be set up? The files are all in the same places on both
customer and development machines.

Curiously, if I replace the real .exe.config with a junk file (e.g. a
..exe) the programs doesn't even get that far and just say: "The system
cannot execute the specified program." This suggests that the
..exe.config is being found at least once.

Chris

[PL]

The Enterprise Library is not part of the core framework, possibly it is
missing on the target machine, try to download and install it separately on
the target machine.

http://msdn.microsoft.com/library/de...ml/EntLib2.asp

PL.
<ch*********@po stmaster.co.uk> skrev i meddelandet
news:11******** **************@ j73g2000cwa.goo glegroups.com.. .

Firstly, let me come clean and say I don't really know what I'm doing.

Classic tale: I'm using some code developed by a third party who is now
uncontactable. Further, he did it in C# and .NET which are a total
mystery to me. My bit of the project is done in C and links to his bit
which is a DLL. As VS2005 for C doesn't seem to know about
App.config.exes , he provided a .exe.config file saying "this will work
with everything -- just rename it in the same directory as your .exe".

All is well on a "developmen t" system that has VS2005 installed, but
our customers' machines don't. There, everything fails with a message:

Exception: The configuration section for Logging cannot be found in the
configuration source.
at
Microsoft.Pract ices.Enterprise Library.Logging .LogWriterStruc tureHolderCusto mFactory.Create Object(IBuilder Context
context, String name, IConfigurationS ource configurationSo urce,
ConfigurationRe flectionCache reflectionCache )
at ... <snip long traceback chain>

but the .exe.config _does_ have a section called
"loggingConfigu ration".

The "Exception ..." message seems to be coming from one of the
functions _fastClientServ ice.lookupQueue Reference,
_fastClientServ ice.createQueue , or _fastClientServ ice.Connect which I
can't find any documentation for. Are they Microsoft's or something
written by the contractor?

Possibly significantly, this is the same message I get when the
.exe.config file is deleted, so perhaps something is looking in the
wrong place. Are there any environment variables or equivalent that
have to be set up? The files are all in the same places on both
customer and development machines.

Curiously, if I replace the real .exe.config with a junk file (e.g. a
.exe) the programs doesn't even get that far and just say: "The system
cannot execute the specified program." This suggests that the
.exe.config is being found at least once.

Chris

[chris_doran]

PL wrote:

The Enterprise Library is not part of the core framework, possibly it is
missing on the target machine, try to download and install it separately on
the target machine.

http://msdn.microsoft.com/library/de...ml/EntLib2.asp

PL.
The Enterprise Library _is_ installed on the target machine, or so I am
told by my boss (who has disappeared for the weekend leaving me to fix
this for an important meeting with a customer on Monday). However, he
says it was "installed manually", so I'm slightly suspicious. I asked
if it could be installed "properly", but he said NO. I've copied what I
am told are the DLLs actually required, including
Microsoft.Pract ices.Enterprise library.Logging .dll, to just about
everywhere, but to no effect.

Chris

<ch*********@po stmaster.co.uk> skrev i meddelandet
news:11******** **************@ j73g2000cwa.goo glegroups.com.. .

Firstly, let me come clean and say I don't really know what I'm doing.

Classic tale: I'm using some code developed by a third party who is now
uncontactable. Further, he did it in C# and .NET which are a total
mystery to me. My bit of the project is done in C and links to his bit
which is a DLL. As VS2005 for C doesn't seem to know about
App.config.exes , he provided a .exe.config file saying "this will work
with everything -- just rename it in the same directory as your .exe".

All is well on a "developmen t" system that has VS2005 installed, but
our customers' machines don't. There, everything fails with a message:

Exception: The configuration section for Logging cannot be found in the
configuration source.
at
Microsoft.Pract ices.Enterprise Library.Logging .LogWriterStruc tureHolderCusto mFactory.Create Object(IBuilder Context
context, String name, IConfigurationS ource configurationSo urce,
ConfigurationRe flectionCache reflectionCache )
at ... <snip long traceback chain>

but the .exe.config _does_ have a section called
"loggingConfigu ration".

The "Exception ..." message seems to be coming from one of the
functions _fastClientServ ice.lookupQueue Reference,
_fastClientServ ice.createQueue , or _fastClientServ ice.Connect which I
can't find any documentation for. Are they Microsoft's or something
written by the contractor?

Possibly significantly, this is the same message I get when the
.exe.config file is deleted, so perhaps something is looking in the
wrong place. Are there any environment variables or equivalent that
have to be set up? The files are all in the same places on both
customer and development machines.

Curiously, if I replace the real .exe.config with a junk file (e.g. a
.exe) the programs doesn't even get that far and just say: "The system
cannot execute the specified program." This suggests that the
.exe.config is being found at least once.

Chris