prior to VS 2010, we used Wed Deployment Project to get the website ready to copy out. We liked it because it allowed for us to do a "Merge Each individual folder output to its own assembly". We did this because when we made a change, we could just copy out that folders dll, the file was easy to find and we didn't have to redploy the entire web site. Now we've upgraded our site to VS 2010. I installed the beta for Web Deployment Project and have tried to build a website. The file structure in the bin is what we would expect as it looks like it did in prior versions however when we go to run our website some of the pages don't come up. We get a
Could not load type 'Pages_FIT_ApplicantList' from assembly 'Pages.FIT, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because the method 'Page_Load' has no implementation (no RVA).
However, if i publish the site using VS 2010 feature... the page comes up correctly.. makes me lean towards a problem with the Web Deploymnet Project build. When i publish using VS 2010 i see that i can tell it to create for each page.. but that sure creates a lot of dll's.. is there a way to do just the folders and the nice naming convention that they used to use.
The VS was created as a website, not a web application. It was added to a blank solution.
At any rate, would appreciate some guidence.
Thanks