The various build action options

• None: The file is not included in the project output group and is not compiled in the build process. An example is a text file that contains documentation, such as a Readme file.
• Compile: The file is compiled into the build output. This setting is used for code files.
• Content: Allows you to retrieve a file (in same dir as assembly) as a stream via Application.GetContentStream( uri ). For this method to work, it needs a AssemblyAssociatedContentFile custom attribute which VS graciously adds when you mark a file as “Content”
• Embedded resource: embeds the file in an exclusive assembly manifest resource.
• Resource (wpf only): embeds the file in a shared (by all files in the assembly with similar setting) assembly manifest resource named AppName.g.resources.
• Page (wpf only): Used to compile a xaml file into baml. The baml is then embedded with the same technique as Resource (i.e. available as `AppName.g.resources)
• ApplicationDefinition (wpf only): Mark the XAML/class file that defines your application. You specify the code-behind with the x:Class=”Namespace.ClassName” and set the startup form/page with StartupUri=”Window1.xaml”
• SplashScreen (wpf only): An image that is marked as SplashScreen is shown automatically when an WPF application loads, and then fades
• DesignData: Compiles xaml viewmodels so that usercontrols can be previewed with sample data in visual studio (uses mock types)
• DesignDataWithDesignTimeCreatableTypes: Compiles xaml viewmodels so that usercontrols can be previewed with sample data in visual studio (uses actual types)
• EntityDeploy: (Entity Framework): used to deploy the Entity Framework artifacts
• CodeAnalysisDictionary: A xml file containing custom word dictionary for spelling rules

Origin : Stack Overflow

Cannot access the file make sure it exists and you have permission

Microsoft Excel cannot access the file $path to file$. There are several possible reasons:

• The file name or path does not exist.
• The file is being used by another program.
• The workbook you are trying to save has the same name as a currently open workbook.

I was receiving this error while I was implementing excel automation in a WCF service

Oddly all you have to do is create two folders, or one if you are running a 32BIT OS

64 bit

·Windows 2008 Server x64

Please make this folder.

C:\Windows\SysWOW64\config\systemprofile\Desktop

32 bit

·Windows 2008 Server x86

Please make this folder.

C:\Windows\System32\config\systemprofile\Desktop

Update This is also happening in Windows Server 2012 R2

but the usual fix didn’t work. Oddly enough another folder is required

Windows SERVER 2012 R2
C:\Windows\SysWOW64\config\systemprofile\AppData\Local\Microsoft\Windows\INetCache

So it would seem that a folder named “Desktop” is required in the systemprofile folder in order that excel automation can open files