|
Posted by rgalgon on February 23, 2007, 2:50 pm
Please log in for more thread options
show/hide quoted text
> This just started occuring today.
> I started a new WM5.0 project and when I go todeployit to the device
> it starts deploying every single reference to the project folder. (its
> a C# smartphone application).
> System.configuration
> System.xml
> System.security
> etc.
> etc.
> It of course runs out of memory after the first few dlls are deployed.
> I've never seen VS2005 do this for any of my other Windows Mobile
> projects.
> Any ideas as to why this is happening or how to stop it?
> I've compared my configuration files to my other WM projects and they
> look very similar.
I initially found a 'fix' for this because some of the reference's
property "Copy Local" was set to true. Things worked fine for some
time until, randomly, it started up again today trying to deploy ever
single reference as a dll to the device, but everything's Copy Local
is set to false this time.
Any ideas?
| 
XML Sitemap
> I started a new WM5.0 project and when I go todeployit to the device
> it starts deploying every single reference to the project folder. (its
> a C# smartphone application).
> System.configuration
> System.xml
> System.security
> etc.
> etc.
> It of course runs out of memory after the first few dlls are deployed.
> I've never seen VS2005 do this for any of my other Windows Mobile
> projects.
> Any ideas as to why this is happening or how to stop it?
> I've compared my configuration files to my other WM projects and they
> look very similar.