Tuesday, July 24, 2012 3:49 PM
I have some serious problems with my click once deployment right now.
Within my solution i added a project containing some logic for synchronisation, referencing the Microsoft.Synchronisation.Dlls...
Whenever i publish my main application now, i get an error on all clients with the message that Microsoft.Synchronisation... was not found in GAC.
However, this sync-project as well as all Synchronisation.dlls are excluded from my Click once app files. So why are they still required? (My Main app doesn need them)
thanks for help
- Changed Type Bob Wu-MTMicrosoft Contingent Staff, Moderator Wednesday, July 25, 2012 5:39 AM
Tuesday, July 24, 2012 4:25 PM
I was checking the clickonce generated manifest file, and i don't know why these dlls are mentioned as prerequisite?? I excluded them on purpose in my Application files
<dependency> <dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"> <assemblyIdentity name="Microsoft.Synchronization.Data" version="22.214.171.124" publicKeyToken="89845DCD8080CC91" language="neutral" processorArchitecture="msil" /> </dependentAssembly> </dependency> <dependency> <dependentAssembly dependencyType="preRequisite" allowDelayedBinding="true"> <assemblyIdentity name="Microsoft.Synchronization.Data.SqlServerCe" version="126.96.36.199" publicKeyToken="89845DCD8080CC91" language="neutral" processorArchitecture="msil" /> </dependentAssembly> </dependency>
Wednesday, July 25, 2012 5:42 AMModerator
Wednesday, July 25, 2012 4:02 PM
I found the error in my solution but wasn't able to solve it.
I have three projects.
Project1: SyncFx21 which is referencing the Microsoft.Synchronisation.Dlls version 2.1
Project2: SyncOld which is referencing the Microsoft.Synchronisation.Dlls version 1.0
The UI project references project 1 and project 2.
My goal is to exclude these Synchronisation.Dlls from my project - they shouldn't be published. The reason for that is that only some selected users are able to synchronise a device, and for all others i don't want to install them all sync fx components.
The problem now during the click once deployment is probably related to having different versions of the same Synchronisation.Dlls. When I exclude the Synchronisation.Dll from my clickonce deployment, only the Version 2.1 gets excluded and Version 1.0 is alway put into the prerequisites. (even i don't want them there)
I hope I could describe my problem clear enough
Tuesday, July 31, 2012 11:11 AMModerator
I'm still doing research on this issue, if I get anything, I will let you know.
Bob Wu [MSFT]
MSDN Community Support | Feedback to us
Wednesday, August 08, 2012 8:39 AM
As the UI project refers back to project 1 &2 which depends on synchronization dll, it make sense for the clickone project to include it as prerequisites. Since the application are targeting two kinds of end users, is it possible for you to seperate the deployment?
Tracy YU[MSFT] MSDN Community Support
- Edited by Tracy Yu-MSFT Wednesday, August 08, 2012 8:40 AM