ClickOnce XmlSerializers.dll.deploy

[=?Utf-8?B?QW5kcmV3X2QxMjM=?=]

Here is my problem. I have an app that has over 9 web services. For years I
had not issues with clickonce but now it looks like the build is missing
XmlSerializers.dll.deploy. I did have this issue once in vs 2005 and one the
problem just went away. Well now its back. If I build the app 20 times it
may work once. I did find that if I remove this as a required dll that I can
get my program to run. I can't seem to find any info about this problem. I
did try to rebuild my program on two different computers. I am using vs 2008
sp1. My program is using 2.0 framework but the error happen even on 3.5.
One thing I found makes the build run is doing big changes like adding a new
from or Changing the frame work. But this will only work for one build.

PLATFORM VERSION INFO
Windows : 5.1.2600.196608 (Win32NT)
Common Language Runtime : 2.0.50727.3053
System.Deployment.dll : 2.0.50727.3053 (netfxsp.050727-3000)
mscorwks.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfdll.dll : 2.0.50727.3053 (netfxsp.050727-3000)
dfshim.dll : 2.0.50727.3053 (netfxsp.050727-3000)

SOURCES
Deployment url :
file:///C:/Documents%20and%20Settings/Andrew/Desktop/vdiworkflow/NPCC/NPCC/bin/Release/app.publish/NPCC.application
Application url :
file:///C:/Documents%20and%20Settings/Andrew/Desktop/vdiworkflow/NPCC/NPCC/bin/Release/app.publish/Application%20Files/NPCC_5_0_2_8/NPCC.exe.manifest

IDENTITIES
Deployment Identity : NPCC.application, Version=5.0.2.8, Culture=neutral,
PublicKeyToken=413cbacad869ec29, processorArchitecture=msil
Application Identity : NPCC.exe, Version=5.0.2.8, Culture=neutral,
PublicKeyToken=413cbacad869ec29, processorArchitecture=msil, type=win32

APPLICATION SUMMARY
* Online only application.

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later
in the log.
* Activation of C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\NPCC.application resulted in exception. Following failure messages were detected:
+ Downloading file:///C:/Documents and
Settings/Andrew/Desktop/vdiworkflow/NPCC/NPCC/bin/Release/app.publish/Application Files/NPCC_5_0_2_8/NPCC.XmlSerializers.dll.deploy did not succeed.
+ Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .
+ Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .
+ Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [8/15/2008 9:31:45 PM] : Activation of C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\NPCC.application has started.
* [8/15/2008 9:31:50 PM] : Processing of deployment manifest has
successfully completed.
* [8/15/2008 9:31:50 PM] : Installation of the application has started.
* [8/15/2008 9:31:50 PM] : Processing of application manifest has
successfully completed.
* [8/15/2008 9:31:51 PM] : Request of trust and detection of platform is
complete.

ERROR DETAILS
Following errors were detected during this operation.
* [8/15/2008 9:31:53 PM]
System.Deployment.Application.DeploymentDownloadEx ception (Unknown subtype)
- Downloading file:///C:/Documents and
Settings/Andrew/Desktop/vdiworkflow/NPCC/NPCC/bin/Release/app.publish/Application Files/NPCC_5_0_2_8/NPCC.XmlSerializers.dll.deploy did not succeed.
- Source: System.Deployment
- Stack trace:
at
System.Deployment.Application.SystemNetDownloader. DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader. DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Downl oad(SubscriptionState
subState)
at
System.Deployment.Application.DownloadManager.Down loadDependencies(SubscriptionState
subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri
sourceUriBase, String targetDirectory, String group, IDownloadNotification
notification, DownloadOptions options)
at
System.Deployment.Application.ApplicationActivator .DownloadApplication(SubscriptionState
subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory&
downloadTemp)
at
System.Deployment.Application.ApplicationActivator .InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at
System.Deployment.Application.ApplicationActivator .PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String&
errorPageUrl)
at
System.Deployment.Application.ApplicationActivator .ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Net.WebException
- Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .
- Source: System
- Stack trace:
at System.Net.FileWebRequest.EndGetResponse(IAsyncRes ult asyncResult)
at System.Net.FileWebRequest.GetResponse()
at
System.Deployment.Application.SystemNetDownloader. DownloadSingleFile(DownloadQueueItem next)
--- Inner Exception ---
System.Net.WebException
- Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .
- Source: System
- Stack trace:
at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri,
FileAccess access, Boolean asyncHint)
at System.Net.FileWebRequest.GetResponseCallback(Obje ct state)
--- Inner Exception ---
System.IO.FileNotFoundException
- Could not find file 'C:\Documents and
Settings\Andrew\Desktop\vdiworkflow\NPCC\NPCC\bin\ Release\app.publish\Application Files\NPCC_5_0_2_8\NPCC.XmlSerializers.dll.deploy' .
- Source: mscorlib
- Stack trace:
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess
access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize,
FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean
bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess
access, FileShare share, Int32 bufferSize, FileOptions options, String
msgPath, Boolean bFromProxy)
at System.Net.FileWebStream..ctor(FileWebRequest request, String path,
FileMode mode, FileAccess access, FileShare sharing, Int32 length, Boolean
async)
at System.Net.FileWebResponse..ctor(FileWebRequest request, Uri uri,
FileAccess access, Boolean asyncHint)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

[kevin.morrison]

I am having the exact same issue. My clickonce app had never failed to
deploy. Now since I installed VS2008 SP1 I can no longer publish my
app. XmlSerializers.dll.deploy is missing and I can't figure out how
to get it back!

Kevin

On Aug 15, 10:33*pm, Andrew_d123
<[e-mail]:

Here is my problem. *I have an app that has over 9 web services. *Foryears I
had not issues with clickonce but now it looks like the build is missing
XmlSerializers.dll.deploy. *I did have this issue once in vs 2005 and one the
problem just went away. *Well now its back. *If I build the app 20 times it
may work once. *I did find that if I remove this as a required dll thatI can
get my program to run. *I can't seem to find any info about this problem. *I
did try to rebuild my program on two different computers. *I am using vs 2008
sp1. *My program is using 2.0 framework but the error happen even on 3.5. *
One thing I found makes the build run is doing big changes like adding a new
from or Changing the frame work. *But this will only work for one build..

[kevin.morrison]

Ok, the fix for me was to go to the publish tab in the project
properties, click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status. My app still
works, so I guess it isn't needed in this case.

On Aug 18, 8:37*am, [e-mail] wrote:

I am having the exact same issue. My clickonce app had never failed to
deploy. *Now since I installed VS2008 SP1 I can no longer publish my
app. *XmlSerializers.dll.deploy is missing and I can't figure out how
to get it back!

Kevin

On Aug 15, 10:33*pm, Andrew_d123

<[e-mail]:

Here is my problem. *I have an app that has over 9 web services. *For years I
had not issues with clickonce but now it looks like the build is missing
XmlSerializers.dll.deploy. *I did have this issue once in vs 2005 andone the
problem just went away. *Well now its back. *If I build the app 20 times it
may work once. *I did find that if I remove this as a required dll that I can
get my program to run. *I can't seem to find any info about this problem. *I
did try to rebuild my program on two different computers. *I am usingvs 2008
sp1. *My program is using 2.0 framework but the error happen even on 3.5. *
One thing I found makes the build run is doing big changes like adding a new
from or Changing the frame work. *But this will only work for one build.- Hide quoted text -

- Show quoted text -

[=?Utf-8?B?TWFzdGVyUmFuZ2Vy?=]

"ke************@gmail.com" wrote:

Ok, the fix for me was to go to the publish tab in the project
properties, click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status. My app still
works, so I guess it isn't needed in this case.

Had same issue. Same solution. What's happening? I didn't even put that in
my project. Why the frak is it showing up now?

[=?Utf-8?B?QW5kcmV3X2QxMjM=?=]

OK,
I spent many hours 30+ on the internet. Here is what I found as a fix.
I found that if you turn generate serialization assembly to off and not auto
is the fix. This way the XmlSerializers.dll.deploy is not even part of your
app.

The issue is when you use web services that uses WSE. Looks like there is
a know issue but dont google XmlSerializers.dll.deploy but google generate
serialization assembly. At this point I am very scared to even publish
anything. You got to love clickonce and you got to hate it.
Andrew
click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status

"MasterRanger" wrote:

>

"ke************@gmail.com" wrote:

Ok, the fix for me was to go to the publish tab in the project
properties, click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status. My app still
works, so I guess it isn't needed in this case.

Had same issue. Same solution. What's happening? I didn't even put that in
my project. Why the frak is it showing up now?

[=?Utf-8?B?SlZK?=]

I had the same issue and the same solution. But this problem occured only
today. I deployed this app hundreds of times and everything was ok. Moreover
I didn't change anything in VS or so. So I didn't understand from where this
problem came.

"Andrew_d123" wrote:

OK,
I spent many hours 30+ on the internet. Here is what I found as a fix.
I found that if you turn generate serialization assembly to off and not auto
is the fix. This way the XmlSerializers.dll.deploy is not even part of your
app.

The issue is when you use web services that uses WSE. Looks like there is
a know issue but dont google XmlSerializers.dll.deploy but google generate
serialization assembly. At this point I am very scared to even publish
anything. You got to love clickonce and you got to hate it.
Andrew
click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status

"MasterRanger" wrote:

"ke************@gmail.com" wrote:

Ok, the fix for me was to go to the publish tab in the project
properties, click the Application Files button and set the
XmlSerializers.dll to "exclude" under Publish Status. My app still
works, so I guess it isn't needed in this case.
>

Had same issue. Same solution. What's happening? I didn't even put that in
my project. Why the frak is it showing up now?

[=?Utf-8?B?SlZK?=]

Sorry, actually I did installed VS2008 SP1. So probably because of that.