Problem with publishing - <filename>.exe.config.deploy file?

[B. Chernick]

I am trying to deploy a Dot Net 2.0 Winforms app using ClickOnce. (Run only,
not install). I am rather new to this technology.

When I install a simple test app I have no problem. But when I try to
deploy my current application which consists of 2 projects within one
solution (and some fairly extensive references) this happens: The app does
not work unless I go into the deployment directory on the server and manually
copy the file app.config.deploy to <Project Name>.exe.config.deploy.

After that, everything works fine.

Anyone else have this problem?

[RobinS]

We're not having this problem. Check the properties on your application
files.

Robin S.
--------------------------
"B. Chernick" <BChe...@discussions.microsoft.com> wrote in message
news:BD40179E-DDDE-43E3...@microsoft.com...

[B. Chernick]

Sorry. Could you be more specific? Are you referring to the settings in the
Publish tab of the Project properties?

[RobinS]

Yes, especially in terms of how the files are included.

If you actually deploy it to be installed rather than run off of the
server, does it work?

Robin S.
---------------------------

"B. Chernick" <BChe...@discussions.microsoft.com> wrote in message

news:5B6549AC-CC2C-4FF9...@microsoft.com...

[B. Chernick]

To the best of my recollection, the problem is the same, whichever way it is
deployed. (I intend to retest this ASAP but for the moment, I seem to be cut
off from the server.)

[B. Chernick]

I've managed to get back on the test server and the problem appears identical
whether the app is setup for install or run online only, the missing
exe.config.deploy file.

The error is as follows:
Downloading http://<server name>/<app name>/<app name>_1_0_0_14/<app
name>.exe.config.deploy did not succeed.
+ The remote server returned an error: (404) Not Found.

[RobinS]

How are you pushing the deployment? Are you using http, ftp, or publishing
it to a file?

Robin S.

----------------------
"B. Chernick" <BChe...@discussions.microsoft.com> wrote in message

news:26499717-E48D-4615...@microsoft.com...

[B. Chernick]

I do not remember any such setting. Probably whatever the default is. (I
would assume http since I am putting a pile of files on a web server
directory.)

Unfortunately I am away from work this week so I will check on this and get
back to you, hopefully next Monday.

Thanks.

[B. Chernick]

I'm afraid I may have made an obvious mistake. I was pushing code to the
server that was compiled in debug mode. Once I compiled the entire solution
as a release, the problem appeared to go away, at least for now.

[RobinS]

That's cool. I've deployed debug versions, but our application is installed
on the desktop, not run from the server. Maybe that makes a difference.
Glad you figured it out!

Robin S.
--------------------------------------

"B. Chernick" <BChe...@discussions.microsoft.com> wrote in message

news:B2AF76D5-32AF-493A...@microsoft.com...

[sadashimizu]

I have a problem with publishing c# solution: 'XXXX.exe.config.deploy did not succeed. + Could not find file'. I tried to find this file in my PC that I coding, but there is no such file. I've checked property>Publish>Application Files..> and there's exe.config file on the list.
I built this solution as 'Release'.
Where should I check? I'm using VS2005.
Thank you.

[sadashimizu]

I solved this by myself. Sorry for bother you. I found .exe.config file and rename it to .exe.config.deploy then copy to server folder. It works fine.

Thank you.

[Warren Caulton]

I fixed a similar error. First I did a clean build of the solution, then a rebuild of the solution, then publish. The exe.config.deploy showed up in the folder.

> On Tuesday, July 03, 2007 9:52 AM BChernic wrote:

> I am trying to deploy a Dot Net 2.0 Winforms app using ClickOnce. (Run only,
> not install). I am rather new to this technology.
>
> When I install a simple test app I have no problem. But when I try to
> deploy my current application which consists of 2 projects within one
> solution (and some fairly extensive references) this happens: The app does
> not work unless I go into the deployment directory on the server and manually
> copy the file app.config.deploy to <Project Name>.exe.config.deploy.
>
> After that, everything works fine.
>
> Anyone else have this problem?

>> On Wednesday, July 11, 2007 12:59 AM RobinS wrote:

>> We're not having this problem. Check the properties on your application
>> files.
>>
>> Robin S.
>> --------------------------

>>> On Friday, July 13, 2007 11:12 AM BChernic wrote:

>>> Sorry. Could you be more specific? Are you referring to the settings in the
>>> Publish tab of the Project properties?
>>>
>>> "RobinS" wrote:

>>>> On Monday, July 16, 2007 3:05 AM RobinS wrote:

>>>> Yes, especially in terms of how the files are included.
>>>>
>>>> If you actually deploy it to be installed rather than run off of the
>>>> server, does it work?
>>>>
>>>> Robin S.
>>>> ---------------------------

>>>>> On Monday, July 16, 2007 8:12 AM BChernic wrote:

>>>>> To the best of my recollection, the problem is the same, whichever way it is
>>>>> deployed. (I intend to retest this ASAP but for the moment, I seem to be cut
>>>>> off from the server.)
>>>>>
>>>>> "RobinS" wrote:

>>>>>> On Monday, July 16, 2007 10:56 AM BChernic wrote:

>>>>>> I've managed to get back on the test server and the problem appears identical
>>>>>> whether the app is setup for install or run online only, the missing
>>>>>> exe.config.deploy file.
>>>>>>
>>>>>> The error is as follows:
>>>>>> Downloading http://<server name>/<app name>/<app name>_1_0_0_14/<app
>>>>>> name>.exe.config.deploy did not succeed.
>>>>>> + The remote server returned an error: (404) Not Found.
>>>>>>
>>>>>> "RobinS" wrote:

>>>>>>> On Tuesday, July 24, 2007 2:08 AM RobinS wrote:

>>>>>>> How are you pushing the deployment? Are you using http, ftp, or publishing
>>>>>>> it to a file?
>>>>>>>
>>>>>>> Robin S.
>>>>>>> ----------------------

>>>>>>>> On Wednesday, July 25, 2007 3:16 PM BChernic wrote:

>>>>>>>> I do not remember any such setting. Probably whatever the default is. (I
>>>>>>>> would assume http since I am putting a pile of files on a web server
>>>>>>>> directory.)
>>>>>>>>
>>>>>>>> Unfortunately I am away from work this week so I will check on this and get
>>>>>>>> back to you, hopefully next Monday.
>>>>>>>>
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>> "RobinS" wrote:

>>>>>>>>> On Thursday, August 02, 2007 1:28 PM BChernic wrote:

>>>>>>>>> I'm afraid I may have made an obvious mistake. I was pushing code to the
>>>>>>>>> server that was compiled in debug mode. Once I compiled the entire solution
>>>>>>>>> as a release, the problem appeared to go away, at least for now.
>>>>>>>>>
>>>>>>>>> "RobinS" wrote:

>>>>>>>>>> On Monday, August 20, 2007 12:07 AM RobinS wrote:

>>>>>>>>>> That's cool. I've deployed debug versions, but our application is installed
>>>>>>>>>> on the desktop, not run from the server. Maybe that makes a difference.
>>>>>>>>>> Glad you figured it out!
>>>>>>>>>>
>>>>>>>>>> Robin S.
>>>>>>>>>> --------------------------------------
>>>>>>>>>> "B. Chernick" <BChe...@discussions.microsoft.com> wrote in message
>>>>>>>>>> news:B2AF76D5-32AF-493A...@microsoft.com...

>>>>>>>>>>>> On Friday, August 01, 2008 4:58 PM Sada Shimizu wrote:

>>>>>>>>>>>> I solved this by myself. Sorry for bother you. I found .exe.config file and rename it to .exe.config.deploy then copy to server folder. It works fine.
>>>>>>>>>>>>
>>>>>>>>>>>> Thank you.

>>>>>>>>>>>> Submitted via EggHeadCafe - Software Developer Portal of Choice
>>>>>>>>>>>> Kentico CMS for ASP.NET Sites
>>>>>>>>>>>> http://www.eggheadcafe.com/tutorials/aspnet/ee551a85-2206-446e-bc7d-c978f60ec671/kentico-cms-for-aspnet-sites.aspx