VS 2005 still not ready for prime time

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

After being able to use the new Web Application addon to VS 2005 I thought
that I could finally use the product. However, I am still stumbling over
everthing trying to get my web application to compile and run properly. The
real annoying feature is when you try to switch to the Design View and there
is a mismatched tag you must correct that before it lets you look at the web
design. Why? The program ran ok before. The other thing is that the system
cannot handle 2 sets of form tags in a web page. It always says that last
form tag is unmatched which is not true. I delete the tag and then try to
execute the web page and it tells me that I have an unmatched form tag. You
can't win. As far as I am concerned VS 2005 is still a step backward unless
someone can explain to me why I am wrong in my above observations. There are
too many bugs for it to be useful at this point.
 
Hi there,

Just want to share my experience. I got the same prob before.
But in my situation, the prob only happens when I designed your layout with
another HTML designer (i.e: Dreamweaver or FrontPage) and then reload the
generated page(s) in VS2005 designer. They will scrambled and pops up
several 'mismatch tags' error, and not letting you to switch to design view
anymore untill all those errors resolved.
From that moment on, I always use the VS2005 designer. Should I need to
design a complex layout using, say, DreamWeaver (yes, IMO, DreamWeaver
easier to work around this), then I should be ready to spend times to clean
up all those 'mess', so VS2005 won't complain about the tags.
So, if your situation is just like mine, then stick with the VS2005
designer.

regards,
 
Mike;
I do use the VS2005 Designer only. In fact, I code many of my webpages
manually with html code. I never use Frontpage or Dreamweaver because they
are too restrictive and cumbersome to use and create unpredictable results.
My biggest complaint is that VS2005 is making me go back and recode 100's of
webpages that were displaying properly before. And I still maintain that it
does not handle nested FORM tags which I use occassionally. So I have no
choice but to recode many of my webpages in order to use VS2005 in order to
make them look like they did in VS2003. This is progress?
Dave
 
I forgot to mention that VS 2005 should make it an option whether or not to
tighten up the tag editing on webpages. If the tag sytnax was accepted by
VS2003 but not VS2005 it forces an awful lot of reprogramming on large
websites. Changing the rules in the middle of the game goes against upward
compatibility of software.
Dave
 
The handling of only one server form tag is an ASP.NET feature and has
nothing to do with VS.

In my experience, besides the Visual Foxpro IDE, Microsoft has not made an
IDE that is usable until VS 2005. In the past for .NET, I would use text
editors. Overall, however, I do not want to rely on the IDE to ensure that
my code is working. I'm the programmer, not the IDE.
 
Back
Top