 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Visual Studio.NET / IDE / May 2004Spot the error??
Below is the output text from a build. Notice the last line. Then try to spot the error. I couldn't but I guess VS2003 could. Please MS fix the bloody IDE. This is just a sample of the frustration at using this IDE. Time to close it and reopen. ------ Build started: Project: ToadInterfaces, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ------ Build started: Project: SQLEditor, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ------ Build started: Project: ArgumentControl, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ------ Build started: Project: SQLServer, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ------ Build started: Project: ToadUI, Configuration: Debug .NET ------ Preparing resources... Updating references... Performing main compilation... Building satellite assemblies... ---------------------- Done ---------------------- Build: 4 succeeded, 1 failed, 0 skipped You can edit the build macro to stop building on an error; it was discussed on one of these newsgroups a while ago. You should be able to find it on Google - Google seems able to conjure up every post that ever existed. Try looking in this one and vsnet.general. Steve > Below is the output text from a build. Notice the last line. Then try to > spot the error. I couldn't but I guess VS2003 could. Please MS fix the [quoted text clipped - 35 lines] > ---------------------- Done ---------------------- > Build: 4 succeeded, 1 failed, 0 skipped But there is no error. Just a VS2003 error that seems to think there is one, and if there is what is the error. All build steps report on errors. Lloyd Sheen > You can edit the build macro to stop building on an error; it was discussed > on one of these newsgroups a while ago. You should be able to find it on [quoted text clipped - 42 lines] > > ---------------------- Done ---------------------- > > Build: 4 succeeded, 1 failed, 0 skipped Sorry, assumed one was failing and it was carrying on regardless (which it also does). Does this only happen for this solution? These projects? Can you isolate the one that's "failing"? Are they all in fact getting built correctly, or is there actually an error that it isn't telling you about? Also, any build events that are being launched can cause a 'failure' even if everything does get built properly. I've never seen this happen, and we regularly have solutions with 10s of projects and multiple configurations and installers build without problems. Have you had a look on Google for phantom errors? Also, you might consider posting in one of the groups related to the type of projects you're building - there may be specific problems there. Steve > But there is no error. Just a VS2003 error that seems to think there is > one, and if there is what is the error. All build steps report on errors. [quoted text clipped - 54 lines] > > > ---------------------- Done ---------------------- > > > Build: 4 succeeded, 1 failed, 0 skipped In addition, just saw a post entitled "To all with phony build errors" in vsnet.general, dated 30 April at 19:16 (BST). It mentions a soon to be released hotfix, dunno if it's related to your problem. Steve > Sorry, assumed one was failing and it was carrying on regardless (which it > also does). Does this only happen for this solution? These projects? Can you [quoted text clipped - 73 lines] > > > > ---------------------- Done ---------------------- > > > > Build: 4 succeeded, 1 failed, 0 skipped I will search for that and see. The only solution I have found to to restart the IDE. This IDE is one of the most frustrating tools I have ever worked with. Lloyd Sheen > In addition, just saw a post entitled "To all with phony build errors" in > vsnet.general, dated 30 April at 19:16 (BST). It mentions a soon to be [quoted text clipped - 86 lines] > > > > > ---------------------- Done ---------------------- > > > > > Build: 4 succeeded, 1 failed, 0 skipped Additionally: Projects can be built individually (rather then building the entire solution). This way you will know which project is causing the error. Limiting the scope of your changes to a single project / code module / line of code at a time (as much as possible) and building often, will help to cut down on pathological errors. The thing I would like to know how to do is to step through the errors. In the olden Visual C++ IDE, it was possible to step through the errors by hitting the F4 key, but that does not seem to do the trick in VS.NET. Does anyone know the keyboard accelerator to do this? ccallen > You can edit the build macro to stop building on an error; it was discussed > on one of these newsgroups a while ago. You should be able to find it on [quoted text clipped - 42 lines] > > ---------------------- Done ---------------------- > > Build: 4 succeeded, 1 failed, 0 skipped The problem is that there is no error. The error is in VS2003. I get out of the car and get back in (restart the IDE) and all is good for a while. Just one of many problems with VS2003. Lloyd Sheen > Additionally: > Projects can be built individually (rather then building the entire [quoted text clipped - 63 lines] > > > ---------------------- Done ---------------------- > > > Build: 4 succeeded, 1 failed, 0 skipped Did you try building each project individually? Did all of the projects build with no errors, or were you able to isolate the project generating the error? Other troubleshooting steps: 1. Export the maike file and building at the command line. 2. Rebuild the bad project (or all of them if nessessary), which includes inspecting the project related files in notepad so look for anything obvious. 3. Try to repro the error on a different machine. > I get out of the car and get back in (restart the IDE) and all is good for a while. This kind of sounds like a hardware / software issue, Step 3 could help to confirm if you have a system problem. Step 2 is always a hassle, but many times I have fixed mysterious errors like this by rebuilding the whole thing from scratch. Never found the cause, but didnt have to deal with the problem either. > The problem is that there is no error. The error is in VS2003. > [quoted text clipped - 78 lines] > > > > ---------------------- Done ---------------------- > > > > Build: 4 succeeded, 1 failed, 0 skipped There is no bad project. Simply close IDE , open IDE and for a while things work. It is a VS problem. There are many other problems in the IDE just the same. This is just one of them. This was what is most likely a futile attempt to indicate to MS that while we all wait for the next release , we suffer with the current IDE. Lloyd Sheen > Did you try building each project individually? > Did all of the projects build with no errors, or were you able to isolate [quoted text clipped - 102 lines] > > > > > ---------------------- Done ---------------------- > > > > > Build: 4 succeeded, 1 failed, 0 skipped never seen anything like that in .Net 2003 in any of our projects what is it that u find so frustrating in .Net IDE? i've used VS 6, Borland - all flavours, Sun One... & etc. and find this IDE the best i've seen could u perhaps give some more precise info as to the nature of the project ? ;-) > Below is the output text from a build. Notice the last line. Then try to > spot the error. I couldn't but I guess VS2003 could. Please MS fix the [quoted text clipped - 35 lines] > ---------------------- Done ---------------------- > Build: 4 succeeded, 1 failed, 0 skipped If I was to list all the problem the newsgroup would run out of storage space. It seems the only way is to exit and restart the IDE. One example that I just encountered: Trying to debug a problem with a duplicate add into a Hashtable. The IDE returns an exception but there is no chance to see what it was. The exception is in a modal dialog and the IDE stops on the line with the class declaration for the mainform (using VB.NET). I put BP,s on all lines that add to the hashtable but it doesn't stop on any of the lines. And yes it is compiled with debug info, and other lines will stop. Just one , here is another. If the Solution Explorer is docked but not always shown (not sure the term) the toolbar items disappear. You have to click an item that is different type from the currently selected item to get the toolbar buttons back. I could go on but since it appears that MS is more worried about the next release (I was going to say upcomming but the delays make that a mute point) we will see no improvement on the VS2003 IDE. Oh well. Lloyd Sheen > never seen anything like that in .Net 2003 in any of our projects > [quoted text clipped - 47 lines] > > ---------------------- Done ---------------------- > > Build: 4 succeeded, 1 failed, 0 skipped I get the same problem every 10 builds or so with up to 11 out of 18 projects reporting a failure but no build failures. In my case a rebuild solution cures the problem for a while rather than exiting the IDE. My hunch is that the error is a dependency (or something) issue which throws an IDE error flagging the build as failed. This is only a guess ! > never seen anything like that in .Net 2003 in any of our projects > [quoted text clipped - 47 lines] > > ---------------------- Done ---------------------- > > Build: 4 succeeded, 1 failed, 0 skipped I will try the rebuild. But don't people think that MS should prop up this IDE so that when it does things like this and reports an error with no details this is a BUG. Lloyd Sheen > I get the same problem every 10 builds or so with up to 11 out of 18 > projects reporting a failure but no build failures. In my case a rebuild [quoted text clipped - 61 lines] > > > ---------------------- Done ---------------------- > > > Build: 4 succeeded, 1 failed, 0 skipped I attended an MSDN event yesterday, and a PM from the MS Usablity group assigned to VS.NET 2005 made a quick presentation. He said that they are very interested in getting feedback from all VS.NET users. This may not solve your immediate issues, but it's an additional ear to bend. http://www.microsoft.com/usability/ (and it sounds like your having what might be usability issues). The usability folks are also looking for people to come into thier usability labs to test VS.NET 2005 (it takes a couple hours and you get a free software of your choice for doing it). The first time I went in I got C8, which came in a huge box with all the white books (and lots of floppies). ccallen > I will try the rebuild. But don't people think that MS should prop up this > IDE so that when it does things like this and reports an error with no [quoted text clipped - 72 lines] > > > > ---------------------- Done ---------------------- > > > > Build: 4 succeeded, 1 failed, 0 skipped weird never had any such problems do you use try/catch blocks ? if you don't it's normal for the bp's to be ignored and the exception passed higher up when an exeption occurs on code called by a line with a bp if you do then once again - weird - probably indicates a bug in the MS code but again - never seen it - tried your solution-docked-toolbar thing - nothing changed - everything stable configuration problems? corrupted files? try a uninstall/re-install? i donno - all i can say is that neither i nor my colleagues have encountered such strange behavior so i can't help w/o actually being there or seeing your solution sorry I have now reinstalled VS 5 times. It makes no difference. I have 512 memory and nothing shows as a problem in any other application. The ones mentioned in this thread are just a sample of the problems. If you read this group all the time it seems that my disappointment is not unusual. Lloyd Sheen > weird > [quoted text clipped - 19 lines] > > sorry 5 times huh? sheesh ! i haven't re-installed it even once - since a year ago ! i work on military intelligence info systems that can get quite huge and sometimes ya gotta make 'em do code acrobatics to do what they want and i have yet to see this kind of problem - must be doin' somthin' right without knowing what it is !! so, i ain't got no more answers - sorry 8-) Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.