Last post Mar 30, 2006 09:04 PM by omar_k
Mar 29, 2006 04:01 AM|RyanJ19|LINK
I was wondering if there are any advantages to the web application project model, other than easier conversion to VS 2005? Are any pros and cons (like should I continue to use it for new projects or would I be better off using
web projects for new ASP.NET applications)?
I am also having a problem with licensing a 3rd party control. I have a couple that I use, but I am only having a licensing issue with one of them. The company is telling me to use the "build runtime licenses" context menu in
VS2005, but since that does not exist for web application projects, of course that is not an option. And when I tell them I am using the web application project, it doesn't seem like they want to support me on it because web application projects are in beta...
I realize web application projects automatically compile control licenses into your project assembly on the build of the project (like VS2003), but I am not sure how to troubleshoot it when it is not working.
Mar 30, 2006 09:04 PM|omar_k|LINK
Can you reply with the name/company of the specific control that is not working for license generation? As you mention, the model works very similar to VS2003, so it is unexpected that the license isn't being generated.
As for advantages to using WAP instead of "Websites", the primary ones are:
- easier conversion from VS2003
- ability for stand-alone class files to more easily reference code-behind classes for pages.
- if you want to sub-divide a single ASP.NET application into multiple VS projects, WAP allows you to do that.
- full support for MSBuild
- finally full site build times are significantly faster in WAP than in Websites.
The advantages that Websites provide are:
- no project file needed, folder defines project contents (some web developers prefer this loser project definition)
- no full build required to test changes made to pages. You can simply make edits and hit refresh in the browser to see the results.
- if you prefer doing code inline, rather than in a code-behind file, Websites are probably a better choice.
- entire website does not need to be in a compil-able state if you want to develop/debug/test individual pages. Can be helpful in team development situations.
I hope this helps in making some of your decisions. We'll look into the control licensing issue if we can get more details on the control that is giving problems.