Deploying to Windows Mobile 5.0

  • Thread starter Thread starter Rick
  • Start date Start date
R

Rick

This seems to take a really long time. Looking at what is being
deployed, some of it doesn't make sense to me:

Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Drawing.Design\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.Design.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.ServiceProcess\2.0.0.0__b03f5f7f11d50a3a\System.ServiceProcess.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Data.SqlXml\2.0.0.0__b77a5c561934e089\System.Data.SqlXml.dll'
Deploying
'C:\WINDOWS\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\Microsoft.VisualC\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualC.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.Configuration\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Drawing\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Windows.Forms\2.0.0.0__b77a5c561934e089\System.Windows.Forms.dll'
Deploying
'C:\WINDOWS\assembly\GAC_32\System.Web\2.0.0.0__b03f5f7f11d50a3a\System.Web.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Design\2.0.0.0__b03f5f7f11d50a3a\System.Design.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Web.Services\2.0.0.0__b03f5f7f11d50a3a\System.Web.Services.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices.Protocols\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.Protocols.dll'
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_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Web.RegularExpressions\2.0.0.0__b03f5f7f11d50a3a\System.Web.RegularExpressions.dll'
Deploying
'C:\WINDOWS\assembly\GAC_32\System.Transactions\2.0.0.0__b77a5c561934e089\System.Transactions.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\Accessibility\2.0.0.0__b03f5f7f11d50a3a\Accessibility.dll'
Deploying
'C:\WINDOWS\assembly\GAC_32\System.Data.OracleClient\2.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System\2.0.0.0__b77a5c561934e089\System.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Runtime.Remoting\2.0.0.0__b77a5c561934e089\System.Runtime.Remoting.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.Xml\2.0.0.0__b77a5c561934e089\System.Xml.dll'
Deploying
'C:\WINDOWS\assembly\GAC_MSIL\System.DirectoryServices\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.dll'
Deploying 'C:\Projects\Pocket
Menus\UtilityClasses\bin\Debug\UtilityClasses.dll'
Deploying 'C:\Program Files\NCover\NCover.Framework.dll'
Deploying
'C:\Projects\SqlCeHelper\Microsoft.ApplicationBlocks.Data\bin\Microsoft.ApplicationBlocks.Data.dll'
Deploying 'C:\Projects\Pocket Menus\MenuClasses\bin\MenuClasses.dll'
Deploying 'C:\Projects\Pocket Menus\Data\bin\Data.dll'
Deploying 'C:\Projects\Pocket Menus\Menu Calculator\bin\Menu
Calculator.exe'
Deploying 'C:\Program
Files\Microsoft.NET\SDK\CompactFramework\v2.0\windowsce\diagnostics\System_SR_enu_wm.cab'

What is wrong with this picture? Like, where is
System.DirectoryServices.dll coming from? or System.Data.OracleClient?
(The ApplicationBlocks.Data piece is a compact framework version I've
adapted to 2.0)

I'm then getting an out of memory error on loading a 32 x 32 icon from
an assembly resource. But there seems to be plenty of memory looking at
the device itself! Anyone?
 
Thanks! Good call. One the one hand, it's good to be able to build a full
framework based test project in the same solution as a CF project, and run
NUnit tests against some of the classes. On the other hand, the environment
can be just a hair too permissive at times...
 
If it's not too permissive we blame the team for closing doors and if they
aren't we blame them for letting us shoot ourselves in the foot. However, in
this case I agree that there should be at least a more visible warning.

Cheers
Daniel
 
Back
Top