ClickOnce Deployment Issue

[DotNetWWW]

Thanks , but Where is the client deployment cache folder located? and another issue is that Should Visual Studio be installed on the server machine or I can publish my app in my pc and then transfer it to Server pc and share it for other clients? Thanks in advance

[Michael Sync]

You are publishing your application on the server directly. If you need to add or modify the required dlls that you already published on the server, you can use MageUI to make changes. then, you can give the installation URl to client to install your application.. then your application will be downloaded to the client machine (under ClickOnce Deployment Cachae folder e.g. C:\Documents and Settings\[User Name]\Local Settings\Apps\2.0) and will run the application..

Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)

[DotNetWWW]

I'm not developing the application in the environment that the server is located , I'm at home and working on project and the server pc is in the customer office somewhere else, In this situation how can I deploy the app? And would you please talk more about MageUI and how to access it? Thanks in advance ,

[Michael Sync]

You can just copy the published folder that you have published in your machine. In server, you can paste your folder on the server. then create the virtual directory on that server m/c and point it to your folder. that's all you need.

DotNetWWW wrote:

would you please talk more about MageUI and how to access it?

You can type megaui on VS 2005 commandline. (not normal commandline). I highly recommend you to read "ClickOnce Deployment Documentation.pdf" from "ClickOnce Community Resource Kit". The main reason why we need megaui tool is that it allows us to add the dlls without republishing the application. another thing is that if you are publishing the application, you have to add the dll to your project.. There are some cases that you don't want to add those adds.. (e.g CAB projects or SCSF project.) For that case, megaui tool helps a lot..

Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)

[DotNetWWW]

Thanks a lot for your great help ,

Michael Sync wrote:

then create the virtual directory

Is it obligatory to create a virtual directory? Or it is enough to share that publish folder on server?

Michael Sync wrote:

The main reason why we need megaui tool is that it allows us to add the dlls without republishing the application

What is the problem if we republish the app?The clickonce deployment checks the app for updates when the client runs it , isn't it?And if we use "The application is available online only" , do we need to be worry about updates?because the app always runs the latest version directly from server?! Also my app has some fonts required to be installed and some files to be copied to client Application Data Folder , I think I should create a windows installer setup for that , yes? Thanks a lot again

[Michael Sync]

DotNetWWW wrote:

Is it obligatory to create a virtual directory? Or it is enough to share that publish folder on server?

Is your server the web server? If yes, it's not necessary to create the Virtual directory. The main reason why we create the VD is that we don't want to use the "Folder Sharing" for that. If someone wants to install the ClickOnce application, they will access this application through URL..

DotNetWWW wrote:

What is the problem if we republish the app?The clickonce deployment checks the app for updates when the client runs it , isn't it?And if we use "The application is available online only" , do we need to be worry about updates?because the app always runs the latest version directly from server?!

No. You don't need to worry about the updates but we don't use that option in our projects.

DotNetWWW wrote:

Also my app has some fonts required to be installed and some files to be copied to client Application Data Folder , I think I should create a windows installer setup for that , yes?

I don't know about that.

Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)

[DotNetWWW]

Thanks

Michael Sync wrote:

No. You don't need to worry about the updates but we don't use that option in our projects.

Why?

[Michael Sync]

DotNetWWW wrote:

Why?

Because we want our application to run offline too. Because we don't want our employees to go back if the connection is down.. Another reason is that we used the dynamic updates (from code) to get the latest updates. So, we want to disable "The application should check for updates" option.

Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)

[DotNetWWW]

Thanks agagin , My app is based on SQL Server 2005 , so if the server is down , running the application in offline mode will be useless , Am I Right? And when I use Online Only option , the "ApplicationName.application" runs the latest version , Am I Right?

[Michael Sync]

DotNetWWW wrote:

My app is based on SQL Server 2005 , so if the server is down , running the application in offline mode will be useless , Am I Right?

Yeah. You are right.

DotNetWWW wrote:

when I use Online Only option , the "ApplicationName.application" runs the latest version , Am I Right?

Yeah. You are right. :)

Thanks and Regards, Michael Sync ( Blog: http://michaelsync.net)

[DotNetWWW]

Thanks , another point is that when I use Online Option , Where the application.exe.config for each client is saved? as I told you that my app connection string is stored in app.config? and in Online Only option , the app is not cached in clinet machine anymore , Am I Right? Thanks a lot , my friend :)