RajL

Hi,

I have a project that does not deploy to WM 6 Pro Emulator with a disk full error:

Error 2 Deployment and/or registration failed with error: 0x8973190e. Error writing file '%csidl_program_files%\helloapplication\system.web.dll'. Error 0x80070070: There is not enough space on the disk.
Device Connectivity Component

I have 94GB of free space on the only drive. The same project deploys properly on my colleague's machine! I have Vista Home Premium whereas the colleague has Vista Business.

A lot of DLLs are copied during the deployment which are not copied for other projects. The list from output window is shown below.

Is there a size of the Emulator that can be set so as to allow copying

2. When I compile the project, I see a warning:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3247: Found conflicts between different versions of the same dependent assembly.

Doesn't give a name of the conflicting assembly! Any ideas where to look

Thx and Regards,

- Raj

------------- Files copied ---------------

Deploying 'C:\Windows\assembly\GAC_MSIL\System.DirectoryServices.Protocols\2.0.0.0__b03f5f7f11d50a3a\System.DirectoryServices.Protocols.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.OLE.Interop\7.1.40304.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.OLE.Interop.dll'
Deploying 'C:\Windows\assembly\GAC_32\VJSharpCodeProvider\2.0.0.0__b03f5f7f11d50a3a\VJSharpCodeProvider.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.MSXML\8.0.0.0__b03f5f7f11d50a3a\Microsoft.MSXML.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.CompactFramework.Build.Tasks\8.0.0.0__b03f5f7f11d50a3a\Microsoft.CompactFramework.Build.Tasks.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.Build.Framework\2.0.0.0__b03f5f7f11d50a3a\Microsoft.Build.Framework.dll'
Deploying 'C:\Windows\assembly\GAC\VsWebSite.Interop\8.0.0.0__b03f5f7f11d50a3a\VsWebSite.Interop.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.WizardFramework\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.WizardFramework.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.DeviceConnectivity.Interop\1.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.DeviceConnectivity.Interop.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.TextManager.Interop.8.0\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.TextManager.Interop.8.0.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\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.dll'
Deploying 'C:\Windows\assembly\GAC\EnvDTE\8.0.0.0__b03f5f7f11d50a3a\EnvDTE.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.Shell.Interop.8.0\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Shell.Interop.8.0.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.Runtime.Remoting\2.0.0.0__b77a5c561934e089\System.Runtime.Remoting.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\Microsoft.VisualStudio.Shell.Interop\7.1.40304.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Shell.Interop.dll'
Deploying 'C:\Windows\assembly\GAC_32\mscorcfg\2.0.0.0__b03f5f7f11d50a3a\mscorcfg.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.VSHelp\7.0.3300.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.VSHelp.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.Vsa\8.0.0.0__b03f5f7f11d50a3a\Microsoft.Vsa.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.TemplateWizardInterface\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.TemplateWizardInterface.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Editors\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Editors.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.Drawing.Design\2.0.0.0__b03f5f7f11d50a3a\System.Drawing.Design.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Shell\2.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Shell.dll'
Deploying 'C:\Windows\assembly\GAC\VSLangProj80\8.0.0.0__b03f5f7f11d50a3a\VSLangProj80.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.Build.Tasks\2.0.0.0__b03f5f7f11d50a3a\Microsoft.Build.Tasks.dll'
Deploying 'C:\Windows\assembly\GAC\stdole\7.0.3300.0__b03f5f7f11d50a3a\stdole.dll'
Deploying 'C:\Windows\assembly\GAC_32\System.Data\2.0.0.0__b77a5c561934e089\System.Data.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\System.Design\2.0.0.0__b03f5f7f11d50a3a\System.Design.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.ManagedInterfaces\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.ManagedInterfaces.dll'
Deploying 'C:\Windows\assembly\GAC\VSLangProj\7.0.3300.0__b03f5f7f11d50a3a\VSLangProj.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualBasic\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualBasic.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\System.Management\2.0.0.0__b03f5f7f11d50a3a\System.Management.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.Shell.Design\2.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Shell.Design.dll'
Deploying 'C:\Windows\assembly\GAC\VSLangProj2\7.0.5000.0__b03f5f7f11d50a3a\VSLangProj2.dll'
Deploying 'C:\Windows\assembly\GAC\EnvDTE80\8.0.0.0__b03f5f7f11d50a3a\EnvDTE80.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\System.Security\2.0.0.0__b03f5f7f11d50a3a\System.Security.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\Microsoft.VisualStudio.ProjectAggregator\8.0.0.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.ProjectAggregator.dll'
Deploying 'C:\Windows\assembly\GAC_MSIL\System.Deployment\2.0.0.0__b03f5f7f11d50a3a\System.Deployment.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.TextManager.Interop\7.1.40304.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.TextManager.Interop.dll'
Deploying 'C:\Windows\assembly\GAC_32\System.Data.OracleClient\2.0.0.0__b77a5c561934e089\System.Data.OracleClient.dll'
Deploying 'C:\Windows\assembly\GAC\Microsoft.VisualStudio.Debugger.Interop\8.0.1.0__b03f5f7f11d50a3a\Microsoft.VisualStudio.Debugger.Interop.dll'
Deployment and/or registration failed with error: 0x8973190e. Error writing file '%csidl_program_files%\helloapplication\system.web.dll'. Error 0x80070070: There is not enough space on the disk.
========== Build: 1 succeeded or up-to-date, 0 failed, 1 skipped ==========
========== Deploy: 0 succeeded, 1 failed, 0 skipped ==========



Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

Christopher Fairbairn

Hi Raj,

The error message is not stating that your desktop PC is running out of space, but the emulated Windows Mobile device is running out of storage space as the files are being deployed. You should be able to confirm this by going into the Memory control panel applet on the emulator and viewing how much space is left in the column titled "Storage".

Having a look at your log file you copy and pasted I am concerned about the DLLs being downloaded. There appears to be a signficiant number of desktop specific assemblies being downloaded to the device.

I would look at your project's references and see if you have included any assemblies compiled against the desktop version of the .NET framework within your smart device project. Visual Studio definatly shouldn't be attempting to deploy most of the assemblies listed in the log (for example System.Data.OracleClient, System.Runtime.Remoting, Microsoft.Build.Tasks, EnvDTE80 et al, there is no way these files will operate on the PDA).

Can you explain the structure of your project, and what references you have to additional assemblies

This is possibly the cause of the first warning message you mentioned. Typically this warning message is alerting you to the fact that via references and included assemblies your code refers to two different versions of the same assembly. Typically this is caused by including code which is compiled against a desktop assembly into a Smart Device project (since there will be two different versions of System.dll etc etc).

Hope this helps,

Christopher Fairbairn






Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

RajL

Thanks Christopher. I have the following references. All, but OrientationAware dlls, are from WindowsCE with CopyLocal false, whereas OrientationAware dlls are CopyLocal true. The problem exhibits even if I deploy on other emulators, including WM 5 Pocket PC. Note that the same project deploys properly on my colleague's machine, which is more confusing...

Microsoft.Practices.Mobile.UI.OrientationAware

Microsoft.Practices.Mobile.UI.OrientationAware.Designer

Microsoft.WindowsCE.Forms

mscorlib

System

System.Data

System.Data.SqlServerCe

System.Drawing

System.Messaging

System.Windows.Forms

System.Windows.Forms.DataGrid

System.Xml

Thanks and Regards,

- Raj





Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

Ilya Tumanov

You can as well have 94 terabytes free on your PC - that does not matter because emulator has no access to it. Increasing emulator¡¯s memory is possible but that is not going to fix the issue.

The problem here is what you have a reference, directly or indirectly, to one or more desktop assembly in your project so VS tries to deploy all the desktop DLLs. That is not allowed and makes your project invalid. Even if you increase the storage your application won¡¯t run. You have to find incorrect references and remove them. That probably would take care of the warning as well. See this on how to determine incorrect reference.






Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

Christopher Fairbairn

Hi Raj,

I have a feeling your problem may be due to the reference you have included to Microsoft.Practices.Mobile.UI.OrientationAware.Designer within your Smart Device project. Have you tried removing this reference from your smart device project, and seeing if it avoids deploying the Visual Studio related assemblies

I have not utilised the Orientation Aware controls yet, but from it's naming convention I have a feeling that the Designer assembly will be intended for use on the desktop and that could explain why you are getting dependicies on the desktop assemblies when you include it within the project intended for the PDA.

Could you try removing this assembly from your references, recompile your project and see if a deployment stops deploying those additional assemblies

Hope this helps,

Christopher Fairbairn






Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

RajL

Thanks Ilya. It turned out that OrientationAware control that was included was the culprit. We used another OrientationAware control and it is able to deploy without any errors.

Is there an official version of OrientationAware that Microsoft offers

Thx and Regards,

- Raj





Re: .NET Compact Framework Solution can't be deployed to WM 6 Pro Emulator

Ilya Tumanov

First of all, your 94 GB of free space have nothing to do with amount of free space on emulator. Some developers believe an emulator uses PC's file system by mapping all files directly but that is not the case. File system is also emulated. I believe by default it has about 60 MB free.

Now, the issue here is not the free space but the fact what your application uses one or more assembly compiled for desktop. That automatically makes it invalid and causes VS to deploy desktop framework assemblies which of course won't work even if you do have enough space. You should find and remove all assemblies compiled for desktop to fix the issue.

Now, common reason to add such a reference in a first place is an attempt to use some functionality in that assembly. E.g. "But I can't remove it, need Oracle client/Speech Recognition/3D modeling library¡± and so on. Sorry, but these assemblies are not going to work even if you really need them to. You have to remove them and find another way to do what needs to be done. Say, get a device compatible version, remove that functionality or implement it yourself.