I have created my project by clickonce technolgy, my project size is 10 MB,
My main EXE file is 8 MB,
now when I have to update small thing as an other refreneced file , the update should download all 10 MB again ...
that is a probelm because my project is going o be 40 MB,
Is there any soultion to download the small file changes
because EXe file need to download each time :(

ClickOnce update
Ashraf Gawdat
Placebo
Sandeep Saxena
I have projects work together to give u full functionaity, as, One for accounting, other for reprting .. etc
pg53
The main reason is so the user can roll back an update installed with click once. There is also the possibility of the main exe crashing because it is seeing the wrong version of project2.
adam11235
ok,
example:
I have Project1 - the main project - and project 2 is reference in projec1,
now if ihave change project2 why I need to download project1
I think it should copying localy right
but this is not!!
Quilnux
I think u have missunderstanding,
I have no problem in update itself, but the problem is how to decrease download bytes
The biggest file in most of the applications is EXE file, no for each update I need to download the EXE file even if I have not update it, because I build it each time when I'm publishing, that mean each updating will download the last build for EXE!!
now how can I prevent EXE file to download or update if it is not has changes
Got it
Dinesh Chandnani
You will have to create your own method of doing this. I would have a database or webservice which tells the latest version number of the app and where to download the update. If there is an update available process.start a update program and close the main application. Have the update application download the update, install it and then restart the main program.
Lazo
liangguotx
See Choosing a ClickOnce Update Strategy for more info
polejnik
no it is not
it is One application has many exe file talking together
that is all
TimL
Billy Hollis did an session on loading forms on the fly at user group meeting I went to. He broke the application into several parts. Each part started off as a windows application. Once the part was complete he converted it to a dll by changing the project type to class library and recompiling. The main program displayed a list of the parts and would load the parts on the fly with activator create instance. Here is a link to an example he made. My tought here is that you could have the main program check for updates to the dlls and download them as needed. I would only deploy the updates to the main program with click once.
Beerwolf