Error "A namespace does not directly contain members such as fields or methods"

visual-studio namespaces buildaction
BoltBait picture BoltBait · Jan 19, 2010 · Viewed 56.3k times · Source

I'm trying to build my C# project and I'm getting the error message "A namespace does not directly contain members such as fields or methods". It is flagging the first character (the less than symbol) of the app.config file.

I've checked all of my files for places where there are variables or functions directly inside of a namespace--found nothing. The app.config looks fine.

Google is failing me and I'm pulling my hair out. What could be causing this error?

Answer

BoltBait picture BoltBait · Jan 19, 2010

Figures! As soon as I finally break down and ask the question that I find the answer...

The app.config file properties section (somehow) listed the Build Action of "Compile" when it should be set to "None".

How in the world did it get changed? I know I didn't change it. Grrr...

Oh well, at least it's building now. Hopefully someone else will benefit from my hairloss.

Related questions

Getting "type or namespace name could not be found" but everything seems ok?

I'm getting a: type or namespace name could not be found error for a C# WPF app in VS2010. This area of code was compiling fine, but suddenly I'm getting this error. I've tried removing the Project Reference and the …

Read More
The type or namespace name 'Practices' does not exist in the namespace 'Microsoft'

I am using Microsoft Visual Studio 2005 for c# I have the following namespace on my code using Microsoft.Practices.EnterpriseLibrary; using Microsoft.Practices.EnterpriseLibrary.AppSettings; using Microsoft.Practices.EnterpriseLibrary.Data; and I keep on getting this error: -The type or …

Read More
Should I stop fighting Visual Studio's default namespace naming convention?

I'm working on an MVVM project, so I have folders in my project like Models, ViewModels, Windows, etc. Whenever I create a new class, Visual Studio automatically adds the folder name to the namespace designation instead of just keeping the …

Read More