 | |
Re: Nevermind
Visual Studio.net (General) microsoft.public.vsnet.general
 |
| | Thread Tools | Search this Thread | Display Modes |
#1
 
| |||
| |||
|
Re: Nevermind -
06-30-2003
, 01:57 PM
|
Right no. I'm sure there is a solution out there but what a pain in the rear to waste a bunch of time fooling around with this crud rather then being productive and programming. Suxs. CS "Eric" <buffm3driver (AT) verizon (DOT) net> wrote in message news:u9SGkngNDHA.1204 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Nevermind... after working it in all day, it did it again, thus leaving me to the conclusion that Visual Studio 2003 stinks and I will forever kick myself for upgrading to software that is, at best, beta. Maybe someday Microsoft will release a service pack with a new feature called "Make VS 2003 act like VS 2002" and then it would actually work. Oh well. "Mark Stemmler" <mark.stemmler (AT) sycamorenet (DOT) com> wrote in message news:exBISPdNDHA.1184 (AT) TK2MSFTNGP11 (DOT) phx.gbl... Makes sense in a twisted way since Projects and Solution files are supposed to be the only things that change going from VS2002 to VS2003. I've avoided the problems by not having the designer and code window for the same form open at the same time. That is annoying since I didn't much care about what was open when working in VS2002. I've gotten used to it though. I may try your solution. "Eric" <buffm3driver (AT) verizon (DOT) net> wrote in message news:%23KPpUEdNDHA.2052 (AT) TK2MSFTNGP11 (DOT) phx.gbl... I *think* I found a fix. I was thinking it was the project itself that was for some reason causing the problem. Maybe the conversion from VS 2002 to VS 2003 screwed things up. So I renamed my screwed up project and created a new project. I added the other projects I was using and readded all references. Then, in Windows Explorer, I copied all of the files that were in the one UI project that I was having the problems in to the new solution that did not have any forms in it yet. Then, with the new blank solution open, I drag and dropped the files into the solution explorer from Windows Explorer. I had to redo some references and it probably took about 20 minutes to tweak things but I have yet to have this problem, whereas in the old project it would happen instantly. You may want to try this with your project and see if it fixes it. Let me know your results... -Eric "Mike Landmeier" <mikelandmeier (AT) home (DOT) com> wrote in message news:%23w$IHzaNDHA.212 (AT) TK2MSFTNGP10 (DOT) phx.gbl... I have similar problems, but I haven't found the trigger. My project is a VS 2002 and I never had intellisense or auto-formatting problems when using VS2002. My project is a winform project and has numerous forms and user controls But now, when I work with my app, the editor starts to degrade; 1. Intellisense stops working 2. Undo/redo functionality is lost. Sometimes I get the message "Unknown undo/redo error". 3. Text selection works differently. "AAA.bbb" is selected instead of "AAA" when I double click on "AAA" 4. C# Autoformatting stops working. Most of the time, the problems clear up by exiting VS 2003 and restarting. Sometimes, I have to reboot. I am using VS 2003 Enterprise Architect. Generally, I am finding VS 2003 a distraction to use and have been considering going back to VS 2002. Eric, I don't have any solutions to offer, just the comfort of knowing you are not alone... Mike PS. With VS 2002, I had a macro that incremented the AssemblyVersion with every build. With VS 2003, this macro caused these editor problems to occur very frequently. I stopped using the macro and the editor problems still occur, but less frequently. "Eric" <eric (AT) datcomedia (DOT) com> wrote in message news:8bb24c6d.0306161318.681b7e79 (AT) posting (DOT) google.com... Using Visual Studio 2003 (Enterprise Developer): If I create a form in my solution that was converted from VS 2002, and then add a few text boxes and labels, and then go to the "View Code" view, all of my intellisense does not work, the auto-formatting does not work, copy/paste does not work, undo/redo does not work, and the wording such as "public" that is normally blue turns to black. See screenshot here: http://www.cyberbaal.com/randomville/vs2003bug.jpg If I close the design view and the code view of the form and go to "View Code" from the Solution Explorer, then it works fine. But the minute I have both "View Code" and the "View Design" views open at the same time, the problem occurs. However, if do the exact same steps in a new project created in Visual Studio 2003, it works fine and all of the features I describe above seem to work fine. I have tried removing the csproj.user file and the .suo file, and that does not correct it either. It seems to be something in just that one project file, but I have no idea what it could be. By the way, the solution contains multiple projects with this particular project being the startup project that has all UI based forms. I even reformatted my computer thinking maybe something got messed up when upgrading from VS 02 to VS 2003, but I still have the same problem. At this point, I am regretting upgrading to VS 2003 as this has caused a lot of headaches and 2002 was working just fine. Any thoughts on what I should do? Anyone else experience this? Thanks. -Eric |
|
« Previous Thread
|
Next Thread »
| Thread Tools | Search this Thread |
| Display Modes | |
Linear Mode
| |
Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.
Copyright ©2000 - 2013, Jelsoft Enterprises Ltd.