Lots of type 'xxxxxxx' is not defined errors when migrating web site project to web app project

[John Dalberg]

I am migrating a web site project to a web application project as indicated
at this page:
http://webproject.scottgu.com/CSharp/Migration2/Migration2.aspx

However when I try to compile, I get a lot of type 'xxxxxxxxx' is not
defined errors. It seems classes in the project are not getting compiled in
the project even when they are present in the solution explorer. When I
inspected the vbproj file, I noticed that many .vb files are in an
'include' tag instead of a 'compile' tag. So they are being included as
like static files instead of being compiled.

These .vb files reside in folders. I have added these files in different
ways: drag and drop or add existing.. The only way I can add these files
and have them compile is if add them to the root folder.

What's the way to include a folder in the project and have all the .vb
files compiled instead of just being included?

John Dalberg

 

[Cowboy \(Gregory A. Beamer\)]

For classes to be compiled automagically, in ASP.NET 2.0, they should go in
the App_Code folder. I have not tried this with a converted project, so I am
not sure if there are additional caveats. I also have only done a few test
projects with the web application model, as my production apps were started
before the project was in final form.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA

*********************************************
Think outside the box!
*********************************************