Re: visual studio .net 2003 aborts on startup
From: Ken Varn (nospam)
Date: 10/22/04
- Next message: Jonas Avellana: "VS.Net 2k3 Developing WebForms"
- Previous message: Cliff Sutton: "text box control"
- In reply to: ohdotoh: "Re: visual studio .net 2003 aborts on startup"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 22 Oct 2004 10:01:41 -0400
You make a lot of valid points.
I just had another VS.NET temporary file problem today. I tried to change
the virtual directory of one of my ASP.NET applications, and VS.NET refused
to output my bin files to the new directory location. It opened my source
files from the right place, but would not output the BIN files. The BIN
files were going to the wrong folder. After a day of digging, I finally
found that I had to delete a temporary ASP.NET directory to get it to
finally accept my virtual directory path change.
-- ----------------------------------- Ken Varn Senior Software Engineer Diebold Inc. EmailID = varnk Domain = Diebold.com ----------------------------------- "ohdotoh" <ohdotoh@discussions.microsoft.com> wrote in message news:B159AFAB-F60E-4088-AD55-D1DC032790B2@microsoft.com... > Okay, since I really hate it when people figure these things out on their own > and don't tell anyone: > > I ran the process explorer from sysinternals.com to see what was being > opened during the splash screen, and saw this in the list: > > File C:\Documents and Settings\sean\Local Settings\Application > Data\ApplicationHistory\devenv.exe.6262e30a.ini.inuse > > I deleted all the files in the ApplicationHistory folder and I can now use > visual studio again. > > Here's a little suggestion for Microsoft: > > Document more fully what files your programs use, what the purpose of the > file is, and !!!WHERE THE PROGRAM PUTS THEM ON THE SYSTEM!!!!! > > Or how about this? > > When a program is "un-installed" it should either: > remove every file (and folder) it silently created during its install and > use -- > or -- > tell the user where those files and folders are so they can remove them > 3rd party installers such as InstallShield typically offer this _HELPFUL_ > option > > Is this really so much to ask? A "re-install" or "repair" is really pretty > useless if it isn't going to clean up the damage it did the first time > around, the sloppy way that uninstalls are dealt with leads to an > accumulation of garbage in systems that simply doesn't have to happen with a > little attention to detail on the part of the people in charge of windows > development. > > I just spent 4 days wasting time trying to get VS2003 up and running, > because it silently created and opened files in an -- apparently, you try > searching for any mention -- undocumented folder that, had I known where to > look, could have been cleaned out and I could have been working again in 30 > seconds. > > Thanks to Ken for taking the time to respond, kudos Ken! > > Hang on! Hold the presses! Now that I already know what file I'm looking > for, here's a list of files in visual studio from the veritest certification > report: > http://cert.veritest.com/ReportFiles/Microsoft_VSnet_Preport.pdf > > Of course, the report claims that the file that was keeping the application > from working was "properly left behind" on uninstall. > > Application settings and history applicable only the application being > removed are considered "properly left behind"????? This is like going camping > and leaving the campsite littered with your empty beer cans on the way out. > > Perhaps I have a different view of "well behaved" programs, but in my view, > a program that on uninstall leaves behind a hidden, corrupted configuration > file that prevents the application from being able to function when > re-installed is not "well behaved", and the file was not "properly left > behind". > > If anyone has the resources to do better, Microsoft does. This is just plain > sloppy. > > Sean > > > "ohdotoh" wrote: > > > I moved all my projects to a different location, removed all visual studio > > applications and the folders left behind in documents and settings as well as > > program files, reinstalled visual studio (and the .net framework just in > > case) and still can't get past the splash screen without hitting the error. > > > > More ideas? > > > > Sean > > > > "Ken Varn" wrote: > > > > > I have had this occur once or twice. The usual culprit is a messed up > > > solution or project that you are loading at startup. For me it depended on > > > the type of project file that was last loaded. C++ projects are the ones > > > that I have had the problem with the most. > > > > > > If the previous project that was loaded was C++, delete all the temporary > > > project and solution files (i.e., *.ncb, *.user, *.suo (this one is hidden), > > > etc.. > > > > > > If it is some other type of project, then look at deleting all of the > > > temporary project files and see if that fixes it. > > > > > > You may also want to tweak the VS settings file to disable auto project load > > > at startup. > > > > > > > > > > > > -- > > > ----------------------------------- > > > Ken Varn > > > Senior Software Engineer > > > Diebold Inc. > > > > > > EmailID = varnk > > > Domain = Diebold.com > > > ----------------------------------- > > > "ohdotoh" <ohdotoh@discussions.microsoft.com> wrote in message > > > news:99756419-61FD-4E1D-8A29-835ECF05DAC7@microsoft.com... > > > > Faulting application devenv.exe, version 7.10.3077.0, faulting module > > > > msenv.dll, version 7.10.3077.0, fault address 0x00069583. > > > > > > > > This is on windows xp pro. > > > > > > > > It worked saturday morning, and saturday evening it wouldn't start. > > > Although > > > > I had installed visual studio 2005 beta several days before, everything > > > > continued to work as advertised until suddenly the ide aborts and sends an > > > > error report on startup. > > > > > > > > I attempted to rollback to a previous restore point. No change in the > > > > problem. I uninstalled the .net framework as well as all of vs2005 beta, > > > and > > > > then re-installed .net framework from the dvd. No change. I completely > > > > uninstalled all visual studio products, and deleted the orphaned folders > > > left > > > > behind in \Program Files and \Program Files\Common Files as well as the > > > ones > > > > in \Documents and Settings. I even moved all my source code folders to a > > > > different folder. > > > > > > > > I then reinstalled VS.NET 2003 from the dvd, and the problem persists. If > > > > Microsoft products can't avoid DLL Hell, what hope is there for us mere > > > > mortals? > > > > > > > > If I have to reformat and reload my system just to get VS.NET working > > > again, > > > > I am going to blow a gasket. Meanwhile, I have just spent two days that I > > > > needed to be spending writing code for the project I can't open anymore > > > > except in notepad because msenv.dll is barfing. > > > > > > > > P.S. This is my 'work at home' system, my system at the office is also > > > > running vs.net 2003, also had (no longer, can't take the risk) vs2005 > > > beta, > > > > but is running win2k and does not have the problem. > > > > > > > > I have searched google as well as msdn, and while I did find references to > > > > vs interdev 6 from 2 years ago, and someone else who never got an answer > > > for > > > > a similar sounding J++ error on MSDN, but no references to VS.NET 2003. > > > > > > > > Answers anyone? > > > > > > > > >
- Next message: Jonas Avellana: "VS.Net 2k3 Developing WebForms"
- Previous message: Cliff Sutton: "text box control"
- In reply to: ohdotoh: "Re: visual studio .net 2003 aborts on startup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
