Visual Studio is not recognizing new classes

I'm using visual studio 2008 SP1, I'm working with a web pro开发者_开发问答ject in VB.NET. the problem when I add new class file (of-course in App_Code) it doesn't recognize it. all the old class files are working fine, but the new ones aren't. I restarted my computer and still the same problem.

Any Ideas

---

compare properties of working class with un recognised class. Specifically, "Build Action". It should resolve the problem.

if not let me know. :)

---

If there is a solution involved, try "rebuilding" the entire solution. Rebuilding projects and websites individually didn't do it for me - after trying other suggestions here only the project rebuild worked.

---

Make sure it is in the same namespace as the thing you are trying to call it from, or fully declare using the namespace when creating one. Perhaps also give us an example of one that works and one that doesn't.

Also, don't forget to use the proper access modifier. Start with Public to see if that fixes your problem. If that does then your classes are almost certainly in different namespaces.

---

A made a small checklist bases on answer (also what I would do)

1. Access modifier of a class must be Public or Friend. Read more here

Public Class MyClass

End Class

2. Namespace The class you are trying to access to must be either in the same namespace or Imported via the keyword Imports YourNamespace.MyFeature Read more here

3. A vb class must be set to compile in its build action. The option wont be available if your are in debug / running mode. To check this you need to: Right click on MyClass.vb -> Property -> Build Action -> Compile.

4. If these steps didn't work you could try to clean project/solution, close and reopen VS, then re-build project/solution.

Hope it help!

---

Sometimes, a simple Clean and Rebuild of the project will resolve the issue.

I was refactoring a non-object-oriented C++ code to an object-oriented one. So, I think Visual Studio was confused at that point and the solution I mentioned worked for me.

---

maybe you are trying to use internal classes from another assembly or there may be problems with the access modifiers of the class.