Re: Severe Web Application Project Problems

DaveNCheez — Mon, 10 Jul 2006 13:06:35 GMT

Drawing at straws here, but make sure a component you are using is not turning off VS Intellisense.

Check to make sure the following options are checked:

Tools > Options > Text Editor > C# > General and check "Auto list members" and "Parameter information" checkboxes

This will simply turn on VS intellisense if it has been disabled by another component.

Re: Severe Web Application Project Problems

DaveNCheez — Mon, 10 Jul 2006 13:03:30 GMT

cbenard,
Alot of people seem to have problems similar to the ones you list.

http://west-wind.com/weblog/posts/6269.aspx is a blog post about such issues.

Still looking for a solution to such issues.

Dave

Severe Web Application Project Problems

cbenard — Fri, 07 Jul 2006 19:13:51 GMT

Hi. I work for a small development company and we're trying to develop a new site using the Web Application Project template. We have 4 projects inside the solution (for our different functional areas' business and data tiers) in addition to the web application project itself.

We are constantly having three main problems:

When we rebuild, it puts a [NameOfWebProject].dll and .pdb in the actual root directory of the web pages. This causes the compiler to state that classes exist in two places (the compiled CS files and the .dll). Both do actually contain the class (verified by ildasm). We have to delete the .dll and then we will be able to see the page, unless one of the other problems is preventing it. We turned off batch compilation in Web.Config in order to address this issue.
Visual Studio forgets about our classes all the time. This means intellisense stops working as well. We can close Visual Studio and reopen it and it will occasionally start working. However, in some instances, the classes will still not highlight with the right color, or they will highlight for about 1-2 seconds and then go back to white (not recognized or reserved; I use light on dark).
In partial classes, specifically the designer generated files, the properties do not work sometimes. For instance, I've added a property to my Master Page called Mode, which is an enum called MasterMode. The page that is trying to use it will say that base is system.object, not BaseForm. BaseForm inherits from System.Web.UI.Page. It seems like the designer generated files do not read the inheritance information from the rest of the partial class, in the main .cs file. I'm not sure how to make this more clear, but I would be able to answer specific followups on this.

I hope some of these issues can be addressed, because I like the idea of WAP. Right now, my coworker is in the process of converting it to a single project so we can try that, and barring that, we'll have to resort to doing it without doing a web application project.

Thanks in advance.

VS 2005 Web Application Projects

Re: Severe Web Application Project Problems

Re: Severe Web Application Project Problems

Severe Web Application Project Problems