Problem with one touch deployment

[Mark Baldwin]

I can create a new project, add a button that displays a MessageBox and then
publish it to the localhost. This works as expected.

However, when I publish an existing application, I get no errors yet the
publish location is empty! This existing project was once copied across from
another machine but I have been publishing it to a file location with no
problems, when I switch it to a URL, it doesn't work.

The publish URL is http://localhost/test - note this works with a new
project just not with the existing project. I have tried a filesystem path
"c:\inetpub\wwwroot\test" and I get the same problem.

Any help much appreciated...

 

[Mark Baldwin]

Just to clarify, I have been using a UNC path to publish and it has been
working with no problems but changing to a URL or local file path results in
the published folder being empty. There are no errors being displayed.

 

[Guest]

C:\Inetpub\wwwroot\publish.htm

This is the page that you should launch and it gives an option to run the
app(if you stick to the default publish properties). If there is a version
number, it should put all the exes in the folder followed by the version
number. You can also launch the exe from that folder. By default, the
version number gets incremented everytime.

 

[Linda Liu [MSFT]]

Hi Mark,

Based on my understanding, you copy a WinForms application project to a
machine(let's call it A) from another machine(let's call it B) and publish
this application via ClickOnce on the machine A. The problem is that if the
publish location is a URL,e.g http://localhost/test, the published folder,
i.e. c:\inetpub\wwwroot\test is empty. If I'm off base, please feel free to
let me know.

I performed a test according to your description, but didn't reproduce the
problem.

I create a WinForms application project on a machine B and then copy the
project to a machine A. Then I open the project with VS05 on the machine A
and publish it via ClickOnce. The publish location is a URL:
http://localhost/MyTest.

After the publish finishes, the published folder c:\inetpub\wwwroot\MyTest
contains the published files such as publish.htm, setup.exe, deployment
manifest and application manifest.

Could you tell me how you publish the application after you copy it from
another machine?

Sincerely,
Linda Liu
Microsoft Online Community Support

==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications.

Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
==================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Mark Baldwin]

I only suspect the problem is related to the project being moved.

Lets say I have the existing project called "existing" and a new project
called "new".

Once I hace created the new project, I right click it in solution explorer,
select properties and then click the publish page, then click "publish now".
The project compiles and the installation web page appears - the "new"
folder has been created on http://localhost/new

If I do the same with the existing project, it compiles but does not publish
to the web server.

Looking in the property pages for each project, the settings are the same on
every page except obviously the relevent names are different, new and
existing. The existing project was signed with a certificate issued to my
old machine, I have since recreated this (though this hasn't fixed the
problem).

I have tried various ways to publish including clicking the "publish wizard"
and right clicking the project in solution explorer and selecting publish
from there.

However the strange thing is that the existing project has always published
to a UNC path \\<ip>\<folder>

 

[Linda Liu [MSFT]]

Hi Mark,

Thank you for your prompt response.

You may have a try deleting all the files in the Bin folder of the existing
project and setting the Publish Version to 1.0.0.0 in the Publish tab
within the Project Designer.

Hope this helps.

Sincerely,
Linda Liu
Microsoft Online Community Support

 

[Mark Baldwin]

Linda,

Thanks but I have fixed this problem now, well kind of. I have removed all
dependencies for the project and it now deploys. I am not sure why this
works.

 

[Linda Liu [MSFT]]

Hi Mark,

Thank you for your feedback on how you succeed in solving this problem.

Could you tell me what the dependencies for the project are?

If you create a new project and add such these dependencies in the new
project, and then publish the new application to the local host, does this
problem exist?

Sincerely,
Linda Liu
Microsoft Online Community Support