VS2005 deploys every debug CF system dlls

  • Thread starter Thread starter Trapulo
  • Start date Start date
T

Trapulo

Hello,
I've a problem debugging a CF application with VS2005.

I've created a solution with an exe application, and two libs that this exe
referes. The application targets WinCE5.0 device, and I'm debugging it with
an axim that runs win mobile 2005 pocket pc.
When I start debugging the application, VS:
- compiles the application
- deploy EVERY TIME to Pocket (to application's folder) runtime files as:
"system.windows.forms.dll", "system.dll", "system.deployment.dll"
- deploy my application
- run and debug my application


Why this? It deploys every time every CF dll my application uses ! And it
takes a long :(
I've many other CF application with same configuration (target on CE5.0,
debug on axim) and it deploy only compiled application as it may.
I've checked on proprerties that system dlls are not referenced with "copy
local" setting, and I don't know what can be the problem.

Thanks
 
Can you copy from the output window (select build in the combo) and paste
here?

Cheers
Daniel
 
I have this SAME problem. I thought that it was re-deploying the entire Compact FW each time I tried to debug. This is making me crazy! Yesterday, I had this problem once, and I uninstalled the Compact .NET FW from the device, redeployed, and it worked. But it is back today. I do not understand this..... :(

Dave Brown

(e-mail address removed)
 
After builiding my code, I have this:

------ Deploy started: Project: XXXX, Configuration: Debug Any CPU ------

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Serialization.Formatters.Soap\2.0.0.0__b03f5f7f11d50a3a\System.Runtime.Serialization.Formatters.Soap.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\Accessibility\2.0.0.0__b03f5f7f11d50a3a\Accessibility.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Configuration.Install\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.Install.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.ServiceProcess\2.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll'

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'

then it deploys my application's exe and dlls



thank you
 
I also tried this, but nothing changed. However, I have many other projects
that deploy only rigth files, so I think this is not related to CF installed
on device, but I think it's related only to VS.

bye
 
I also tried this, but nothing changed. However, I have many other projects
that deploy only rigth files, so I think this is not related to CF
installed on device, but I think it's related only to VS.
Click to expand...

Same problem here, also unchecking the "Deploy the latest version of the
..Net CF" in the project properties.
And the worst is that if with vs2003 this deployement was relatively fast
with vs2005 it take a looooong time!

I think that the support for PPc is worst than in vs2003: debugger is slower
too, the edit & continue is not still implemented, deploying I got often
error copying files on the device, ActiveSync 4.1 sometimes has problems
connecting to windows mobile 5 evices, the choose to deploy to the right
device (PocketPC 2003 or WM5) is more difficult...

I really don't see a real advantage of the use of Fw 2.0 for smart
devices... :(
 
Thanks for posting your output.

You are using a desktop assembly somewhere from your exe or from another dll
you are referencing.

The clue is the public key token of the desktop version:
2.0.0.0__b03f5f7f11d50a3a

So Visual Studio tries to deploy the relevant desktop assemblies to the
device (a bit dumb but that's what it does). Get rid of any full framework
assemblies from your project and you'll be fine.

Cheers
Daniel
 
Daniel Moth said:
Thanks for posting your output.
Click to expand...

thank you for your assistance
You are using a desktop assembly somewhere from your exe or from another
dll you are referencing.

The clue is the public key token of the desktop version:
2.0.0.0__b03f5f7f11d50a3a

So Visual Studio tries to deploy the relevant desktop assemblies to the
device (a bit dumb but that's what it does). Get rid of any full framework
assemblies from your project and you'll be fine.
Click to expand...


You are rigth! I don't know why, but my exe was referencing
system.deployment and system.serviceprocess from standard framework.. I
removed them, and now deployment works quick!

thank you !
 
Back
Top