Problem with deployment of config file

  • Thread starter Thread starter Miroslaw Praglowski
  • Start date Start date
M

Miroslaw Praglowski

I have a Smart Device application with app.config file. Everything
works ok (I'm using OpenNET.CF SDF 2.0 to read configuration) except
one thing - when I deploy my project on emulator (or device) using
Visual Studio 2005 config file is not deployed. Also localized
resources for assembly referenced in my project are not deployed. Is
there any way to force VS to deploy this items ?
 
Make sure that the files you want to deploy are part of the project.
Select the file in the solution explorer and make sure that the property
"Copy to Output Directory" is set to "Copy if Newer" or "Copy Always".
 
But if you set "Copy to Output Directory" property of App.config file
to "Copy if Newer" or "Copy Always" Visual Studio will copy it to bin
folder as App.config and deploy with the same name. When "Copy to
Output Directory" property is set to "Do not copy" VS copies it to bin
folder with name <ApplicationName>.exe.config but does not deploy it on
device (or emulator).

The question is how to force VS to deploy <ApplicationName>.exe.config
?
 
And second issue: what with localized resources ?

In my application I have referenced class library project
(Localization.dll) - this project contains localizer resources in
seweral languages.

When I build mobile application I have this files in bin folder:
Localization.dll
pl-PL\Localization.resources.dll

But only Localization.dll is deployed on device by Visual Studio. Why ?
 
And second issue: what with localized resources ?

In my application I have referenced class library project
(Localization.dll) - this project contains localizer resources in
seweral languages.

When I build mobile application I have this files in bin folder:
Localization.dll
pl-PL\Localization.resources.dll

But only Localization.dll is deployed on device by Visual Studio. Why ?
 
Back
Top