I was monkeying around with a ClickOnce deployment, and it failed. No big deal, I was just "checking it out." But now when I try to compile my app, I get:

Failed to connect to '\\BCSHANP41\Misc\' with the following error: Unable to create the Web site '\\BCSHANP41\Misc'. The path '\\BCSHANP41\Misc' does not exist or you do not have access. The filename, directory name, or volume label syntax is incorrect.

What do I need to do to get it to stop trying to connect to that folder (where I tried to deploy my app)?

---

Writer / Photographer / Drummer

The Publish Wizard appears.

In the Where do you want to publish the application? page, enter a valid file path using the format \\machinename\applicationname , then click Next.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

...but it does not give an actual example of what "\\machinename\applicationname " should be. Should it be, e.g., "\\BCSHANP41\MySharedFolder " or should it be "\\BCSHANP41\MySharedFolder\MyApp.exe " or should it be something else altogether? I used "\\BCSHANP41\MySharedFolder " figuring it knew the .exe name (which failed), but the phrase "\\machinename\applicationname " gives me pause...

Also:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Note
If users will install the application from the Web, this file path must correspond to the URL that the users will access. For example, if the users will install from http:\\www.microsoft.com\myapplication\publish.htm, you would enter the path c:\inetpub\wwwroot\myapplication.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

After giving instructions earlier for a web deployment, it seems to confuse the issue by making it sound like you can web-deploy an app published to a file share (first it separates them, then it amalgamates them)

Ok, let me clarify the document:

For the first problem, the path should be \\BCSHANP41\MySharedFolder , but make sure the user has permission to modify the shared folder. If you are going through permission problems now, you can try to change the permission of the shared folder to let "Everyone" have the permission to "Modify".

For the second problem, please don't confuse the published location with install location. You probably published to a file share, but you may want to install from a website. As you can see from the publish page of the project, you can specify the install path if it is different from the publish location. If you don't specify, the application will be installed from the published location.

Please feel free to let me know if you have anything unclear.

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

I was able to get this err msg to go away by stripping the following out of the cs.proj file:

<ManifestCertificateThumbprint>326162F5E30C73627F0A30CED80474F85D55EFE3</ManifestCertificateThumbprint>
<ManifestKeyFile>WpfMania_TemporaryKey.pfx</ManifestKeyFile>
<GenerateManifests>true</GenerateManifests>
<SignManifests>true</SignManifests>
<PublishUrl>\\BCSHANP41\Misc\</PublishUrl>
<Install>true</Install>
<InstallFrom>Unc</InstallFrom>
<UpdateEnabled>true</UpdateEnabled>
<UpdateMode>Foreground</UpdateMode>
<UpdateInterval>7</UpdateInterval>
<UpdateIntervalUnits>Days</UpdateIntervalUnits>
<UpdatePeriodically>false</UpdatePeriodically>
<UpdateRequired>false</UpdateRequired>
<MapFileExtensions>true</MapFileExtensions>
<ApplicationRevision>0</ApplicationRevision>
<ApplicationVersion>1.0.0.%2a</ApplicationVersion>
<UseApplicationTrust>false</UseApplicationTrust>
<PublishWizardCompleted>true</PublishWizardCompleted>

...Maybe there should be an "Unpublish Wizard" -- or is there?

---

Writer / Photographer / Drummer

Hi Clay,

Did you make sure the UNC path "BCSHANP41\Misc\" is available in your machine? If yes, did you have the access to the specific folder?

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

Hi Clay,

Did you make sure the UNC path "BCSHANP41\Misc\" is available in your machine? If yes, did you have the access to the specific folder?

I'm not sure I understand the question. BCSHANP41 is my own machine, so I have access to all the folders.

IMO, the ClickOnce wizard is not very helpful. It should show examples of what format is expected for the three types of deployment (CD, shared drive, web site). I would expect that if I chose either Shared Drive OR CD to be deployed tomy own machine, I could enter "C:\Misc" and then the necessary files would be generated and placed in the C:\Misc folder.

I have done a fair amount of research on ClickOnce, and tried it out a few times, and it seems to be quite obstruse and not well documented. Sometimes it works, sometimes it doesn't, and there doesn't seem to be any rhyme or reason for its fickleness.

---

Writer / Photographer / Drummer

Hi Clay,

I think it's well documented, but you fail to find it.

Please refer to this document for the steps on publishing to the web server, shared drive, and cd.


Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

Hi Clay,

I think it's well documented, but you fail to find it.

Please refer to this document for the steps on publishing to the web server, shared drive, and cd.

Thanks for that link, Bruce.

IMO, these instructions are not easy to follow, to wit, here is an excerpt:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
To publish to a file share
In Solution Explorer, select the application project.

On the Build menu, click Publish Projectname.

The Publish Wizard appears.

In the Where do you want to publish the application? page, enter a valid file path using the format \\machinename\applicationname, then click Next.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

...but it does not give an actual example of what "\\machinename\applicationname" should be. Should it be, e.g., "\\BCSHANP41\MySharedFolder" or should it be "\\BCSHANP41\MySharedFolder\MyApp.exe" or should it be something else altogether? I used "\\BCSHANP41\MySharedFolder" figuring it knew the .exe name (which failed), but the phrase "\\machinename\applicationname" gives me pause...

Also:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Note
If users will install the application from the Web, this file path must correspond to the URL that the users will access. For example, if the users will install from http:\\www.microsoft.com\myapplication\publish.htm, you would enter the path c:\inetpub\wwwroot\myapplication.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

After giving instructions earlier for a web deployment, it seems to confuse the issue by making it sound like you can web-deploy an app published to a file share (first it separates them, then it amalgamates them)

---

Writer / Photographer / Drummer

The Publish Wizard appears.

In the Where do you want to publish the application? page, enter a valid file path using the format \\machinename\applicationname , then click Next.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

...but it does not give an actual example of what "\\machinename\applicationname " should be. Should it be, e.g., "\\BCSHANP41\MySharedFolder " or should it be "\\BCSHANP41\MySharedFolder\MyApp.exe " or should it be something else altogether? I used "\\BCSHANP41\MySharedFolder " figuring it knew the .exe name (which failed), but the phrase "\\machinename\applicationname " gives me pause...

Also:
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Note
If users will install the application from the Web, this file path must correspond to the URL that the users will access. For example, if the users will install from http:\\www.microsoft.com\myapplication\publish.htm, you would enter the path c:\inetpub\wwwroot\myapplication.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

After giving instructions earlier for a web deployment, it seems to confuse the issue by making it sound like you can web-deploy an app published to a file share (first it separates them, then it amalgamates them)

Ok, let me clarify the document:

For the first problem, the path should be \\BCSHANP41\MySharedFolder , but make sure the user has permission to modify the shared folder. If you are going through permission problems now, you can try to change the permission of the shared folder to let "Everyone" have the permission to "Modify".

For the second problem, please don't confuse the published location with install location. You probably published to a file share, but you may want to install from a website. As you can see from the publish page of the project, you can specify the install path if it is different from the publish location. If you don't specify, the application will be installed from the published location.

Please feel free to let me know if you have anything unclear.

Best regards,
Bruce Zhou

---

Please mark the replies as answers if they help and unmark if they don't.

On the "How Will Users Install the Application" page of the Publish / ClickOnce Wizard, the middle option ("From a UNC path or file share" has a Browse button. However, if you select the location from there, it doesn't enter it into the associated TextBox in the expected format, so that you get the err msg, "The string must be a fully qualified UNC path, for example "\\server\myapplication"."

It sets the TextBox to "C:\QuickURLsShared," whereas it should be "\\BCSHANP41\QuickURLsShared\"

---

Writer / Photographer / Drummer