Can I debugg Application on device w/o copying referrences ?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

We debug a VB.Net App that uses compact framework to a DAP Windows CE.Net
device.

When I debug I would like to only have the EXE copied down. Right now it
copies any referrences as well and checks the .NET CF version.

The first message I receive is:
Files in the package 'netcf.all.wce4.armv4.cab' are more recent on the
device than on the development computer. Consider upgrading to the latest
version. Files affected are:

This is not true as the .cab file on my dev box is version 1.0 SP3 and it is
the same version installed on the device.

Then it copys over all the Dll's of the referrences that we have. We use a
few 3rd party dlls

example:
Copying files from 'C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\Windows CE\' to '\Program Files\TI_VRT_CE'
Copying Xceed.Compression.Formats.dll
Copying Xceed.Zip.dll
Copying nsoftware.IPWorksZipCF.dll

I would like to stop these from copying. For content files you can chage the
Build Type to None and it wont copy. But referrences do not have that. There
is a property called "Copy Local" but it seems to do nothing when deploying.

Anyone have any ideas ?
 
This is not true as the .cab file on my dev box is version 1.0 SP3 and it
is
Click to expand...
Ignore the message it is harmless. VS picks the RTM cab (your SP3
installation has nothing to do with that)
I would like to stop these from copying. For content files you can change
the
Click to expand...
Why? Your application will not work then (since your code that uses them
will not find anything to call) and you'll likely get a TypeLoadException.
is a property called "Copy Local" but it seems to do nothing when
deploying.
Click to expand...
This is irrelevant to deployment as you found out. It control whether the
assembly you are referencing is copied to your bin folder or not.

Cheers
Daniel
 
This is not true as the .cab file on my dev box is version 1.0 SP3 and it
Ignore the message it is harmless. VS picks the RTM cab (your SP3
installation has nothing to do with that)
Click to expand...

I realize its harmless, I would just to stop it from checking.
Why? Your application will not work then (since your code that uses them
will not find anything to call) and you'll likely get a TypeLoadException.
Click to expand...

It takes abotut 30 seconds to start a debug session on the device accross
the network.
Thats the reason I would like to stop it from copying those files every
time. I dont need the Dll's to go down on each Debug session. They stay on
the device and its unneccesary to copy them down all the time.

Thanks for the comments.

Dan
 
Back
Top