Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Apr 17, 2006 08:37 PM by mbund
Apr 10, 2006 06:03 PM|LINK
First of all, thank you for the great addition to the VS2005 - the WAP.
I have upgraded my ASP.NET application from 2003 to the 2005 Web Application Projects version. But I cannot get my project to run in the new environment, here are the questions/issues/comments that I have:
Thank you very much.
Apr 10, 2006 07:34 PM|LINK
1. System.DirectoryServices -- that seems odd. I'll try to repro.
2. Rebuild Project -- I cannot recreate that behavior.
I did a simple test where I copied an assembly into the bin folder, then made a change in my WAP project so it's assemblies would be re-built. The copied assembly was not deleted.
3. No, webform .resx files are not required.
You should confirm there is no date worth saving in them, make a backup (always!) then delete them.
Apr 17, 2006 08:18 PM|LINK
Thank you for your reply...
I had to swet some more to finally find the source of the problem!
What was happenning is that prior to convertion to WAP2005, I had all of my classes stored in the "app_code" folder.
When I renamed the folder "app_code" to "app_code1" and built the project again, the application started working immediately and flawlessly.
One more comment: I love the new configuration window in WAP where I can choose the web development server vs IIS and have the option of omitting the
virtual directory. I wish the same could be done to the Web Site Projects because as of now you do not have a choice to run the website like this:
Thank you again for making our live easier with great products...
Apr 17, 2006 08:37 PM|LINK
Thanks for the feedback. We are considering the change to allow using the root folder for WSP (a lot of users like this in WAP).
Sorry I did not catch the App_Code issue. When you said you converted from VS03 to WAP, I assumed you would not have an App_Code folder.
As part of the migration from WSP to WAP, we rename the App_Code folder to Old_App_Code. The reason has to do with the compilation differences between the two models. In WAP, all standalone class files, including those in the
App_Code folder, are pre-compiled into a single assembly and placed in the bin folder. When you publish your web app, the bin folder is copied to the server too.
On the server, requests to a aspx/ascx page will cause the asp.net to compile that page and link it to the pre-compiled binary. But because this is asp.net 2.0, if it finds a special folder like App_Code it will also compile
it. As a result you will have two classes with the same name being referenced in your web app.
When you manually renamed your App_Code folder, you resolved this issue.
Hope that makes sense...