Cannot find Application Configuration File under Win2000

[Charles Law]

A client has just reported that when they run a VB.NET application on
Windows 2000 an error is reported "Cannot find Application Configuration
File". It runs fine on Windows XP Pro.

Does anyone know what file it could be referring to? The application does
use bespoke files when it starts, but these are all present.

TIA

Charles

 

[Jeff Dillon]

Was the application installed via a setup package?

Jeff

 

[Charles Law]

Hi Jeff

No. The solution was zipped and extracted onto the client's m/c. They have
VS.NET (2003) installed, as have I. They built the solution w/o error, but
when they run it, it throws this exception.

Charles

 

[Chris Dunaway]

Typically, the application configuration file is named AppName.exe.config
where AppName is the actual name of the .exe. Is that file present?
Normally the App.Config file gets automatically renamed when compiled.

--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.

 

[Charles Law]

I don't know if such a file exists on the Win2k m/c, but in any case it
doesn't exist on the XP m/c, and that one works.

Further information though, I took the solution - pre-built - to the Win2k
m/c and ran it there, and it worked. I then built the solution on the Win2k
m/c and ran the exe outside the IDE and it worked. It is as if running the
pre-built version affected the target m/c so that it could then run a
version built locally.

I also noted that a different error was being reported: ProjectX or one of
its components could not be found. This error occurred before any code
started executing, so I don't think it can be anything particular that my
code is doing or relies upon. Needless to say ProjectX was present, and in
the bin directory.

Sorry if the information is a bit garbled, but any thoughts?

Charles

Typically, the application configuration file is named AppName.exe.config
where AppName is the actual name of the .exe. Is that file present?
Normally the App.Config file gets automatically renamed when compiled.

--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.

 

[Guest]

Um yes. Create a setup package, and install it normally? Zip file installs
don't register objects.

Time to learn how to build setup packages. Darn.

Jeff

I don't know if such a file exists on the Win2k m/c, but in any case it
doesn't exist on the XP m/c, and that one works.

Further information though, I took the solution - pre-built - to the Win2k
m/c and ran it there, and it worked. I then built the solution on the Win2k
m/c and ran the exe outside the IDE and it worked. It is as if running the
pre-built version affected the target m/c so that it could then run a
version built locally.

I also noted that a different error was being reported: ProjectX or one of
its components could not be found. This error occurred before any code
started executing, so I don't think it can be anything particular that my
code is doing or relies upon. Needless to say ProjectX was present, and in
the bin directory.

Sorry if the information is a bit garbled, but any thoughts?

Charles

Does anyone know what file it could be referring to? The application
does
use bespoke files when it starts, but these are all present.

Typically, the application configuration file is named AppName.exe.config
where AppName is the actual name of the .exe. Is that file present?
Normally the App.Config file gets automatically renamed when compiled.

--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.

 

[Charles Law]

Hi Jeff

Perhaps I didn't explain my problem well enough. I am not trying to install
the application on the client m/c. I want only to pass to them the source
code so that they too can build and run it. Correct me if I am wrong, but
that is not the role of a setup package.

Charles

Um yes. Create a setup package, and install it normally? Zip file installs
don't register objects.

Time to learn how to build setup packages. Darn.

Jeff

I don't know if such a file exists on the Win2k m/c, but in any case it
doesn't exist on the XP m/c, and that one works.

Further information though, I took the solution - pre-built - to the
Win2k
m/c and ran it there, and it worked. I then built the solution on the Win2k
m/c and ran the exe outside the IDE and it worked. It is as if running
the
pre-built version affected the target m/c so that it could then run a
version built locally.

I also noted that a different error was being reported: ProjectX or one
of
its components could not be found. This error occurred before any code
started executing, so I don't think it can be anything particular that my
code is doing or relies upon. Needless to say ProjectX was present, and
in
the bin directory.

Sorry if the information is a bit garbled, but any thoughts?

Charles

On Fri, 12 Nov 2004 00:21:05 -0000, Charles Law wrote:

Does anyone know what file it could be referring to? The application
does
use bespoke files when it starts, but these are all present.

Typically, the application configuration file is named AppName.exe.config
where AppName is the actual name of the .exe. Is that file present?
Normally the App.Config file gets automatically renamed when compiled.

--
Chris

dunawayc[AT]sbcglobal_lunchmeat_[DOT]net

To send me an E-mail, remove the "[", "]", underscores ,lunchmeat, and
replace certain words in my E-Mail address.