Or worse, couldn't change it because that would break backwards compatibility with some arcane plugin....
Lesson learned, don't use the design view for webforms... -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Paul Cowan Sent: Friday, November 24, 2006 15:38 To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] has there been a service pack for .net 2.0? I have been developing from interdev to the present VS2005 on web apps. I never use the design view for HTML. I suspect the same people have consistently got it wrong over the years. It is a complete [EMAIL PROTECTED] > Date: Fri, 24 Nov 2006 09:09:52 -0500> From: [EMAIL PROTECTED]> Subject: Re: [ADVANCED-DOTNET] has there been a service pack for .net 2.0?> To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM> > Ditto on the comments regarding the quality of Visual Studio 2005.> Although, I do agree it's the first Visual Studio .NET approaches being> functional.> > I feel there many fundamental defects and fundamental design flaws (some> contrary to Microsoft's Patterns and Practices that *it* pushes) in Visual> Studio that need to be addressed.> > There's many designer issues logged on> http://connect.microsoft.com/visualstudio/feedback. Some are feature> requests (like support for forms/controls using generics or abstract base> classes) but hardly any seem to be of any importance to anyone other than> the person that logged it. If the issues that have been raised in this> thread are important to anyone reading it they should make their voice> heard on the feedback site by voting for these issues. Searching for the> words "forms designer" shows a very large list of issues (some> suggestions, some bugs) but the only issues that have more than a couple> of votes seem only to be feature requests (again, abstracts and generics> in the forms designer). From Microsoft's point of view the community is> saying most of the issues described in this thread aren't important.> > The issue of performance toggling between code/design views is a big issue> that the Visual Studio team is working on--it's one of the only bugs that> has garnered a lot of votes (49 at last count). If you find or know of an> issue on Connect you feel is important (or was raised in this thread),> post the URL here (or the WinForms list if it's a WinForms designer issue)> with a description so everyone else can vote on it--if it's important to> them. It's clear that Microsoft is working on the bugs that the community> has said are important on Connect. After that, they're working on the> bugs they feel have a priority.> > Discussing bugs in Visual Studio on these lists may get you advice on a> workaround and allow you to blow off steam; but it won't get the bug fixed.> > ===================================> This list is hosted by DevelopMentor(r) http://www.develop.com> > View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor(r) http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
